Changelog

Review requests report their real channel4 October 2026

• fixed

  A review request sent on personal WhatsApp, email or website chat now reports that channel and its `conversation_id`. It used to report `whatsapp` with no conversation, although the message was delivered. `channel` can therefore be any conversation channel.

  • POST/api/v1/review-requests
  • GET/api/v1/review-requests/{id}
  • GET/api/v1/review-requests

Bookings, segments, reviews and business hours4 October 2026

Four parts of the product that had no API get one: put a customer in the diary from your own website, keep a contact list in step, ask for a review when a job is done, and read or set when the business is open.

• added

  Bookings: list what can be booked and with whom, read the free slots, create a booking for an existing contact or one found by phone, reschedule or reassign it, move it forward, and cancel it. A booking is only accepted at a time the slots endpoint offers, so the API cannot book outside working hours.

  • GET/api/v1/booking-types
  • GET/api/v1/bookable-members
  • GET/api/v1/bookings/slots
  • GET/api/v1/bookings
  • POST/api/v1/bookings
  • GET/api/v1/bookings/{id}
  • PATCH/api/v1/bookings/{id}
  • POST/api/v1/bookings/{id}/cancel
• added

  Segments: list, create, rename and delete saved contact lists, page through the contacts in one, and add or remove contacts. The id is what a broadcast audience or an assistant trigger takes as `segment_id`. Uses the existing contacts:read and contacts:write scopes.

  • GET/api/v1/segments
  • POST/api/v1/segments
  • GET/api/v1/segments/{id}
  • PATCH/api/v1/segments/{id}
  • DELETE/api/v1/segments/{id}
  • GET/api/v1/segments/{id}/contacts
  • POST/api/v1/segments/{id}/contacts
  • DELETE/api/v1/segments/{id}/contacts/{contact_id}
• added

  Reviews: send a contact a review request, follow it from sent to clicked to completed, and read the ratings and answers that came back, along with the forms and review platforms the account has set up.

  • GET/api/v1/reviews
  • GET/api/v1/reviews/{id}
  • GET/api/v1/review-requests
  • POST/api/v1/review-requests
  • GET/api/v1/review-requests/{id}
  • GET/api/v1/review-forms
  • GET/api/v1/review-platforms
• added

  Business hours: read the account’s time zone, weekly hours and whether it is open now, and set them. A change applies at once to assistant schedules, website chat availability and broadcast send windows.

  • GET/api/v1/business-hours
  • PUT/api/v1/business-hours
• added

  Six scopes: bookings:read and bookings:write, reviews:read and reviews:send, account:read and account:write. In each pair the second implies the first.

• changed

  The booking object in the booking.created, booking.cancelled and booking.completed webhook events gains `notes` and `updated_at`, and `source` can now be `api`. It is the same object GET /bookings/{id} returns.

• fixed

  The OpenAPI document now lists every webhook event under its top-level `webhooks` key. The events were always delivered; the document had left them out.

AI assistants3 September 2026

The assistant layer joins the API: configure assistants, start runs and watch them, and answer the approvals they raise.

• added

  Assistants, with their tool grants, schedule, channel bindings and delegation policy.

  • GET/api/v1/assistants
  • POST/api/v1/assistants
  • GET/api/v1/assistants/{id}
  • PATCH/api/v1/assistants/{id}
  • DELETE/api/v1/assistants/{id}
• added

  Granting tools to an assistant, with `enabled` resolved against each tool’s catalogue default — so the answer is what the assistant can do, not merely what was overridden.

  • GET/api/v1/assistants/{id}/tools
  • PUT/api/v1/assistants/{id}/tools
• added

  The tool catalogue, and the instruction library assistants draw their standing guidance from.

  • GET/api/v1/tools
  • GET/api/v1/instructions
  • POST/api/v1/instructions
  • GET/api/v1/instructions/{id}
  • PATCH/api/v1/instructions/{id}
  • DELETE/api/v1/instructions/{id}
  • GET/api/v1/assistants/{id}/instructions
  • PUT/api/v1/assistants/{id}/instructions
• added

  Memories — what an assistant has learned about the account, another assistant or one contact. Written on the natural key, so the same key twice updates rather than duplicates.

  • GET/api/v1/memories
  • POST/api/v1/memories
  • DELETE/api/v1/memories/{id}
• added

  Triggers: what wakes an assistant on a schedule, on a CRM event, or when another system calls in. Preview resolves the audience and spends nothing; firing starts runs and does.

  • GET/api/v1/triggers
  • POST/api/v1/triggers
  • GET/api/v1/triggers/{id}
  • PATCH/api/v1/triggers/{id}
  • DELETE/api/v1/triggers/{id}
  • POST/api/v1/triggers/{id}/token
  • POST/api/v1/triggers/{id}/preview
  • POST/api/v1/triggers/{id}/run
• added

  Runs. Starting one returns 202 with a queued run — poll it, or subscribe to assistant.run_completed. The event feed is the whole timeline: every tick, message, tool decision and handoff.

  • GET/api/v1/runs
  • POST/api/v1/runs
  • GET/api/v1/runs/{id}
  • POST/api/v1/runs/{id}/cancel
  • GET/api/v1/runs/{id}/events
• added

  Human approvals. A run that needs a decision parks until somebody answers or the timeout rule fires, and holds that conversation’s run slot while it waits.

  • GET/api/v1/asks
  • GET/api/v1/asks/{id}
  • POST/api/v1/asks/{id}/answer
• added

  AI spend and the monthly budget, in billed figures that match the invoice.

  • GET/api/v1/ai/usage
  • GET/api/v1/ai/budget
• added

  Seven scopes: assistants:read and :write, runs:read and :start, asks:read and :answer, and ai:usage. A run bound to a contact can reply on your channels, so runs:start says so in its description.

Inquiries3 September 2026

A website contact form can now post straight into the Raabta HQ inbox. Submissions land in Inquiries in the dashboard, notify the team, and fan out to any webhook endpoint subscribed to them.

• added

  Inquiries: submit an inquiry from your own form backend, list and filter the inbox, read one, move it through triage, delete it, and list or add internal notes.

  • GET/api/v1/inquiries
  • POST/api/v1/inquiries
  • GET/api/v1/inquiries/{id}
  • PATCH/api/v1/inquiries/{id}
  • DELETE/api/v1/inquiries/{id}
  • GET/api/v1/inquiries/{id}/notes
  • POST/api/v1/inquiries/{id}/notes
• added

  Two scopes: inquiries:read and inquiries:write. As everywhere else, write implies read.

• added

  Two webhook events: inquiry.created, delivered as the submission arrives, and inquiry.status_changed.

Public API v12 September 2026

The first public release of the REST API: seven resources, cursor pagination on every list, Idempotency-Key on every create, and an OpenAPI 3.1 document generated from the same definitions these pages are.

• added

  GET /me — identify a key, its account, and the scopes it can exercise.

  • GET/api/v1/me
• added

  Contacts: list, create, get and update contacts; add and remove tags; set custom-field values; list and add notes; list tags, create tags and list custom-field definitions.

  • GET/api/v1/contacts
  • POST/api/v1/contacts
  • GET/api/v1/contacts/{id}
  • PATCH/api/v1/contacts/{id}
  • POST/api/v1/contacts/{id}/tags
  • DELETE/api/v1/contacts/{id}/tags/{tag_id}
  • PUT/api/v1/contacts/{id}/custom-fields
  • GET/api/v1/contacts/{id}/notes
  • POST/api/v1/contacts/{id}/notes
  • GET/api/v1/tags
  • POST/api/v1/tags
  • GET/api/v1/custom-fields
• added

  Conversations: list and get threads, list their messages, change status or assignment, mark read, hand over to a human, return to the assistant, and list team members.

  • GET/api/v1/conversations
  • GET/api/v1/conversations/{id}
  • GET/api/v1/conversations/{id}/messages
  • PATCH/api/v1/conversations/{id}
  • POST/api/v1/conversations/{id}/read
  • POST/api/v1/conversations/{id}/takeover
  • POST/api/v1/conversations/{id}/return-to-ai
  • GET/api/v1/members
• added

  Messages: send a text, template or media message to a thread or a phone number, and read one message with its delivery status.

  • POST/api/v1/messages
  • GET/api/v1/messages/{id}
• added

  Templates: list and get approved WhatsApp message templates.

  • GET/api/v1/templates
  • GET/api/v1/templates/{id}
• added

  Broadcasts: create and send a template campaign, list and get campaigns, list per-recipient delivery, and cancel a scheduled one.

  • POST/api/v1/broadcasts
  • GET/api/v1/broadcasts
  • GET/api/v1/broadcasts/{id}
  • GET/api/v1/broadcasts/{id}/recipients
  • POST/api/v1/broadcasts/{id}/cancel
• added

  Pipelines and deals: list pipelines with their stages; list, create, get, update, move, close, reopen and delete deals.

  • GET/api/v1/pipelines
  • GET/api/v1/deals
  • POST/api/v1/deals
  • GET/api/v1/deals/{id}
  • PATCH/api/v1/deals/{id}
  • POST/api/v1/deals/{id}/move
  • POST/api/v1/deals/{id}/close
  • POST/api/v1/deals/{id}/reopen
  • DELETE/api/v1/deals/{id}
• added

  Webhooks: register HTTPS endpoints, subscribe them to events, rotate a signing secret, send a test ping, and inspect or redeliver individual deliveries.

  • GET/api/v1/webhooks
  • POST/api/v1/webhooks
  • GET/api/v1/webhooks/{id}
  • PATCH/api/v1/webhooks/{id}
  • DELETE/api/v1/webhooks/{id}
  • POST/api/v1/webhooks/{id}/rotate-secret
  • POST/api/v1/webhooks/{id}/test
  • GET/api/v1/webhooks/{id}/deliveries
  • GET/api/v1/webhooks/{id}/deliveries/{delivery_id}
  • POST/api/v1/webhooks/{id}/deliveries/{delivery_id}/redeliver
• added

  The OpenAPI 3.1 document at /api/v1/openapi.json, generated from the endpoint registry.