Confirm claim

The method confirms if the claim was successfully evaluated. After the claim is confirmed, its status changes to accepted, and the service starts the process of searching for an executor.

The pricing.offer is valid for a limited period of time (10 minutes).
After it expires, the order status changes to failed if an attempt is made to confirm the order.

Request

POST

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

Service URL

Query parameters

Name

Description

claim_id

Type: string

Claim ID received at the claim creation stage

Min length: 32

Max length: 64

Example: ``

Headers

Name

Description

Accept-Language

Type: string

Preferred response language. Examples: "en" — English

Example: en

Body

application/json

{
  "version": 1
}

Name

Description

version

Type: integer

Claim version. Changed after the claim was edited (int64)

Responses

200 OK

Claim confirmed

Body

application/json

{
  "id": "741cedf82cd464fa6fa16d87155c636",
  "status": "new",
  "version": 1,
  "user_request_revision": "example",
  "skip_client_notify": true
}

Name	Description
id	Type: ClaimId Claim ID obtained at the claim creation stage Min length: `32` Max length: `64` Example: `741cedf82cd464fa6fa16d87155c636`
skip_client_notify	Type: boolean
status	Type: ClaimStatus Claim status. To learn more, see Status model Enum: `new`, `estimating`, `estimating_failed`, `ready_for_approval`, `accepted`, `performer_lookup`, `performer_draft`, `performer_found`, `performer_not_found`, `pickup_arrived`, `ready_for_pickup_confirmation`, `pickuped`, `delivery_arrived`, `ready_for_delivery_confirmation`, `delivered`, `delivered_finish`, `returning`, `return_arrived`, `ready_for_return_confirmation`, `returned`, `returned_finish`, `failed`, `cancelled`, `cancelled_with_payment`, `cancelled_by_taxi`, `cancelled_with_items_on_hands`
user_request_revision	Type: string The current version of changes in the claim entered by the user Example: `example`
version	Type: integer Claim version from the request (int64)

ClaimId

Claim ID obtained at the claim creation stage

Type: string

Min length: 32

Max length: 64

Example: 741cedf82cd464fa6fa16d87155c636

ClaimStatus

Claim status. To learn more, see Status model

Type: string

Enum: new, estimating, estimating_failed, ready_for_approval, accepted, performer_lookup, performer_draft, performer_found, performer_not_found, pickup_arrived, ready_for_pickup_confirmation, pickuped, delivery_arrived, ready_for_delivery_confirmation, delivered, delivered_finish, returning, return_arrived, ready_for_return_confirmation, returned, returned_finish, failed, cancelled, cancelled_with_payment, cancelled_by_taxi, cancelled_with_items_on_hands

404 Not Found

Claim not found

Body

application/json

{
  "code": "not_found",
  "message": "Claim not found"
}

Name

Description

code

Type: string

Error code

Const: not_found

Example: not_found

message

Type: string

Error description

Example: Claim not found

409 Conflict

Attempting to confirm the claim that wasn't evaluated

Body

application/json

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

Name

Description

code

Type: string

Error code

Enum: inappropriate_status, old_version, offer_expired, state_mismatch

message

Type: string

Error description

Example: Invalid action regarding the claim

429 Too Many Requests

Too many requests

Body

application/json

{
  "code": "too_many_requests",
  "message": "Too many requests"
}

Name

Description

code

Type: string

Error code

Const: too_many_requests

Example: too_many_requests

message

Type: string

Error description

Example: Too many requests

Was the article helpful?

1. Create claim

3. Get claim information