Skip to content
Public API & Webhooks

A REST API and signed webhooks.

Read locations, items and availability, create customers, and create, change and cancel bookings over a public REST API, documented in an OpenAPI 3.1 spec. Signed webhooks tell your systems when bookings, payments and the catalog change. API keys and webhook subscriptions are not self-serve today.

How it works

Three steps, start to finish.

01

Read the spec

The OpenAPI 3.1 document and an interactive reference are public, and the API reference page shows an illustrative request.

02

Call the API

Send the key in the x-api-key header or as a bearer token. Each key has a per-minute rate limit, and keys are stored only as hashes.

03

Receive webhooks

Each delivery carries an X-GoGo-Signature header with a timestamp and an HMAC-SHA256 signature, failed deliveries are retried with backoff, and admins see recent deliveries on the Connections page.

Capabilities

The details your team works with.

Bookings and checkout

Create customers and bookings, update or cancel bookings, check them in and out, and run quotes and checkout sessions.

Events that fire

Booking, payment, new-customer, location and catalog changes send webhooks.

Choose the events

Admins choose which events an existing webhook subscription receives.

Not self-serve today

There is no screen to create an API key or a webhook subscription today.

Keep exploring

Pairs well with.

All features