Developer API Terms

1. Access

1. The API is part of Pro and of complimentary plans that include it. When your business stops having one of these plans, your keys, OAuth grants and webhook endpoints are kept but stop working until it has one again.

2. The API is for server-to-server use by your business and by the services you choose to connect. You may not offer API access, or a service that mainly resells it, to third parties.

2. Credentials and connected services

1. You are responsible for your API keys, for the OAuth applications you authorize and for the systems and services you connect, including what they do with the access you give them.

2. Keep keys secret. Give each key and application only the permissions it needs. Revoke a key or a grant at once if you suspect it has been exposed.

3. Actions taken with your keys or grants are treated as actions of your business.

3. Data you send and receive

1. You remain the controller of the personal data of your customers and guests that you send to the API, create through it or receive from it, including through webhooks. You are responsible for having a lawful basis and giving the required notices for that processing.

2. When you direct data to a service through a key, an OAuth grant or a webhook endpoint, Clearslot discloses it on your instruction. That service is your recipient, not Clearslot's subprocessor.

3. Bookings you create through the API must reflect a real request from the guest. Where a booking page asks the guest to accept cancellation fees or to let a service begin within a withdrawal period, you may confirm that consent through the API only when the guest has actually given it.

4. Limits and acceptable use

1. The API has published limits. You may not attempt to get around them, for example by spreading requests across keys or businesses.

2. You may not use the API to scrape data you are not entitled to, to send unsolicited communications, to test or probe Clearslot's security without written permission, or for any use the Terms prohibit.

3. We may throttle, suspend or revoke access, keys, grants or endpoints when reasonably necessary for security, for the integrity of the Service, or to stop a breach of these API Terms or the Terms. Where we can, we tell you first or promptly afterwards.

5. Changes to the API

1. Version one of the API changes only by adding features. We announce deprecations in the changelog and with response headers.

2. We give at least 12 months' notice of a change that breaks existing integrations, except where a shorter period is needed to fix a security problem or to comply with law.

6. OAuth application publishers

If your business registers an OAuth application that other businesses authorize, you also agree to:

1. describe the application, its publisher and the data it requests accurately, and keep that description current;

2. request and keep only the data the application needs;

3. delete the data you received from a business, and stop using it, when that business disconnects the application, unless the law requires you to keep it;

4. have a privacy policy that covers the application; and

5. accept that an application not yet reviewed by Clearslot can be authorized only by your business and a small number of businesses you invite, and that we may suspend an application, which revokes its grants.

7. Other terms

The liability, indemnity, suspension, termination, governing law and dispute terms of the Terms apply to the API. These API Terms are provided in English.