Main flow

This section describes the simplest flow: the service automatically selects a robot, the robot picks up the cargo at the loading point and takes it to the delivery point. For more information about other options, see Popular use cases.

Step

Who performs

Action

1

Partner

Creates an order for cargo delivery to the customer.

In the route_points array within the request body, specify the loading point type = source and the delivery point type = destination. You need to specify the visit order for each point in the visit_order field, starting with 0.

In the conditions section, you can specify the maximum_first_point_eta parameter: then only those robots that can arrive at the loading point before the specified time will be considered.

The service expects date and time with timezone specification. Example formats:

  • 2026-01-11 17:26:27.704301+00:00
  • 2026-01-11T19:18:43Z

If timezone is not specified, the service assumes UTC+0 timezone.

Request
POST /claims/create?idempotency_key=<your_idempotency_key>

{
"route_points": [
    {
    "address": {
        "coordinates": [
            55.733989,
            37.588116
        ]
    },
    "point_id": "0",
    "type": "source",
    "visit_order": 0
    },
    {
    "address": {
        "coordinates": [
            55.735120,
            37.642817
        ]
    },
    "point_id": "1",
    "type": "destination",
    "visit_order": 1
    }
],
"external_order_id": "Order #1",
"conditions": {}
}

The response returns the id of the created order.

Response
{
    "created_at": "2025-01-29T18:02:01Z",
    "updated_at": "2025-01-29T18:02:01Z",
    "id": "5555",
    "route_points": [
        {
            "address": {
                "coordinates": [
                    55.733989,
                    37.588116
                ]
            },
            "id": "0",
            "visit_order": 0
        },
        {
            "address": {
                "coordinates": [
                    55.735120,
                    37.642817
                ]
            },
            "id": "1",
            "visit_order": 0
        }
    ],
    "status": "new",
    "eta": 100,
    "user_request_revision": "0"
}

2

Service

Evaluates the order, which takes about 1 second. The order is automatically approved, and the estimated time of arrival (ETA) to the customer is calculated. A robot is chosen for the order, the order is sent for delivery, and the order status to performer_found.

Additional flows:

3

Partner

Requests the order status using the order id obtained at step 1. This request is also used throughout the route to monitor the current order status and ETA. See Statuses.

Request
POST /claims/info?claim_id=<your_claim_id>

For the approved order, status = accepted. The eta field returns the estimated time of arrival.

Response
{
    "created_at": "2025-01-29T18:02:01Z",
    "updated_at": "2025-01-29T18:02:01Z",
    "id": "5555",
    "route_points": [
        {
            "address": {
                "coordinates": [
                    55.733989,
                    37.588116
                ]
            },
            "id": "0",
            "visit_order": 0
        },
        {
            "address": {
                "coordinates": [
                    55.735120,
                    37.642817
                ]
            },
            "id": "1",
            "visit_order": 0
        }
    ],
    "status": "new",
    "eta": 100,
    "user_request_revision": "0"
}

4

Robot

Arrives at the cargo pickup point. The order status is pickup_arrived.

5

Partner

Opens the lid to put the cargo.

Request
POST /claims/open_hatch?claim_id=<your_claim_id>&idempotency_key=<your_idempotency_key>

6

Partner

After the cargo is loaded, confirms it. When confirmed, the robot lid closes automatically: you don't have to send a request.

Request
POST /claims/confirm_exchange?claim_id=<your_claim_id>&idempotency_key=<your_idempotency_key>

7

Robot

Transports the cargo to the delivery point. The order status is delivery_arrived.

8

Customer

Opens the lid to pick up the cargo.

Request
POST /claims/open_hatch?claim_id=<your_claim_id>&idempotency_key=<your_idempotency_key>

Additional flow:

9

Customer

After receiving the cargo, the customer confirms the delivery. When confirmed, the robot lid closes automatically: you don't have to send a request.

Request
POST /claims/confirm_exchange?claim_id=<your_claim_id>&idempotency_key=<your_idempotency_key>

Additional flow:

The order status changed to delivered. The order is complete.

If you didn't find the answer you were looking for, you can use the feedback form to submit your question. Please describe the problem in as much detail as possible. Attach a screenshot if possible.

Contact support

The customer uses the partner's mobile app.

Previous
Recommendations and restrictions
Next
Popular use cases