DevelopersChanges data

accept_request

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

What it does

Mark one open service request as accepted - somebody is on it. The customer's thread is notified automatically with a fixed line that promises NO arrival time; never add one yourself. Any staff member already assigned stays assigned. Refused when the request is not open.

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

Parameters

business_idstringrequired

The id returned by list_businesses.

request_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_request","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87","request_id":"r90b…"}}}'

Response

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

{
  "request": {
    "id": "r90b…",
    "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"