API terms of use

These terms apply to the use of the Mitgliederbuch API, embed codes and AI connector. They come on top of the general terms and the data processing agreement, which continue to apply between Mitgliederbuch and the association. This is a translation; in case of differences the Dutch version prevails.

1. Keys

An API key gives access to members' data. Keep it secret: not in code that runs in a browser or app, not in a public repository and not in a URL. Use a separate key for each integration with only the scopes that integration needs. If you think a key has leaked, revoke it immediately under Settings → API keys.

2. Rate limits

Respect the rate limits per key and do not try to get around them, for example by spreading one integration over several keys.

3. Members' data

The association remains the controller of its members' data; Mitgliederbuch is the processor, and the data processing agreement continues to apply. Whoever builds or runs an integration on behalf of an association works on behalf of that association and makes arrangements with it about the data the integration receives. Only fetch the data the integration needs.

4. Revocation

We may revoke or restrict a key or integration in case of misuse, if we suspect a key has leaked, or if an integration hinders the service for other associations. Where possible, we inform the association in advance.

5. Changes

Changes to the API follow the versioning policy. Changes to these terms are announced in the changelog.

6. Contact

Questions about these terms or about an integration: support@mitgliederbuch.de.