Acknowledge Order
Orders
Acknowledge Order
Mark order as received/acknowledged
PUT
Acknowledge Order
Overview
Marks an order as successfully received and acknowledged by your POS system. This prevents the order from repeating in subsequent/get-current calls.
Path Parameters
Order’s
payment_key (UUID) from the /get-current responseHeaders
Your API access token
Response
true if successful"OK" on successExamples
Success Response (200)
Error Responses
Order Repetition Behavior
Key Concept: Orders repeat in
/get-current responses until acknowledged with this endpoint.Example Timeline
Why This Matters
Prevents Duplicate Processing
Prevents Duplicate Processing
Without acknowledgment, the same order appears in every
/get-current call, risking duplicate imports into your POS.Ensures Reliability
Ensures Reliability
If your POS crashes after receiving an order but before acknowledging it, the order will reappear when you restart.
Status Change Tracking
Status Change Tracking
When an order’s status changes (RECEIVED → CONFIRMED → IN_DELIVERY), it appears again so you can track the progression.
When to Call
Integration Pattern
Best Practices
- ✅ Good
- ❌ Bad
Error Handling
Common Issues
Order keeps appearing in get-current
Order keeps appearing in get-current
Cause: Order hasn’t been acknowledged.Solution:
- Verify you’re calling
/successafter importing - Check for errors in the API response
- Ensure you’re using
payment_key(UUID), notid(integer)
Using wrong order ID
Using wrong order ID
Cause: Using
id (integer) instead of payment_key (UUID).Solution:Order disappeared after acknowledge
Order disappeared after acknowledge
Cause: Order was acknowledged and status didn’t change yet.Solution: This is expected behavior! Order will reappear when status changes.
Related Endpoints
Get Current Orders
Fetch orders to acknowledge
Accept Order
Accept order after acknowledging
Order Lifecycle
Complete order flow guide