Orders in your POS, delivery in kuryenoktam
Your POS sends the order; status changes come back as signed notifications.

In short
The kuryenoktam integration works both ways. The POS sends orders with a restaurant-specific API key; if its own order number arrives again, no new record is created. As delivery status changes, kuryenoktam sends an HMAC-signed notification to the POS and retries at growing intervals if it is not delivered.
How do you connect?

1
API key
A key is generated per restaurant in the panel and can be rotated.

2
Send orders
The POS sends orders with its own number; the same number never opens a second record.

3
Webhook URL
Set the POS webhook URL and signing secret in the restaurant settings.

4
Signed status
Each notification is signed over timestamp and body; order is kept per delivery.
Webhook behaviour
| Topic | Behaviour |
|---|---|
| Signature | sha256 HMAC over timestamp + body |
| Retries | 7 times at growing intervals, then marked failed |
| Ordering | Notifications for the same delivery are sent in order |
| Uniqueness | One notification per status |
What can connect
Any system that can make HTTP requests through its API can connect.

POS systems
Restaurant tills that create delivery orders. The AssistOPOS connection is in progress.

Your own app
The restaurant's own ordering site or app.

Trendyol Go food
Connect the restaurant's Trendyol Go account; new orders are fetched at regular intervals and land in the queue.

Restaurant portal
Restaurants without an integration enter orders in the portal.
Try it with your own fleet.
Let's set up your restaurants, couriers and order flow together. See the real screens in a demo account.
