Why is no API key needed?

Delivery's receipt lookup is a public method: it returns a waybill's state to anyone who knows its number. A key is needed only to create receipts, which we do not do yet — so we do not ask for one “just in case”.

Can the CRM create waybills?

Not yet. That needs a Delivery API key you issue yourself in their cabinet, and a separate piece of work. Today you issue the waybill at the carrier and the CRM follows its status.

How often does the status refresh?

Hourly, and only for shipments still on the move. Delivered, cancelled and returned parcels stop being asked about.

What happens with an unknown number?

Nothing. Delivery answers that there is no such receipt and the CRM leaves the shipment where it was — a mistyped number breaks neither the sync nor any other order.

Obriym CRMCustomer flow workspace

Shipping · Delivery (Делівері)

A Delivery parcel's status, inside the order

The waybill number stops being a dead string: the CRM asks Delivery every hour where the parcel is and moves the shipment itself. Connecting takes as long as typing a name.

Try it in a workspace All integrations

What it takes to connect

The one channel in the product that asks for no credentials at all.

API key: not required
Carrier account: not required
Contract with Delivery: not required
Waiting for access: nothing to wait for

What it does, and what it does not

The boundary is stated plainly so nobody waits for something that is not there.

Refreshes the status itself

Every hour it asks Delivery about each waybill whose shipment is still moving. Arrived, cancelled or lost parcels are never asked about again.

Does not care where the number came from

You created the waybill in Delivery's cabinet, a manager typed it in, or it arrived from a marketplace — the CRM follows it the same way.

Stamps dispatch and delivery dates

A delivery date is written only once the parcel was actually handed over. A planned arrival date does not count — that would make the order look closed.

Does not create waybills yet

Creating a receipt from the CRM needs a separate Delivery API key. That is the next step; today you issue the waybill at the carrier and the CRM follows it.

The carrier's official dictionary → the CRM shipment state

Mapped from dictionary 8.1 of Delivery's specification and aligned with Nova Poshta: “shipped” means the same thing for both carriers.

Registered (at the sending warehouse)	Shipped
In transit · At a transit warehouse · Redirected	In transit
Preparing courier delivery · Courier delivering	In transit
Available for pickup	Ready for pickup
Handed over · Partially handed over	Delivered
Cancelled	Cancelled
Disposed of · Sold	Failed

How to connect

1
Add the channel
Settings → Integrations → Platform adapters → Delivery. Enter a name; nothing else is asked.
2
Test the connection
The button makes a real request to Delivery and shows that the API answers. Until it passes, tracking does not run.
3
Put the waybill number on the shipment
In an order → “Shipments” pick the carrier “Delivery” and enter the receipt number. Nothing else to do.

Frequently asked

Why is no API key needed?: Delivery's receipt lookup is a public method: it returns a waybill's state to anyone who knows its number. A key is needed only to create receipts, which we do not do yet — so we do not ask for one “just in case”.
Can the CRM create waybills?: Not yet. That needs a Delivery API key you issue yourself in their cabinet, and a separate piece of work. Today you issue the waybill at the carrier and the CRM follows its status.
How often does the status refresh?: Hourly, and only for shipments still on the move. Delivered, cancelled and returned parcels stop being asked about.
What happens with an unknown number?: Nothing. Delivery answers that there is no such receipt and the CRM leaves the shipment where it was — a mistyped number breaks neither the sync nor any other order.

Let parcels report themselves

Connect Delivery in a minute and stop checking waybills by hand.

Start free

Obriym CRMCustomer flow workspace

Shipping · Delivery (Делівері)

A Delivery parcel's status, inside the order

The waybill number stops being a dead string: the CRM asks Delivery every hour where the parcel is and moves the shipment itself. Connecting takes as long as typing a name.

Try it in a workspace All integrations

What it takes to connect

The one channel in the product that asks for no credentials at all.

API key: not required
Carrier account: not required
Contract with Delivery: not required
Waiting for access: nothing to wait for

What it does, and what it does not

The boundary is stated plainly so nobody waits for something that is not there.

Refreshes the status itself

Every hour it asks Delivery about each waybill whose shipment is still moving. Arrived, cancelled or lost parcels are never asked about again.

Does not care where the number came from

You created the waybill in Delivery's cabinet, a manager typed it in, or it arrived from a marketplace — the CRM follows it the same way.

Stamps dispatch and delivery dates

A delivery date is written only once the parcel was actually handed over. A planned arrival date does not count — that would make the order look closed.

Does not create waybills yet

Creating a receipt from the CRM needs a separate Delivery API key. That is the next step; today you issue the waybill at the carrier and the CRM follows it.

The carrier's official dictionary → the CRM shipment state

Mapped from dictionary 8.1 of Delivery's specification and aligned with Nova Poshta: “shipped” means the same thing for both carriers.

Registered (at the sending warehouse)	Shipped
In transit · At a transit warehouse · Redirected	In transit
Preparing courier delivery · Courier delivering	In transit
Available for pickup	Ready for pickup
Handed over · Partially handed over	Delivered
Cancelled	Cancelled
Disposed of · Sold	Failed

How to connect

1
Add the channel
Settings → Integrations → Platform adapters → Delivery. Enter a name; nothing else is asked.
2
Test the connection
The button makes a real request to Delivery and shows that the API answers. Until it passes, tracking does not run.
3
Put the waybill number on the shipment
In an order → “Shipments” pick the carrier “Delivery” and enter the receipt number. Nothing else to do.

Frequently asked

Why is no API key needed?: Delivery's receipt lookup is a public method: it returns a waybill's state to anyone who knows its number. A key is needed only to create receipts, which we do not do yet — so we do not ask for one “just in case”.
Can the CRM create waybills?: Not yet. That needs a Delivery API key you issue yourself in their cabinet, and a separate piece of work. Today you issue the waybill at the carrier and the CRM follows its status.
How often does the status refresh?: Hourly, and only for shipments still on the move. Delivered, cancelled and returned parcels stop being asked about.
What happens with an unknown number?: Nothing. Delivery answers that there is no such receipt and the CRM leaves the shipment where it was — a mistyped number breaks neither the sync nor any other order.

Let parcels report themselves

Connect Delivery in a minute and stop checking waybills by hand.

Start free

A Delivery parcel's status, inside the order

What it does, and what it does not

Refreshes the status itself

Does not care where the number came from

Stamps dispatch and delivery dates

Does not create waybills yet

The carrier's official dictionary → the CRM shipment state

How to connect

Add the channel

Test the connection

Put the waybill number on the shipment

Frequently asked

Let parcels report themselves

A Delivery parcel's status, inside the order

What it does, and what it does not

Refreshes the status itself

Does not care where the number came from

Stamps dispatch and delivery dates

Does not create waybills yet

The carrier's official dictionary → the CRM shipment state

How to connect

Add the channel

Test the connection

Put the waybill number on the shipment

Frequently asked

Let parcels report themselves