Closing documents

The method is available for all models.

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

Returns a ZIP archive with closing documents in PDF format for the specified month.

The composition of the documents depends on the type of contract

  • Placement agreement

    • the act of rendered services
    • the invoice
    • summary report on statistics data
    • report on the execution of the assignment and on the settlement of mutual claims (agent's report)

  • Promotion agreement (not concluded in Russia after September 30, 2024)

    • the act of rendering services
    • the invoice if the tax scheme requires it

  • Marketing agreement

    • the act of rendered services
    • the invoice
    • advance payment invoice
    • personal account statement
    • details of the report

You can find out the generation status and get a link to the archive using a request. GET reports/info/{reportId}.

, Limit: 1,000 requests per hour

Request

POST

https://api.partner.market.yandex.ru/reports/closure-documents/generate

Body

application/json
{
    "campaignId": 0,
    "monthOfYear": {
        "year": 2025,
        "month": 12
    },
    "contractTypes": [
        "INCOME"
    ]
}

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.

monthOfYear*

Type: ClosureDocumentsMonthOfYearDTO

The month for which the closing documents are needed.

contractTypes

Type: ClosureDocumentsContractType[]

Types of contracts that require closing documents.

If you do not specify them, the archive with documents for all found contracts will be returned.
Type of agreement:

  • INCOME — the accommodation agreement.

  • OUTCOME — a promotion agreement.

  • MARKETING — a marketing contract.

Enum: INCOME, OUTCOME, MARKETING

Min items: 1

Max items: 3

Unique items  

ClosureDocumentsMonthOfYearDTO

Month and year.

Name

Description

month*

Type: integer<int32>

The month number.

Example: 12

Min value: 1

Max value: 12

year*

Type: integer<int32>

Year.

Example: 2025

ClosureDocumentsContractType

Type of agreement:

  • INCOME — the accommodation agreement.

  • OUTCOME — a promotion agreement.

  • MARKETING — a marketing contract.

Type

Description

ClosureDocumentsContractType

Enum: INCOME, OUTCOME, MARKETING

Responses

200 OK

A ZIP archive with closing documents in PDF format.

Body

application/json
{
    "status": "OK",
    "result": {
        "reportId": "string",
        "estimatedGenerationTime": 0
    }
}

Name

Description

result

Type: GenerateReportDTO

The ID that will be needed to track the generation status and receive the finished report or document.

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

GenerateReportDTO

The ID that will be needed to track the generation status and receive the finished report or document.

Name

Description

estimatedGenerationTime*

Type: integer<int64>

Expected generation time in milliseconds.

reportId*

Type: string

The ID that will be needed to track the generation status and receive the finished report or document.

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

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.

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

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 Yandex. 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.

It lists all the services that the Market has provided to the seller over the past month.

Read more about the act in Yandex.Market Help for sellers.

It lists all the services that the Market has provided to the seller over the past month.

This is a mandatory document regulated by a special Government decree.

The invoice contains the same information as in the certificate of services rendered. It is more convenient to use an act for accounting and analysis.

This is a mandatory document regulated by a special Government decree.

The invoice contains the same information as the service delivery certificate. It is more convenient to use an act for accounting and analysis.

The store's accountant needs a summary report to reflect the sale of goods in accounting.

The report is compiled for stores operating under the FBY and FBS models. It indicates how many items and for what amount:

  • sent to customers;
  • delivered to customers;
  • The buyers did not buy back;
  • the buyers returned it.
The report is in the same PDF file as the certificate of services rendered.

Read more about the report in Yandex.Market Help for sellers.

The report shows how much money the Market has received from customers, how much it has already transferred to the seller, and how much it still owes.

Read more about the report in Yandex.Market Help for sellers.

The act states:

  • the total amount of all discounts on products that the Market has provided to customers;
  • the total amount of all shipping discounts that the Market has provided to customers (only for the DBS model);
  • the total amount of payments in Plus points.

Shows the amount on the balance at the beginning of the month that the seller has not spent yet. The document is useful for an accountant.

Shows the seller's balance — expenses and the balance at the end of the month.

Shows the services provided by all the brands of the seller or advertiser. The details are useful for accounting purposes.

Previous
Detailed information on orders
Next
Sales Analytics Report