API Terms of use

Last updated : 18/10/2026

These terms ("API Terms") govern access to and use of the YA-Planning developer API (the "API"). They supplement the service's Terms of use. By creating an API key or calling the API, you (the "Developer") accept these terms.

1. Access & API keys

Access is free after registration. Each key is tied to an establishment and to a set of scopes (permissions) that you choose to the minimum necessary. The secret part of a key is shown only once: keep it securely. You are responsible for all activity carried out with your keys. Report any compromise without delay and revoke the key concerned.

2. Environments

The yap_test_ keys (sandbox) operate on demonstration data and do not affect any real data; writing is disabled there. The yap_live_ keys operate on your production data. Test in the sandbox before going to production.

3. Acceptable use

• Do not exceed the rate limits; put in place retries with back-off on a 429.
• Only use the API for establishments for which you are authorized.
• No reverse engineering, circumvention of access controls, or unauthorized penetration testing.
• No use that harms the availability, integrity or security of the service.
• Never expose your keys on the public client side (repository, front-end application without a proxy).

4. Data protection

The data accessible via the API (students, teachers, timetables) are personal data belonging to the establishment. You act as the establishment's processor and undertake to process it only for the purpose agreed with it, to secure it, not to resell it, and to comply with the GDPR and applicable regulations. Webhook reception must verify the HMAC signature and the freshness of the timestamp.

5. Availability, versions & deprecation

The API is provided "as is", without any service level guarantee for the free plan. We may evolve the API in a backward-compatible way at any time. Any breaking change is announced via a new major version and a minimum notice of 90 days (Deprecation header and the documentation changelog).

6. Suspension

We may suspend or revoke a key, with or without notice, in the event of a violation of these terms, abusive use, a security risk or a legal obligation.

7. Liability

To the extent permitted by law, YA-Planning is not liable for indirect damages related to use of the API. You indemnify YA-Planning against claims resulting from your use of the API or from non-compliance with these terms.

8. Contact

Questions about the API: api@yaplanning.com.

Non-contractual document — provisional version to be validated legally before going into production.