Skip to main content

​
API Versioning

PCI Booking does not version its API. There is a single API endpoint and all changes are backwards compatible. You do not need to specify a version number, pin to a version, or migrate between versions. When new features are added, they are made available at the same base URL:
New fields may be added to response objects over time. Your integration should ignore unknown fields rather than failing on them. Existing fields, endpoints, and behaviors are not removed or changed in a breaking way. If a breaking change is ever required, PCI Booking will notify affected customers directly with migration guidance and a transition period.
Check the Changelog for recent feature additions and bug fixes.

​
Rate Limits

PCI Booking applies rate limits across the API. The limit is measured in requests per second and applies per account: all users and all API keys in your account share the same limit. Not every endpoint is rate limited, and the set of limited endpoints can change. Build your integration so that any call can handle a 429 response.

​
Rate limit behavior

  • The limit is measured per calendar second, for your account as a whole.
  • When the limit is exceeded, the API returns HTTP 429 Too Many Requests with a plain text message.
  • There are no Retry-After or X-RateLimit-* response headers. Wait at least one second before retrying.

​
Example 429 response