---
metadata:
  - name: generator
    content: Diplodoc Platform v5.55.0
alternate:
  - https://yandex.com/dev/market/partner-api/doc/en/pushapi/concepts/identification.md
  - https://yandex.com/dev/market/partner-api/doc/ru/pushapi/concepts/identification.md
  - https://yandex.com/dev/market/partner-api/doc/zh/pushapi/concepts/identification.md
  - href: en/pushapi/concepts/identification.md
    type: text/markdown
    title: Markdown version
  - href: ../../llms.txt
    type: text/markdown
    title: llms.txt
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com/dev/market/partner-api/doc/en/llms.txt


{% note warning "Starting from December 31, push API methods will be unavailable. From October 1, they may be unstable." %}

 

{% endnote %}
 
# Authorization for Yandex.Market requests to the store

The store must be able to identify requests from the Market in order to distinguish them from unauthorized third-party requests. To authorize the Market, an authorization token is used, which is transmitted with each request via URL-parameter or HTTP header (depending on the settings in the merchant's account on the Market).

**Example:**

- in the parameters URL:

    ```no-highlight translate=no
    POST https://<host>/<path_to_market_api>/order/accept?auth-token=41FBAC4A763D480999DAEDAC09B36CBB200000016A894A28
    ```

- in the HTTP header `Authorization`:

    ```no-highlight translate=no
    Authorization: 41FBAC4A763D480999DAEDAC09B36CBB200000016A894A28
    ```

The store must compare the transferred token with the token generated in the seller's account on the Market earlier. If an attempt is made to transfer an incorrect token or if it is missing, the store must return an error. `403 Forbidden`.

## Getting a token {#token}

The authorization token can be generated in the merchant's account on the Market — click on your account icon → **Settings** and in the menu on the left, select **APIs and modules** → tab **Push API**.

{% note warning "Save the token immediately after generation" %}

The token is displayed in the cabinet once — immediately after generation. If it gets lost, you will need to generate a new one.

{% endnote %}

Yandex.Market does not guarantee that requests will come from a specific IP address or set of IP addresses. Since the authorization token is passed in all requests from the Market, to simplify the descriptions of API methods, this parameter is not specified in the examples.

## It may be useful {#read-more}

* [Request method](https://yandex.com/dev/market/partner-api/doc/en/pushapi/concepts/request-method.md)
* [SSL certificate](https://yandex.com/dev/market/partner-api/doc/en/pushapi/concepts/ssl-certificate.md)