DevelopersChanges data

mark_no_show

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

What it does

Record that the customer never came. This RELEASES the slot back into availability, the same as a cancellation, so do not use it as a note-to-self while you are still waiting for someone. It is kept as its own outcome rather than folded into 'cancelled' because for many businesses the difference decides whether a fee applies, and nobody can tell the two apart from a status afterwards. Allowed while the booking is confirmed or checked in.

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

Parameters

business_idstringrequired

The id returned by list_businesses.

booking_idstringrequired

From list_bookings.

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":"mark_no_show","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87","booking_id":"b901…"}}}'

Response

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

{
  "booking": {
    "id": "b901…",
    "status": "no_show"
  },
  "releasedInventory": true
}

Connecting

Paste the URL into your assistant and log in. Avrosh implements OAuth 2.1, so an MCP client discovers the authorisation server, registers itself, and opens a browser asking you to sign in here. That is the whole setup: nothing to copy, no key to keep, and nothing to rotate later.

https://us.avrosh.com/mcp

For something with no browser to log in with — a cron job, a script, an automation platform — there is a second door: a bearer key made in the dashboard under Docs, shown once because only its hash is stored, and revocable at any time.

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

Either way the boundary is the same one: an assistant reaches every business on the account it signed in to, and no others. There are no scopes to configure and nothing to switch on — what bounds it is whose account it is, enforced in the database rather than by a permission anybody sets.