Dostavista API Integration: Cost Calculation, Ordering, Courier Tracking
Losing orders due to missing delivery cost calculations is a reality for 30% of online stores. Customers leave if they don't see an exact price. Integrating Dostavista solves this: the API allows calculating costs, creating orders, and tracking couriers in real time. Our accumulated experience (15+ projects) ensures stable operation without surprises. Average delivery cost savings compared to traditional services are 25%. Contact us for a project assessment — we'll propose the optimal solution.
Why Integrate Dostavista?
Dostavista is a crowdsourcing platform that delivers 2x faster than traditional courier services. A flexible transport type system lets you transport anything from documents to large furniture. The API provides all necessary methods: cost calculation, order creation, status tracking. We use our 10+ years of web development experience for reliable integration. According to our data, cart conversion increases by 15% on average after integration.
Dostavista API Methods
Dostavista provides a REST API with authorization via X-User-Email and X-User-Token. A sandbox environment is available at robotapitest.dostavista.ru. Before using, create an account and get an API token from your personal cabinet. The API has a limit of 10 requests per second per account. Exceeding it returns 429 Too Many Requests, so use caching for calculations. For more details, see the Dostavista API Documentation.
How to Calculate Delivery Cost
POST /api/business/v1/calculate-order { "matter": "Документы", "insurance_amount": "0", "vehicle_type_id": 1, // 1=пешеход, 2=велосипед, 3=мотоцикл, 8=авто "points": [ { "address": "Москва, Тверская, 1", "client_order_id": "pickup" }, { "address": "Москва, Арбат, 10", "client_order_id": "delivery" } ] } The response includes delivery_fee_amount in kopecks — the delivery cost. We recommend adding a small buffer (+5–10%) to the displayed cost, as the final price may slightly differ due to dynamic pricing. Cache results for 1 minute to reduce requests.
How to Create an Order
POST /api/business/v1/create-order { "matter": "Одежда", "vehicle_type_id": 3, "backpay_amount": "0", // наложенный платёж "points": [ { "address": "Москва, Складской переулок, 5", "contact_person": {"phone": "+79001234567", "name": "Склад"}, "taking_amount": "0", "note": "Позвонить за 15 минут" }, { "address": "Москва, Ленина, 20, кв 5", "contact_person": {"phone": "+79007654321", "name": "Покупатель"}, "is_door_to_door": true, "note": "Код домофона: 456" } ] } If vehicle_type_id is invalid, the API returns a 400 error. Use a unique client_order_id for idempotency — this prevents duplicate orders on retries.
Configuring Webhooks for Notifications
- In your Dostavista personal cabinet, specify the URL of your endpoint to receive POST requests.
- Implement event handling:
order.created,order.status_changed,order.finished. - The webhook sends JSON with fields:
order_id,status,courier_latitude,courier_longitude. - Ensure your server responds with 200 OK within 5 seconds — on timeout, the context is retried up to 3 times.
- Test in the sandbox environment by imitating different statuses. For local debugging, use services like webhook.site or ngrok.
Real-Time Courier Tracking
Order statuses can be tracked via polling (GET /api/business/v1/orders/{id}) or webhooks. Current statuses:
| Status | Description |
|---|---|
| new | Order created, awaiting courier assignment |
| available_for_couriers | Available for couriers to take |
| active | Courier assigned, delivering |
| finished | Delivery completed |
| delayed | Execution delayed |
| courier_not_found | Failed to assign courier |
| canceled | Canceled |
The response includes courier_latitude and courier_longitude — courier coordinates. Use JavaScript libraries like Leaflet to display on a map.
Choosing a Transport Type
Dostavista allows selecting transport based on cargo:
| Type | What it transports | Example |
|---|---|---|
| Pedestrian | Small documents, envelopes | Contracts, letters |
| Bicycle | Small parcels, food | Lunches, flowers |
| Motorcycle | Urgent cargo up to 5 kg | Spare parts, documents |
| Car | Large items, multiple boxes | Furniture, electronics |
On the frontend, implement this as an extra step during delivery selection or automatically based on product dimensions.
Error Handling
| HTTP Status | Error Code | Cause | Solution |
|---|---|---|---|
| 400 | INVALID_PARAMETER | Invalid vehicle_type_id or empty address | Validate on the frontend |
| 401 | UNAUTHORIZED | Invalid token | Check X-User-Token in your cabinet |
| 409 | ORDER_EXISTS | Order with that client_order_id already exists | Use unique identifiers |
| 429 | TOO_MANY_REQUESTS | Request limit exceeded | Implement caching or reduce frequency |
| 500 | INTERNAL_ERROR | Temporary server failure | Retry after 3 seconds |
Turnkey Integration Includes
- Requirements analysis and API key setup
- Delivery cost calculation on the website
- Order form with transport type selection
- Courier tracking on a map
- Webhook notifications for status changes
- Testing and debugging in sandbox environment
- Documentation and handover of access
Work Stages
- Analysis and design — 1 day. Gather requirements, connect sandbox.
- Integration development — 2–3 days. Implement calculation, order creation, tracking.
- Testing and deployment — 1 day. Check all scenarios, including API errors.
Integration Timeline
Basic integration with calculation and order creation takes 2 to 3 business days. With map tracking and webhook handling, it takes 4 to 5 days. Exact timelines depend on your project's complexity. For example, for a coffee shop chain we integrated in 3 days, reducing delivery time by 30%.
Our experience (10+ years in web development, 15+ courier service integrations) guarantees reliability and on-time delivery. Get your project evaluated — we will suggest the best solution. Contact us to assess your project — we'll propose the optimal solution.