DevelopersChanges data

confirm_booking

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

What it does

Confirm a PENDING hold - the step that turns a hold into a real booking and stops its expiry clock. Only works on a pending booking; anything else returns a readable refusal. Confirm with the human first, and never claim a booking is confirmed unless this tool returned the confirmed row. It does NOT take payment and does not change payment state.

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":"confirm_booking","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": "confirmed",
    "confirmedAt": "2026-08-16T03:20:00.000Z"
  }
}

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"