Skip to content
Office

Office Pay feature

API and webhooks

Signed webhooks for every event, CSV exports of everything, and an API to read your data.

Webhooks for every event

Get a signed POST to your URL when a checkout completes, a payment succeeds, fails, needs authentication or is returned, a plan is created, completed, cancelled, goes past due or resumes, a dispute opens, or a link is created or turned off. Failed deliveries are retried. Point them at Zapier, Make or n8n with a catch hook, or at your own server.

API and exports

With an API key, read links, plans, payments and customers. Creating links, prefilled checkouts and plan actions through the API is coming soon, along with an MCP connector so your assistant can make a payment request or check who's behind.

Export plans, payments, customers and checkout answers as CSV from any filtered list.

Example

Unlocking a course after payment

A course creator listens for pay.plan.created to give a buyer access and pay.plan.past_due to pause it. The webhook carries the plan's access flag, so the course doesn't need to work out the rules itself. When the customer settles up, pay.plan.resumed turns access back on.

How to set it up

  1. 1

    Open Settings, then Webhooks, and add your endpoint URL.

  2. 2

    Pick the events you want.

  3. 3

    Create an API key under API keys if you want to read data.

API and webhooks is part of Office Pay and included on every plan.

Try Office Pay with your whole team

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