API and developer terms

1. Scope

These terms apply to agencies and software vendors that use the CesiSync API (/v1), webhooks, OAuth apps and the sandbox, and supplement the Terms of use.

2. Keys and authorisation

API keys (bp_live_…, bp_test_…) and OAuth tokens are secret and must not be put in source code, client-side apps or public repositories. Create keys with only the scopes needed and, where possible, an IP allow-list. Revoke a leaked key immediately; the key owner is responsible for actions made with it.

A software vendor may access an agency's data only within the scope that agency granted through OAuth; when permission is withdrawn it stops access and deletes that agency's data.

3. Limits and fair use

Requests are subject to a per-key rate limit (reported in the RateLimit-* response headers). Using several keys to get around the limit is prohibited. For calendar synchronisation use webhooks and GET /v1/events rather than polling. Do not run availability searches more often than necessary.

4. Webhooks

Your webhook address must be public, HTTPS-capable and verify the signature (Standard Webhooks). Failed deliveries are retried for about three days; after 100 consecutive failures the endpoint is disabled. Events may be delivered more than once (at-least-once): make your handling idempotent by event id and detect gaps with property_seq.

5. Data use

Property, calendar, rate and contact data obtained from the API may be used only to sell and manage the properties you are subscribed to. When a subscription ends (subscription.revoked) you must stop showing that property's calendar and rates. You may not share the data with third parties, use it to train AI models or export it in bulk.

6. Sandbox

The sandbox works with sample data, never touches real calendars, carries no warranty and may be reset. Do not show sandbox data to users as if it were live.

7. Versioning and change

The API version is reported in responses. Backwards-compatible additions (new fields, new event types) may be made without notice; your clients must ignore unknown fields. Incompatible changes ship in a new version with a transition of at least 6 months.

8. Suspension

Where use threatens security, stability or other users we may suspend a key or app immediately; where possible we contact you first.