Receipt of the acceptance certificate

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

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 request generates an act of acceptance and transfer of orders included in the shipment, and returns the act in the format PDF. The report contains orders that have been collected and are ready for shipment.

The method is only available for a confirmed shipment. First, confirm the shipment with a request POST v2/campaigns/{campaignId}/shipments/{shipmentId}/confirm then call this method.

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

Date

The date of the request.

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 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:

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:

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/v2/campaigns/{campaignId}/first-mile/shipments/{shipmentId}/act

Path parameters

Name

Description

campaignId*

Type: integer<int64>

The store's campaign ID.

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:

  • block Campaign ID;
  • tab Query log → drop-down list in the block Show logs.

⚠️ It does not match the store's ID (which is indicated in the merchant's account on the Market next to the store's name and in some reports). It is linked to the store one-to-one. Does not apply to advertising campaigns.

Min value: 1

shipmentId*

Type: integer<int64>

Shipment ID.

Min value: 1

Responses

200 OK

Acceptance and transfer certificate for shipment in the format PDF.

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: object[]

A list of errors.
The general error format.

Min items: 1

status

Type: string

The type of response. Possible values:

  • OK — There are no errors.
  • ERROR — an error occurred while processing the request.

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: object[]

A list of errors.
The general error format.

Min items: 1

status

Type: string

The type of response. Possible values:

  • OK — There are no errors.
  • 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: object[]

A list of errors.
The general error format.

Min items: 1

status

Type: string

The type of response. Possible values:

  • OK — There are no errors.
  • 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: object[]

A list of errors.
The general error format.

Min items: 1

status

Type: string

The type of response. Possible values:

  • OK — There are no errors.
  • 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: object[]

A list of errors.
The general error format.

Min items: 1

status

Type: string

The type of response. Possible values:

  • OK — There are no errors.
  • 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: object[]

A list of errors.
The general error format.

Min items: 1

status

Type: string

The type of response. Possible values:

  • OK — There are no errors.
  • ERROR — an error occurred while processing the request.

Enum: OK, ERROR

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