Skip to content
QuickE
Start free

API and webhooks

For the system that already runs your orders

If your orders live in an ERP, a warehouse system or an admin your own team wrote, a store connection is the wrong shape. The API is designed for that case: your system creates the shipment, asks where it stands, and is told the moment something changes, without anyone opening a second screen.

Start freeBook a demo

Connection status

On the roadmap

This connection is planned and not available yet. Nothing described below works today. Every line of it is how the connection will behave once we switch it on.

Book a demo and we will tell you the day it goes live.

What it will do once it is live

Create a shipment from your own system

Your system sends the delivery address, the contact, the payment type and the amount to collect, and gets back a shipment with its tracking reference. From that moment the order is in the dispatch queue with everything an order typed by hand would have, which means nobody in your office rekeys an order that already exists somewhere else.

Read where a shipment stands

Your system can ask for the current state of a shipment and the history behind it at any time, so your own customer service screen answers the question without anyone logging into QuickE. The answer is the same one the dispatch screen shows, because it is the same record.

Receive events instead of asking for them

Rather than polling all day, you give us an address to notify and we send you the moments that change what you would tell a customer: the parcel is on its way, it was delivered, it was refused at the door, it is coming back, the cash was collected. If your endpoint is down, delivery is retried on a schedule, and the state can always be read back, so a missed notification is a delay rather than lost data.

A retry never books the same order twice

Writes are idempotent. Your system attaches its own reference to a request, and if the network drops after we received it but before your side saw the answer, sending the same request again returns the same shipment instead of creating a second one. That is the difference between a clean retry and two parcels at a customer door with two amounts to collect.

Test before it reaches a real driver

Access will be issued as keys you can rotate, with a test environment separate from the one your drivers work in, so an integration can be built and rehearsed without a test order appearing on a real driver route. Every request your system makes is recorded, which is how an argument about what was sent gets settled in a minute.

Questions operators ask

Can my developer build against it today?
No. The API is on the roadmap and is not available yet, and there is no documentation to hand out until it is. Book a demo, tell us what your system needs to send and receive, and we will tell you when access opens.
Do I need the API if I sell on Salla, Zid, Shopify or WooCommerce?
Probably not. Those store connections are designed to cover the standard flow without code, and each carries its own status on the integrations page. The API is for a system that is not one of them, or for a flow the standard connection does not cover.
What does idempotent mean for my operation?
It means a timeout is safe. When your system is not sure whether a shipment was created, it can send the request again and get the original shipment back rather than a duplicate, so a bad connection never turns into a second parcel and a second amount to collect.
What happens if my system is down when an event fires?
The notification is retried on a schedule, and the current state of any shipment stays readable, so once your system is back it can catch up by asking rather than by waiting for something that already passed.
Will the COD figures come through it?
That is the intent. The amount to collect goes out with the shipment and the amount actually collected comes back with the delivery event, so your accounts can reconcile against your own order numbers without an export in between.

Tell us what your system needs

The shape of this API is decided by the operations that use it. Book a demo, walk us through what your system holds and what it needs back, and we will tell you how access works.

Start freeBook a demo