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
- inventory-and-order-processing — Order processing and inventory
- all-methods — Full account management
The request confirms the next shipment and returns the acceptance certificate in the format PDF.
The shipment confirmation is available only after it is generated, otherwise the method will return the code 400 and the error "Closest shipment for reception transfer act generation not found.".
Read more about accepting orders and shipping schedules. in the Help of the Market for sellers.
Express‑delivery
If your store is connected to express delivery and you ship orders to couriers Yandex Go, it is not necessary to prepare the acceptance certificate.
The act includes collected and ready-to-ship orders, which are shipped to a sorting center or pick-up point or transferred 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 merchant'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 external identifier of the seller's order, which can be sent by request POST v2/campaigns/{campaignId}/orders/{orderId}/external-id. |
|
Shipment number in the contractor's (subcontractor's) system |
The order ID on the Market, as in the query output: |
|
Declared value |
The total amount of the order, excluding the shipping cost, as shown in the query output: |
|
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 query output: |
|
Number of seats |
The number of cargo spaces in the order, as shown in the query output: |
Electronic signature of the act
If you specify the parameter signatory the acceptance and transfer certificate is signed with an electronic signature and becomes an electronic document. In this case, you do not need to manually print and sign the act. — it is already legally binding in electronic form.
If the parameter signatory not specified, the report needs to be printed. 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.
Read more about working with acceptance certificates. in the Help of the Market for sellers.
| ⚙️ Limit: 100 requests per hour |
|---|
Request
GET
https://api.partner.market.yandex.ru/v2/campaigns/{campaignId}/shipments/reception-transfer-act
Path parameters
|
Name |
Description |
|
campaignId* |
Type: integer<int64> 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 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:
⚠️ Do not confuse it with:
Min value: |
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 Electronic signature If you specify the parameter Read more about working with acceptance certificates. in the Help of the Market for sellers. Where to find the login:
|
|
warehouse_id |
Type: integer<int32> The warehouse ID. Min value: |
Responses
200 OK
Acceptance and transfer certificate in the format PDF.
Body
application/pdf
Type: string
Format: binary
400 Bad Request
The request contains incorrect data. More information about the error
| Description | Explanation | Solution methods |
|---|---|---|
| Closest shipment for reception transfer act generation not found | Shipments with the status Can be processed not found. | Create a purchase order or wait for the existing order to be upgraded to the desired status. |
| No orders for closest shipment have been processed yet | There are no orders in the next shipment. | Check that the orders have the parameter status it matters PROCESSING, and the parameter substatus — READY_TO_SHIP. You can get the statuses and shipping dates of orders using query methods. GET v2/campaigns/{campaignId}/orders/{orderId}, GET v2/campaigns/{campaignId}/orders or POST v1/businesses/{businessId}/orders, change order statuses — using methods PUT v2/campaigns/{campaignId}/orders/{orderId}/status and POST v2/campaigns/{campaignId}/orders/status‑update. |
| Some orders are in the process of being excluded from shipment {orders id}. Please wait up to 30 minutes and try again | IDs of orders in the nearest shipment that are in the process of being deleted from it. | Transferring orders can take up to 30 minutes. Wait for the transfer to finish and try again. |
| Some orders have not been processed yet. Please change the status of orders to READY_TO_SHIP and try again. {orders id} | IDs of orders in the nearest shipment that have not yet been processed. | Send it for orders with the specified IDs status: PROCESSING and substatus: READY_TO_SHIP and try again. You can change the order statuses using queries PUT v2/campaigns/{campaignId}/orders/{orderId}/status and POST v2/campaigns/{campaignId}/orders/status‑update. |
Body
application/json
{
"status": "OK",
"errors": [
{
"code": "string",
"message": "string"
}
]
}
|
Name |
Description |
|
errors |
Type: object[] A list of errors. Min items: |
|
status |
Type: string The type of response. Possible values:
Enum: |
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: object[] A list of errors. Min items: |
|
status |
Type: string The type of response. Possible values:
Enum: |
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: object[] A list of errors. Min items: |
|
status |
Type: string The type of response. Possible values:
Enum: |
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: object[] A list of errors. Min items: |
|
status |
Type: string The type of response. Possible values:
Enum: |
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: object[] A list of errors. Min items: |
|
status |
Type: string The type of response. Possible values:
Enum: |
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: object[] A list of errors. Min items: |
|
status |
Type: string The type of response. Possible values:
Enum: |
No longer supported, please use an alternative and newer version.