Accept Order

Accept a new order and set preparation time

PUT /orders/accept/{order_id}

Accept Order

cURL

curl --request PUT \
  --url https://www.xn--dkkango-n2a.com/api/integrations/orders/accept/{order_id} \
  --header 'Access-Token: <api-key>' \
  --header 'Content-Type: <content-type>' \
  --data '
{
  "preparing_time": 123
}
'

Missing Field (422)

{
  "status": false,
  "error": "eksik alan",
  "message": "preparing_time is required"
}

Overview

Accepts an order that’s in RECEIVED status and changes it to CONFIRMED. You must provide the estimated preparation time in minutes.

Path Parameters

order_id · string · required

Order’s payment_key (UUID) from the /get-current response

Headers

Access-Token · string · required

Your API access token

Content-Type · string · required

Must be application/json

Body Parameters

preparing_time · integer · required

Estimated preparation time in minutes (e.g., 30)

Response

status · boolean

true if successful

data · string

"OK" on success

Examples

cURL

curl -X PUT https://www.xn--dkkango-n2a.com/api/integrations/orders/accept/3e9caf87-5cb7-4c4e-adcb-fc2ec54cf24e \
  -H 'Access-Token: your-access-token' \
  -H 'Content-Type: application/json' \
  -d '{"preparing_time": 30}'

Success Response (200)

{
  "status": true,
  "data": "OK"
}

Error Responses

Missing Field (422)

{
  "status": false,
  "error": "eksik alan",
  "message": "preparing_time is required"
}

Status Transition

RECEIVED (status_id: 1)
    ↓
[/orders/accept called]
    ↓
CONFIRMED (status_id: 2)

After accepting, the order status history is automatically updated by the database trigger.

Integration Flow

1. Receive Order

   Get order from /orders/get-current with status_id: 1

2. Acknowledge

   Call /orders/success/{payment_key} to acknowledge receipt

3. Review

   Staff reviews order details and decides to accept/reject

4. Accept

   Call /orders/accept/{payment_key} with estimated prep time

5. Prepare

   Kitchen prepares the order

Preparation Time Guidelines

How to Calculate

Consider:

• Current kitchen load
• Order complexity (number of items, modifiers)
• Time of day
• Staff availability

Recommended Values

• Simple orders: 15-20 minutes
• Medium orders: 25-35 minutes
• Complex orders: 35-45 minutes
• Peak hours: Add 10-15 minutes buffer

Impact on Customer

The preparation time is communicated to the customer and affects:

• Estimated delivery time
• Courier dispatch timing
• Customer satisfaction

Always use the payment_key (UUID) from the order object, not the id (integer).

Related Endpoints

Get Current Orders

Fetch orders to accept

Cancel Order

Reject/cancel order instead

Mark On The Way

Next step after preparation

Order Lifecycle

Complete order flow