--- metadata: - name: generator content: Diplodoc Platform v5.50.6 alternate: - https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/provideOrderDigitalCodes.md - https://yandex.ru/dev/market/partner-api/doc/ru/reference/orders/provideOrderDigitalCodes.md - https://yandex.ru/dev/market/partner-api/doc/zh/reference/orders/provideOrderDigitalCodes.md --- > **Documentation Index:** Fetch the complete configuration index at https://yandex.ru/dev/market/partner-api/doc/en/llms.txt
# Transfer of digital goods keys {% list tabs %} - Info **The method is available for the [DBS](https://yandex.ru/dev/market/partner-api/doc/en/overview/dbs.md) model.** Not yet available for Market Yandex Go sellers. {% cut "**If you are using an API Key token, one of the accesses in the list is required to call the method**" %} * inventory-and-order-processing — [Order processing and inventory](https://yandex.ru/dev/market/partner-api/doc/en/_auto/scopes_summary/pages/inventory-and-order-processing.md) * all-methods — Full account management {% endcut %} Transfers the keys of the digital goods that the buyer ordered and paid for. After completing the request, yandex.Market will send him an email with the keys and activation instructions. If the email is delivered, yandex.Market will transfer the order to the final status. `DELIVERED`. {% note tip "После передачи кода покупателю статус заказа изменится не сразу" %} Enable API notifications — Yandex.Market will send you a request. [POST notification](https://yandex.ru/dev/market/partner-api/doc/en/push-notifications/reference/sendNotification.md) When the order status changes to `DELIVERED`. [How to work with notifications](https://yandex.ru/dev/market/partner-api/doc/en/push-notifications/index.md) {% endnote %} The key must be transferred within 30 minutes after the order status changes. `PROCESSING`. If one order includes several keys, send them all in one request. Each product has a unique `id` pass it as a separate element in the array. `items`, and the product keys — in the array `codes`. {% cut "Пример" %} ```json translate=no { "items": [ { "id": 1, "codes": [ "code1", "code2", "code3" ], "slip": "slip", "activate_till": "2025-02-18" }, { "id": 2, "codes": [ "code4", "code5", "code6" ], "slip": "slip", "activate_till": "2025-02-18" } ] } ``` {% endcut %} |
**⚙️ Limit:** 10 000 requests per hour
| |-| ## Request
POST {.openapi__method} ```text translate=no https://api.partner.market.yandex.ru/v2/campaigns/{campaignId}/orders/{orderId}/deliverDigitalGoods ```
### Path parameters #| || **Name** | **Description** || || _campaignId_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: integer The ID of the campaign (store) — The technical identifier that represents your store in the Yandex Market system when working through the API. It is uniquely linked to your store, but it is intended only for automated interaction. You can find it using a query [GET v2/campaigns](https://yandex.ru/dev/market/partner-api/doc/en/reference/campaigns/getCampaigns.md) or find it in the seller's office on the Market. Click on your account icon → **Settings** and in the menu on the left, select **APIs and modules**: * block **Campaign ID**; * tab **Query log** → drop-down list in the block **Show logs**. ⚠️ Do not confuse it with: - the store's identifier, which is displayed in the merchant's personal account. - advertising campaigns. _Min value:_{.json-schema-reset .json-schema-assertion} `1` {.table-cell} || || _orderId_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: integer The order ID. {.table-cell} || |#{.json-schema-properties}
### Body {% cut "application/json" %} ```json translate=no { "items": [ { "id": 0, "codes": [ "example" ], "slip": "example", "activate_till": "2025-01-01" } ] } ``` {% endcut %} #| || **Name** | **Description** || || _items_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| {% cut "**Type**: object[]" %} #| || _activate_till_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string<date> The date before which you need to activate the keys. If the keys are valid indefinitely, specify any date in the distant future. Date format: `YYYY-MM-DD`. _Example:_{.json-schema-reset .json-schema-example} `2025-01-01` {.table-cell} || || _id_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: integer The product ID in the order. It comes in the response of the method [POST v1/businesses/{businessId}/orders](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/getBusinessOrders.md) — parameter `id` in `items`. {.table-cell} || || _slip_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string Activation instructions. You can use HTML tags to format the text: * \, \

, \

and so on — for headlines; * \
and \

— for line breaks; * \

    — for a numbered list; * \
      — for a bulleted list. * \
    • — to create list items (must be inside \
        or \
          ); * \
          — It is supported, but it does not affect the text display. _Max length:_{.json-schema-reset .json-schema-assertion} `10000` _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || || _codes_{.json-schema-reset .json-schema-property} {.table-cell}| **Type**: string[] | null Keys related to the product. The field must be filled in. _Min items:_{.json-schema-reset .json-schema-assertion} `1` _Max items:_{.json-schema-reset .json-schema-assertion} `5000` _Unique items:_{.json-schema-reset .json-schema-assertion} `true` {% cut "**Example**" %}{.json-schema-example} ```json translate=no [ "example" ] ``` {% endcut %} {.table-cell} || |#{.json-schema-properties} {% endcut %} The list of products sold. For a product with the same `id` pass a single element and an array `codes` by the number of keys. _Min items:_{.json-schema-reset .json-schema-assertion} `1` _Max items:_{.json-schema-reset .json-schema-assertion} `100` {% cut "**Example**" %}{.json-schema-example} ```json translate=no [ { "id": 0, "codes": [ "example" ], "slip": "example", "activate_till": "2025-01-01" } ] ``` {% endcut %} {.table-cell} || |#{.json-schema-properties}
          ## Responses
          ## 200 OK An empty answer. {% note warning "Ответ `200` сам по себе не значит, что ключи переданы покупателю" %} If the email with the keys was delivered, yandex.Market will transfer the order to the final status. `DELIVERED`. The order status can be found using the method [POST v1/businesses/{businessId}/orders](https://yandex.ru/dev/market/partner-api/doc/en/reference/orders/getBusinessOrders.md). {% endnote %}
          ### Body {% cut "application/json" %} ```json translate=no { "status": "OK" } ``` {% endcut %} **Type**: object {% cut "**All of 1 type**" %}{.json-schema-combinators data-marker=and} - {% cut "**Type**: object" %} #| || _status_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The type of response. Possible values: * `OK` — There are no errors. * `ERROR` — an error occurred while processing the request. _Enum:_{.json-schema-reset .json-schema-value} `OK`, `ERROR` {.table-cell} || |#{.json-schema-properties} {% endcut %} The standard wrapper for server responses. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK" } ``` {% endcut %} {% endcut %}
          ## 400 Bad Request The request contains incorrect data. [Learn more about errors when working with orders](../../concepts/error-codes#orders)
          ### Body {% cut "application/json" %} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} **Type**: object {% cut "**All of 1 type**" %}{.json-schema-combinators data-marker=and} - **Type**: object {% cut "**All of 2 types**" %}{.json-schema-combinators data-marker=and} - **Type**: object #| || _status_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The type of response. Possible values: * `OK` — There are no errors. * `ERROR` — an error occurred while processing the request. _Enum:_{.json-schema-reset .json-schema-value} `OK`, `ERROR` {.table-cell} || |#{.json-schema-properties} The standard wrapper for server responses. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK" } ``` {% endcut %} - **Type**: object #| || _errors_{.json-schema-reset .json-schema-property} {.table-cell}| {% cut "**Type**: object[]" %} #| || _code_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The error code. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || || _message_{.json-schema-reset .json-schema-property} {.table-cell}| **Type**: string Description of the error. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || |#{.json-schema-properties} {% endcut %} A list of errors. _Min items:_{.json-schema-reset .json-schema-assertion} `1` {% cut "**Example**" %}{.json-schema-example} ```json translate=no [ { "code": "example", "message": "example" } ] ``` {% endcut %} {.table-cell} || |#{.json-schema-properties} {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %} A standard wrapper for server errors. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %}
          ## 401 Unauthorized The authorization data is not specified in the request. [More information about the error](https://yandex.ru/dev/market/partner-api/doc/en/concepts/error-codes.md#401)
          ### Body {% cut "application/json" %} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} **Type**: object {% cut "**All of 1 type**" %}{.json-schema-combinators data-marker=and} - **Type**: object {% cut "**All of 2 types**" %}{.json-schema-combinators data-marker=and} - **Type**: object #| || _status_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The type of response. Possible values: * `OK` — There are no errors. * `ERROR` — an error occurred while processing the request. _Enum:_{.json-schema-reset .json-schema-value} `OK`, `ERROR` {.table-cell} || |#{.json-schema-properties} The standard wrapper for server responses. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK" } ``` {% endcut %} - **Type**: object #| || _errors_{.json-schema-reset .json-schema-property} {.table-cell}| {% cut "**Type**: object[]" %} #| || _code_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The error code. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || || _message_{.json-schema-reset .json-schema-property} {.table-cell}| **Type**: string Description of the error. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || |#{.json-schema-properties} {% endcut %} A list of errors. _Min items:_{.json-schema-reset .json-schema-assertion} `1` {% cut "**Example**" %}{.json-schema-example} ```json translate=no [ { "code": "example", "message": "example" } ] ``` {% endcut %} {.table-cell} || |#{.json-schema-properties} {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %} A standard wrapper for server errors. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %}
          ## 403 Forbidden The authorization data is incorrect or access to the resource is prohibited. [More information about the error](https://yandex.ru/dev/market/partner-api/doc/en/concepts/error-codes.md#403)
          ### Body {% cut "application/json" %} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} **Type**: object {% cut "**All of 1 type**" %}{.json-schema-combinators data-marker=and} - **Type**: object {% cut "**All of 2 types**" %}{.json-schema-combinators data-marker=and} - **Type**: object #| || _status_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The type of response. Possible values: * `OK` — There are no errors. * `ERROR` — an error occurred while processing the request. _Enum:_{.json-schema-reset .json-schema-value} `OK`, `ERROR` {.table-cell} || |#{.json-schema-properties} The standard wrapper for server responses. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK" } ``` {% endcut %} - **Type**: object #| || _errors_{.json-schema-reset .json-schema-property} {.table-cell}| {% cut "**Type**: object[]" %} #| || _code_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The error code. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || || _message_{.json-schema-reset .json-schema-property} {.table-cell}| **Type**: string Description of the error. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || |#{.json-schema-properties} {% endcut %} A list of errors. _Min items:_{.json-schema-reset .json-schema-assertion} `1` {% cut "**Example**" %}{.json-schema-example} ```json translate=no [ { "code": "example", "message": "example" } ] ``` {% endcut %} {.table-cell} || |#{.json-schema-properties} {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %} A standard wrapper for server errors. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %}
          ## 404 Not Found The requested resource was not found. [More information about the error](https://yandex.ru/dev/market/partner-api/doc/en/concepts/error-codes.md#404)
          ### Body {% cut "application/json" %} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} **Type**: object {% cut "**All of 1 type**" %}{.json-schema-combinators data-marker=and} - **Type**: object {% cut "**All of 2 types**" %}{.json-schema-combinators data-marker=and} - **Type**: object #| || _status_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The type of response. Possible values: * `OK` — There are no errors. * `ERROR` — an error occurred while processing the request. _Enum:_{.json-schema-reset .json-schema-value} `OK`, `ERROR` {.table-cell} || |#{.json-schema-properties} The standard wrapper for server responses. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK" } ``` {% endcut %} - **Type**: object #| || _errors_{.json-schema-reset .json-schema-property} {.table-cell}| {% cut "**Type**: object[]" %} #| || _code_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The error code. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || || _message_{.json-schema-reset .json-schema-property} {.table-cell}| **Type**: string Description of the error. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || |#{.json-schema-properties} {% endcut %} A list of errors. _Min items:_{.json-schema-reset .json-schema-assertion} `1` {% cut "**Example**" %}{.json-schema-example} ```json translate=no [ { "code": "example", "message": "example" } ] ``` {% endcut %} {.table-cell} || |#{.json-schema-properties} {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %} A standard wrapper for server errors. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %}
          ## 420 Method Failure The resource access limit has been exceeded. [More information about the error](https://yandex.ru/dev/market/partner-api/doc/en/concepts/error-codes.md#420)
          ### Body {% cut "application/json" %} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} **Type**: object {% cut "**All of 1 type**" %}{.json-schema-combinators data-marker=and} - **Type**: object {% cut "**All of 2 types**" %}{.json-schema-combinators data-marker=and} - **Type**: object #| || _status_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The type of response. Possible values: * `OK` — There are no errors. * `ERROR` — an error occurred while processing the request. _Enum:_{.json-schema-reset .json-schema-value} `OK`, `ERROR` {.table-cell} || |#{.json-schema-properties} The standard wrapper for server responses. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK" } ``` {% endcut %} - **Type**: object #| || _errors_{.json-schema-reset .json-schema-property} {.table-cell}| {% cut "**Type**: object[]" %} #| || _code_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The error code. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || || _message_{.json-schema-reset .json-schema-property} {.table-cell}| **Type**: string Description of the error. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || |#{.json-schema-properties} {% endcut %} A list of errors. _Min items:_{.json-schema-reset .json-schema-assertion} `1` {% cut "**Example**" %}{.json-schema-example} ```json translate=no [ { "code": "example", "message": "example" } ] ``` {% endcut %} {.table-cell} || |#{.json-schema-properties} {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %} A standard wrapper for server errors. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %}
          ## 500 Internal Server Error Internal error of the Market. [More information about the error](https://yandex.ru/dev/market/partner-api/doc/en/concepts/error-codes.md#500)
          ### Body {% cut "application/json" %} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} **Type**: object {% cut "**All of 1 type**" %}{.json-schema-combinators data-marker=and} - **Type**: object {% cut "**All of 2 types**" %}{.json-schema-combinators data-marker=and} - **Type**: object #| || _status_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The type of response. Possible values: * `OK` — There are no errors. * `ERROR` — an error occurred while processing the request. _Enum:_{.json-schema-reset .json-schema-value} `OK`, `ERROR` {.table-cell} || |#{.json-schema-properties} The standard wrapper for server responses. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK" } ``` {% endcut %} - **Type**: object #| || _errors_{.json-schema-reset .json-schema-property} {.table-cell}| {% cut "**Type**: object[]" %} #| || _code_{.json-schema-reset .json-schema-property .json-schema-required} {.table-cell}| **Type**: string The error code. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || || _message_{.json-schema-reset .json-schema-property} {.table-cell}| **Type**: string Description of the error. _Example:_{.json-schema-reset .json-schema-example} `example` {.table-cell} || |#{.json-schema-properties} {% endcut %} A list of errors. _Min items:_{.json-schema-reset .json-schema-assertion} `1` {% cut "**Example**" %}{.json-schema-example} ```json translate=no [ { "code": "example", "message": "example" } ] ``` {% endcut %} {.table-cell} || |#{.json-schema-properties} {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %} A standard wrapper for server errors. {% cut "**Example**" %}{.json-schema-example} ```json translate=no { "status": "OK", "errors": [ { "code": "example", "message": "example" } ] } ``` {% endcut %} {% endcut %}
          - Console ```openapi-sandbox translate=no pathParams: - description: "The ID of the campaign (store) — The technical identifier that represents your store in the Yandex Market system when working through the API. It is uniquely linked to your store, but it is intended only for automated interaction.\n\nYou can find it using a query [GET\_v2/campaigns](../../reference/campaigns/getCampaigns.md) or find it in the seller's office on the Market. Click on your account icon → **Settings** and in the menu on the left, select **APIs and modules**:\n\n* block **Campaign ID**;\n* tab **Query log** → drop-down list in the block **Show logs**.\n\n⚠️ Do not confuse it with:\n- the store's identifier, which is displayed in the merchant's personal account.\n- advertising campaigns.\n" name: campaignId in: path required: true schema: type: integer format: int64 minimum: 1 - description: The order ID. name: orderId in: path required: true schema: type: integer format: int64 searchParams: [] headers: [] body: |- { "items": [ { "id": 0, "codes": [ "example" ], "slip": "example", "activate_till": "2025-01-01" } ] } schema: description: Request for the transfer of digital goods keys. type: object required: - items properties: items: description: > The list of products sold. For a product with the same `id` pass a single element and an array `codes` by the number of keys. type: array minItems: 1 maxItems: 100 items: description: A digital product. type: object required: - id - slip - activate_till properties: id: description: "The product ID in the order.\n\nIt comes in the response of the method [POST\_v1/businesses/{businessId}/orders](../../reference/orders/getBusinessOrders.md) — parameter `id` in `items`.\n" type: integer format: int64 code: description: | {% note warning "Вместо него используйте `codes`" %} Using both parameters together will result in an error. {% endnote %} The key itself. type: string maxLength: 256 deprecated: true x-deprecation-config: shutdown-date: '2026-10-19' replacement-field: codes x-hidden: true codes: description: | Keys related to the product. The field must be filled in. type: array items: type: string maxLength: 256 minItems: 1 maxItems: 5000 uniqueItems: true nullable: true slip: description: > Activation instructions. You can use HTML tags to format the text: * \, \

          , \

          and so on — for headlines; * \
          and \

          — for line breaks; * \

            — for a numbered list; * \
              — for a bulleted list. * \
            • — to create list items (must be inside \
                or \
                  ); * \
                  — It is supported, but it does not affect the text display. type: string maxLength: 10000 activate_till: description: > The date before which you need to activate the keys. If the keys are valid indefinitely, specify any date in the distant future. Date format: `YYYY-MM-DD`. type: string format: date bodyType: application/json method: post security: - type: apiKey name: 'Api-Key' in: header - type: oauth2 x-inline: true flows: implicit: authorizationUrl: https://oauth.yandex.ru/authorize scopes: market:partner-api: API Яндекс.Маркета / Поиска по товарам для партнеров path: v2/campaigns/{campaignId}/orders/{orderId}/deliverDigitalGoods host: https://api.partner.market.yandex.ru ``` {% endlist %}
                  [*Deprecated]: No longer supported, please use an alternative and newer version.