Skip to content
Office

Office Chat feature

Webhooks and REST API

Get a signed POST when something happens in chat, and read or write conversations and contacts with an API key.

Webhooks

Pick the events you want: conversation created, assigned, closed and reopened, message created (visitor, agent or note), contact created and updated, and rating created. Each delivery is JSON signed with a per-endpoint secret in an X-Signature: sha256=... header. Failed deliveries retry after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours, and the delivery log shows every response code with a Resend button.

REST API

Create named API keys with an optional expiry (shown once). List, read, reply to, note, assign and close conversations; list, read, create, update and delete contacts; read messages. Cursor pagination, one error format, and a limit of 120 requests a minute per key. The docs have curl examples for every endpoint.

Zapier, Make and n8n

Point a "Webhooks by Zapier" trigger (or Make, or n8n) at a webhook endpoint and you can send new chats anywhere those tools reach, with no app to install.

Example

Every rating in a spreadsheet

An online course company adds a webhook endpoint for rating.created pointed at a Make scenario. Each rating, comment and conversation link lands as a row in a Google Sheet the founder reviews on Fridays. When Make was down for an hour, the delivery log showed the failed attempts and the retries delivered everything once it came back.

How to set it up

  1. 1

    Open Settings > Webhooks, add your URL and choose events.

  2. 2

    Copy the signing secret and verify the signature on your server.

  3. 3

    For the API, create a key under Settings > API keys.

Webhooks and REST API is part of Office Chat and included on every plan.

Try Office Chat with your whole team

7-day trial with every feature. Cancel from the billing page whenever you like.