Confirmation of the nearest shipment and receipt of the acceptance certificate for it

The method is available for the FBS model.

If you are using an API Key token, one of the accesses in the list is required to call the method

The request confirms the next shipment and returns the acceptance certificate in PDF format.

Express delivery

If your store is connected to express delivery and you ship orders to couriers [Yandex Go(https://go.yandex /), it is not necessary to prepare the acceptance certificate.

The act includes collected and ready-to-ship orders that are shipped to a sorting center or a pick-up point or to Market couriers.

When forming an act, the Market automatically finds and inserts the following data into the template:

The data from which the Market generates the report

Data in the report

Description

Sender

The name of your legal entity indicated in the seller's account on the Market.

Executor

The name of the legal entity of the sorting center or delivery service.

Shipment number in the customer's system

The field is no longer in use

Your order ID, which you provided in the response to the request POST order/accept from the Market.

Shipment number in the contractor's (subcontractor's) system

The ID of the order on the Market, as in the request output GET campaigns/{campaignId}/orders.

Declared value

The total amount of the order excluding the shipping cost, as shown in the request output GET campaigns/{campaignId}/orders or GET campaigns/{campaignId}/orders/{orderId}.

The cost of all the items in the order

The cost of all ordered items.

Weight

The gross weight of the cargo area (the total weight of the package and contents), as in the request output GET campaigns/{campaignId}/orders or GET campaigns/{campaignId}/orders/{orderId}.

Number of seats

The number of cargo spaces in the order, as shown in the request output GET campaigns/{campaignId}/orders or GET campaigns/{campaignId}/orders/{orderId}.

In the printed statement, specify the sender and the contractor. They must sign the act and indicate their last name and initials next to the signature. If necessary, also fill in the details of the power of attorney.

, Limit: 100 requests per hour

Request

GET

https://api.partner.market.yandex.ru/campaigns/{campaignId}/shipments/reception-transfer-act

Path parameters

Name

Description

campaignId*

Type: integer<int64>

The campaign ID.

You can find it using a query GET campaigns or find it in the seller's office on the Market — click on the name of your business and go to the page:

  • Modules and APIs → block Sending data to Yandex.Market.
  • Query log → drop-down list in the block Show logs.

, Do not send the store ID instead, which is indicated in the seller's account on the Market next to the store name and in some reports.

Min value: 1

Query parameters

Name

Description

signatory

Type: string

The username of the user in Yandex ID, on whose behalf the electronic acceptance certificate will be signed.

Specified without @yandex.ru.

Where to find it:

warehouse_id

Type: integer<int32>

The warehouse ID.

Min value: 1
Example: 123123

Responses

200 OK

Acceptance and transfer certificate in PDF format.

Body

application/pdf

Type: string

Format: binary

400 Bad Request

The request contains incorrect data. More information about the error

Body

application/json
{
    "status": "OK",
    "errors": [
        {
            "code": "string",
            "message": "string"
        }
    ]
}

Name

Description

errors

Type: ApiErrorDTO[]

A list of errors.
The general error format.

Min items: 1

status

Type: ApiResponseStatusType

The type of response. Possible values:

  • OK — there are no mistakes.
  • ERROR — an error occurred while processing the request.

Enum: OK, ERROR

ApiErrorDTO

The general error format.

Name

Description

code*

Type: string

The error code.

message

Type: string

Description of the error.

ApiResponseStatusType

The type of response. Possible values:

  • OK — there are no mistakes.
  • ERROR — an error occurred while processing the request.

Type

Description

ApiResponseStatusType

Enum: OK, ERROR

401 Unauthorized

The authorization data is not specified in the request. More information about the error

Body

application/json
{
    "status": "OK",
    "errors": [
        {
            "code": "string",
            "message": "string"
        }
    ]
}

Name

Description

errors

Type: ApiErrorDTO[]

A list of errors.
The general error format.

Min items: 1

status

Type: ApiResponseStatusType

The type of response. Possible values:

  • OK — there are no mistakes.
  • ERROR — an error occurred while processing the request.

Enum: OK, ERROR

403 Forbidden

The authorization data is incorrect or access to the resource is prohibited. More information about the error

Body

application/json
{
    "status": "OK",
    "errors": [
        {
            "code": "string",
            "message": "string"
        }
    ]
}

Name

Description

errors

Type: ApiErrorDTO[]

A list of errors.
The general error format.

Min items: 1

status

Type: ApiResponseStatusType

The type of response. Possible values:

  • OK — there are no mistakes.
  • ERROR — an error occurred while processing the request.

Enum: OK, ERROR

404 Not Found

The requested resource was not found. More information about the error

Body

application/json
{
    "status": "OK",
    "errors": [
        {
            "code": "string",
            "message": "string"
        }
    ]
}

Name

Description

errors

Type: ApiErrorDTO[]

A list of errors.
The general error format.

Min items: 1

status

Type: ApiResponseStatusType

The type of response. Possible values:

  • OK — there are no mistakes.
  • ERROR — an error occurred while processing the request.

Enum: OK, ERROR

420 Method Failure

The resource access limit has been exceeded. More information about the error

Body

application/json
{
    "status": "OK",
    "errors": [
        {
            "code": "string",
            "message": "string"
        }
    ]
}

Name

Description

errors

Type: ApiErrorDTO[]

A list of errors.
The general error format.

Min items: 1

status

Type: ApiResponseStatusType

The type of response. Possible values:

  • OK — there are no mistakes.
  • ERROR — an error occurred while processing the request.

Enum: OK, ERROR

500 Internal Server Error

Internal error of the Market. More information about the error

Body

application/json
{
    "status": "OK",
    "errors": [
        {
            "code": "string",
            "message": "string"
        }
    ]
}

Name

Description

errors

Type: ApiErrorDTO[]

A list of errors.
The general error format.

Min items: 1

status

Type: ApiResponseStatusType

The type of response. Possible values:

  • OK — there are no mistakes.
  • ERROR — an error occurred while processing the request.

Enum: OK, ERROR

No longer supported, please use an alternative and newer version.