Skip a point in the multi-point claim

The method initiates the return of the order by the courier to the initial point of dispatch. The operation can be performed only if the courier has already picked up the order.


If there are multiple destination points on the route, the point specified in the request will be skipped, and the courier will return the item back to the dispatcher after completing the route.

Request

POST

b2b.taxi.yandex.net/b2b/cargo/integration/v2/claims/return

Service URL

Query parameters

Name

Description

claim_id*

Type: string

Claim ID received at the claim creation stage

Min length: 32

Max length: 64

Headers

Name

Description

Accept-Language*

Type: string

Preferred response language. Examples: "en" — English

Example: en

Body

application/json
{
    "point_id": 372036854775807,
    "comment": "The consumer rejected the order",
    "need_return_items": false
}

Name

Description

comment*

Type: string

The reason why the point needs to be skipped

Example: The consumer rejected the order

Max length: 1000

point_id*

Type: integer<int64>

ID of the point that needs to be skipped

Example: 372036854775807

need_return_items

Type: boolean

Return the item to the initial point of dispatch

Responses

200 OK

Return initiated

400 Bad Request

Incorrect point

Body

application/json
{
    "code": "state_mismatch",
    "message": "Invalid action regarding the claim"
}

Name

Description

code*

Type: string

Error code

Example: state_mismatch

Enum: state_mismatch

message*

Type: string

Error description

Example: Invalid action regarding the claim

404 Not Found

Claim not found

Body

application/json
{
    "code": "not_found",
    "message": "Claim not found"
}

Name

Description

code*

Type: string

Error code

Example: not_found

Enum: not_found

message*

Type: string

Error description

Example: Claim not found

409 Conflict

We haven't found a courier yet. You can cancel the request

Body

application/json
{
    "code": "state_mismatch",
    "message": "Invalid action regarding the claim"
}

Name

Description

code*

Type: string

Error code

Example: state_mismatch

Enum: not_allowed, state_transition_forbidden, state_mismatch

message*

Type: string

Error description

Example: Invalid action regarding the claim

410 Gone

Inactive claim

Body

application/json
{
    "code": "inappropriate_status",
    "message": "Invalid action regarding the claim"
}

Name

Description

code*

Type: string

Error code

Example: inappropriate_status

Enum: inappropriate_status

message*

Type: string

Error description

Example: Invalid action regarding the claim