Direct API
Your backend creates a delivery the moment an order is ready and gets an id back to hold onto. Retries are safe: send the same job twice and you get the same delivery, never two drivers at the door.
Integrations
Get jobs in. Get every update back.
Estoul is the delivery layer under whatever you already run on. There are four ways to hand it a job and one stream of updates that keeps both sides telling the same story.
Four ways to hand Estoul a delivery
Start with the one that matches how you work today. Most operators move from one to the next as volume grows.
Event stream
Assigned, collected, arriving, delivered, failed — every change is pushed to your endpoint as it happens, with a catch-up path so a deploy during peak never costs you a status.
Bulk import
A spreadsheet or a scheduled file drop for operations that plan the day in batches. Your column mapping is saved, so tomorrow it is one click.
Straight into the console
No integration at all. Your team creates jobs in Estoul directly, which is how most operators run their first week while the connection is being built.
What crosses the line
Estoul asks for what it needs to execute a delivery and nothing about your customer that it does not.
What you send
- Where the pickup is, and who to ask for when the driver arrives
- Where it is going, and the contact at the door
- When it is ready, and when it was promised
- Your own reference, so both systems agree on what this is
- What is being carried, when the vehicle or the handling matters
What you get back
- The delivery id, the moment it is accepted
- Every status change, with the time it actually happened
- The assigned driver, and where they are right now
- An arrival time that updates as the street changes
- Verified proof of delivery when the job closes
What the integration does for you
Messy order data becomes a deliverable job
Addresses are resolved on the way in
You send what your customer typed. Estoul turns landmarks, building names and half-sentences of directions into a drop point, and asks your team only when it genuinely cannot tell.
Duplicates are caught before a driver moves
The same order arriving twice from a retrying system is recognised as one delivery rather than two, which is the difference between a safe retry and an angry merchant.
Bad jobs come back immediately
A dropoff outside the areas you cover, a time window nobody can make, a missing contact — rejected at the moment you send it, with a reason your developers can act on.
What it takes to start
Integration is a week of work at the outside, and usually an afternoon.
The full reference, field by field, comes with your sandbox.
- A sandbox on day one, with test drivers you can move around a map.
- Credentials scoped to your organisation, issued by us rather than self-served.
- A shared channel with the people who built this, not a ticket queue.
- A test plan that covers the ugly cases: retries, cancellations, failed attempts.
See Estoul on your own operation
Tell us how many drivers you run and where they run, and we will walk you through what a day on Estoul looks like for your team.