Skip to main content
The Let’s Do This Public API provides a REST interface for the data you use to plan, promote, and run events. Requests and responses use JSON.
Keep your API key secret. Do not share it or include it in a public website, mobile app, or client-side application.

Get an API key

Create an API key from the Settings → Credentials section of your Let’s Do This account. Contact your Let’s Do This representative if you cannot access this section. If an API key is exposed, revoke it from the same section and create a replacement. An API key works on its own organization’s data. Endpoints return and change only your events, bookings, participants and other records, so their pages say “your” rather than repeating it. The marketplace events list is the exception: it lists events across Let’s Do This.

Send your first request

Include your API key as a bearer token in the Authorization header:
Use the production server for live data and the staging server when testing an integration.
The code samples on endpoint pages are copyable but do not send requests from this documentation site. This prevents API keys from passing through a documentation proxy.

Paginated responses

List endpoints return results in data and pagination information in page:
To get the next page, send page.next from the response as page[after]. Keep going until next comes back empty. page.prev works the same way with page[before]. Treat cursors as opaque strings. page[size] sets how many results come back per page. Most lists allow 1 to 500 and return 100 by default. A few use smaller pages, such as add-ons at up to 50, so check page[size] on each endpoint for its range and default. The marketplace events list pages differently: set the page size with pageSize, and send page.last as cursor[after] to get the next page.

Optional features

Some endpoints accept a comma-separated features query parameter. Features add fields or behavior for one request without changing the default response contract. For example:
Each endpoint page lists the feature values it supports.

Error responses

Rate limiting

Every import endpoint, the registration-status check and the timing ingest endpoint are rate limited, so a request to one can be rejected with a 429:
  • POST and PUT /v0/bookings/line-items/import
  • POST and PUT /v0/add-ons/import
  • POST /v0/bookings/import
  • POST /v0/credits/import
  • POST /v0/discount-codes/import
  • POST /v0/opt-ins
  • POST /v0/referrals/import
  • POST /v0/reserved-entries/participants/import
  • POST /v0/teams/import
  • POST /v0/membership-waitlist-entries/{entryId}/select
  • POST /v0/event-occurrences/{id}/registration-status
  • POST /timing-inbound/v1
Limits apply per API key and per endpoint, so a burst against one import does not consume the allowance of another. The registration-status check also carries a daily quota per key on top of its burst limit; its reference page states both numbers. A few endpoints outside this list carry their own, separate allowances — the x-ratelimit-* headers on a response are what tell you a limit applies, so treat 429 as a response any endpoint can return. Sequential requests are unlikely to be affected. Sending requests in parallel, which is the natural way to drive a bulk import, is what exhausts an allowance. Every response from these endpoints reports the current state of your allowance: A rejected request also returns a retry-after header with the number of seconds to wait:
Treat these headers as the authoritative source rather than hard coding a figure. Which endpoints are limited, and how generous each allowance is, can change.
Handle a 429 by waiting for the period given in retry-after and retrying. A rejected request is never processed, so retrying it is safe — no import is partially applied because of a rate limit.

OpenAPI schema

You can download the OpenAPI schema to use with tools such as Postman or an OpenAPI client generator. See the API changelog before upgrading an existing integration.