API and Acceptable Use Terms

These terms apply in addition to the Agency Trade Agreement when your agency connects its own systems to Premium Choice Travel Designers with an API key, including through our MCP endpoint.

1. Keys

1.1 API keys are created by your account owner, and each key has only the scopes chosen for it. A key can never top up a wallet, change markups, manage users or create other keys.

1.2 Keep keys secret. Do not put them in client-side code, public repositories or shared documents. Revoke a key at once if it may have been exposed. Your agency is responsible for everything done with its keys.

1.3 Bookings made with a key are your agency's Bookings, on the same terms as bookings made in the portal. Booking and cancelling require an explicit acceptance flag in the request, and your system must obtain that acceptance from a person who has seen the price and the terms.

2. Fair use

2.1 Each key has a limit on requests per minute. Requests above it are refused until the next minute.

2.2 Search in proportion to the bookings you make. We may lower limits or suspend a key whose look-to-book ratio or traffic harms the Platform or our Suppliers, after contacting you where practical.

2.3 Do not cache or store rates beyond the life of a search or quote, or show them to anyone outside your agency and its Clients.

3. Automated and AI agents

If an automated or AI agent acts through your key, it acts for your agency. You are responsible for its instructions and its actions, and for making sure a person approves each booking and cancellation.

4. Changes to the API

We may add to the API at any time. We will give at least 30 days' notice of a change that removes or breaks something your integration uses, unless a security issue or a Supplier requires a faster change.

5. Suspension

We may revoke or suspend a key immediately to protect the Platform, our Suppliers or other agencies.