DevelopersChanges data

accept_order

API reference — one of six tools an AI assistant can call on an Avrosh account.

What it does

Mark one pending order as accepted - the kitchen or counter has it. The customer's chat thread is notified automatically in their own language; do NOT also compose a message, and never promise a delivery time. Refused when the order is not pending (someone else already moved it).

This is the exact text the model reads before deciding to call.

Parameters

business_idstringrequired

The id returned by list_businesses.

order_idstringrequired

From list_work_queue.

Request

curl -X POST https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"accept_order","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87","order_id":"o71a…"}}}'

Response

The result arrives as an MCP content block; the JSON below is what the text field parses to.

{
  "order": {
    "id": "o71a…",
    "status": "accepted"
  }
}

Authentication

Every request carries Authorization: Bearer avk_…. Create a key in the Avrosh dashboard under Docs; it is shown once, because only its hash is stored.

One key reaches every business on the account that made it, and no others. There are no scopes to configure and nothing to switch on — a connected assistant receives the whole toolset. What bounds it is whose account the key belongs to, which is enforced in the database rather than by a permission anybody sets.

curl https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY"