DevelopersChanges data

assign_request

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

What it does

Hand one open or accepted service request to a specific team member, or send staff_id null to put it back in the shared pool. This OVERWRITES any existing assignee - it is the supervisor's correction, so confirm with the human before moving someone else's job. Staff ids come from the human; there is no staff list tool yet, so never guess one.

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.

staff_idstringoptional

The team member to hand it to. Omit or null = back to the pool.

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

Response

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

{
  "assigned": true
}

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"