With your permission, we use Google Analytics to understand visits, demo views, and signups. Optional analytics stays off until you accept. Essential cookies keep the site working.

Privacy policy

Developers

Business API

Read your catering data from your own systems with scoped, read-only keys.

On this page

The Business API lets your own server read bookings, meals, orders, invoices and more from CaterCamp. Every endpoint is read-only. It is available on the Business plan and during the free trial.

Create and revoke keys in Settings → Business API. Workspace owners and administrators with settings access can manage keys.

Keys and permissions

  • Each key has the permissions (scopes) you choose and a data boundary: the whole workspace, or selected operating locations (with or without unassigned work).
  • A key is shown once. CaterCamp stores only a hash, so a lost key cannot be recovered. Create a new key, switch your integration to it, then revoke the old one.
  • A key's permissions and locations cannot be edited later.
  • Every request rechecks the key's expiry, the workspace plan and the current role of the person who created it. Removing that person from the workspace stops their keys.
  • Keep keys on your server, in a secret manager. Never put a key in a browser, mobile app, URL or code repository.

Making requests

Send GET requests with the key in an Authorization header:

GET https://catercamp.com/api/v1/events?limit=50
Authorization: Bearer <your API key>
  • Dashboard sign-in cookies do not work for the API, and cross-origin browser access is not enabled.
  • Responses are JSON, private, no-store, and include an X-Request-Id header. Errors return an error code and message with the same request ID.
  • The current API version is 2026-10-24.

Pagination and limits

  • Lists return 50 records by default, up to 100 with limit. Follow the opaque after cursor from each page until next is null. Keep the same filters when following a cursor.
  • Lists read current data, not a frozen export, so a long sync may need another pass.
  • Detail endpoints accept no query parameters.
  • Rate limits: 60 requests per key and 300 per workspace per UTC minute. A 429 response includes Retry-After.

Endpoints by permission

PermissionEndpoints
clients:read/api/v1/clients, /api/v1/clients/:id
events:read/api/v1/events, /api/v1/events/:id, /api/v1/events/:id/meals/:serviceId, /api/v1/meals?from=YYYY-MM-DD&through=YYYY-MM-DD
orders:read/api/v1/events/:id/order
guarantees:read/api/v1/events/:id/guarantee
instructions:read/api/v1/events/:id/instructions, /api/v1/events/:id/instructions/:publicationId
proposals:read/api/v1/events/:id/proposals, /api/v1/events/:id/proposal-declines, /api/v1/events/:id/proposal-declines/:noticeId
online-requests:read/api/v1/online-requests, /api/v1/online-requests/:id
corporate-requests:read/api/v1/corporate-requests, /api/v1/corporate-requests/:id, /api/v1/corporate-requests/:id/occurrences
event-requests:read/api/v1/event-requests, /api/v1/events/:id/change-requests, /api/v1/events/:id/change-requests/:requestId
delivery:read/api/v1/deliveries, /api/v1/events/:id/deliveries
pickups:read/api/v1/pickups, /api/v1/events/:id/pickups, /api/v1/events/:id/pickups/:pickupId
invoices:read/api/v1/invoices, /api/v1/invoices/:id
catalogue:read/api/v1/branches, /api/v1/branches/:branchId/catalogue
webhooks:read/api/v1/webhook-endpoints/:id/notices

Multi-day bookings and meals

  • An event includes its active dated meals and its operating location and brand. Meal dates and times are local to the event.
  • /api/v1/events/:id/meals/:serviceId returns one current meal, for example one named in a meal-schedule webhook.
  • /api/v1/meals?from=…&through=… lists scheduled meals across bookings for an inclusive range of up to 31 days.
  • Order lines carry their meal ID when assigned. Prices are integer minor units (for example cents). Only included lines count toward the order total. The order is the current working order, not a signed contract or invoice.

Location-limited keys

A key limited to locations only returns work currently assigned to those locations (plus unassigned work if you chose it). Filtering happens before pagination, and query parameters cannot widen the boundary. Standalone invoices need a whole-workspace key.

Invoices

invoices:read must be chosen explicitly. Filter /api/v1/invoices by eventId, clientId or both. An invoice is returned only when the key can access every booking connected to it, so a short or empty page can still have a next cursor. Applied amounts include credits, so they do not mean cash collected.

What the API never returns

Internal notes, ingredient costs, mailbox content, dietary or medical profiles, credentials, files, payment provider references and raw financial ledgers. Customer contact details are only returned by clients:read.

Change notifications

To learn when something changes instead of polling, set up signed webhooks, then fetch the current record with a key that has the matching permission.

Try it with your next real event

Fourteen days with every Business feature. Add one booking, one menu and your team, then choose the plan that fits.

Start your free trial