set_appointment_end

writes

One of the tools an AI assistant can call on an Avrosh account.

What it does

Move a running appointment's expected end time, taking the occupied window with it so later slot offers stay truthful. Appointments only, and only while confirmed or checked in. Give the FULL new end time (get_booking returns the current one as endAt) - not a number of minutes: a nudge like '+15 minutes' repeated after a timeout becomes half an hour and drags the occupied window twice, whereas repeating an absolute time simply lands on the same answer. The move must be within four hours of the current end and can never fall closer than five minutes after the start. It does not move the start - rebook for that - and does not change the price.

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.

new_end_timestringrequired

The full new end instant, ISO 8601 with an offset, e.g. 2026-08-20T11:30:00+08:00.

Response

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

Connecting

Point any MCP client at https://us.avrosh.com/mcp and log in — OAuth 2.1, no key to paste.

The panel here uses the other door: a bearer key made in the dashboard, for a script or a cron job with no browser to sign in with. Both reach the same endpoint. Full notes on the reference overview.

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": "set_appointment_end",
      "arguments": {
        "business_id": "926135ac-487d-4367-8bad-25397d0d4b87",
        "booking_id": "b901…",
        "new_end_time": "2026-08-20T11:30:00+08:00"
      }
    }
  }'