API terms

1Who and when

These terms apply to everyone who uses the API or the MCP server with a PartyPPL token: a token an organisation makes in the portal, or an app you connect to your account with OAuth (such as Claude). If you use the API on behalf of an organisation, they are part of the organiser terms; the terms of service always apply as well.

You accept these terms when you make a token or connect an app. We record which version you accepted and when. A token or connection from before we started recording this has no such record; for those the acceptance of the organiser terms applies, which have always carried the API rules.

The machine-readable version is at `https://api.partyppl.nl/v1/terms` and says the same. Every version has a date as its version number. Where this page and /v1/terms with the same version number differ, this page prevails.

2Who the agreement is with

Provider

PartyPPL

Chamber of Commerce number

97359866

VAT identification number

NL005264805B67

Address

Pater R.D. Kloegstraat 7, 5684 TK Best, the Netherlands

Contact

api@partyppl.nl

PartyPPL is the trade name of the business registered with the Netherlands Chamber of Commerce under number 97359866. That business is your counterparty in this agreement; on the other side is the organisation on whose behalf you use the API, or you yourself when you connect an app to your own account.

3Access and tokens

• You create a token in the portal under API, as an owner or administrator of an organisation. It starts with `ppl_live_`, you see it once, and we keep only a hash of it.
• You connect an app with OAuth on partyppl.nl: you choose on behalf of which organisation, with the rights your role there gives, or just for yourself, with the read scope on the public agenda. You can disconnect at any time in your settings or in the portal.
• Organisers choose from the scopes read, scan, attendance and tickets. The admin scope we give only to our own platform team.
• A token sees only the private data of its own organisation. With the read scope it also sees the public agenda.
• Keep your token secret, like a password. Leaked? Revoke it and make a new one. What happens with your token is your responsibility.

4The six rules

1. Credit PartyPPL wherever you show this data, with a link back to the event's page on partyppl.nl.
2. Do not redistribute the catalogue as a whole, and do not resell it as a data product.
3. Do not present the data as your own, and do not strip the link back.
4. Cache what you fetch. Stay inside the rate limits rather than working around them with more tokens.
5. Event data comes from the organisers themselves and from the public agendas listed on /bronnen; each source keeps its own rights and licence.
6. We correct and remove events as organisers ask us to. Refresh what you have cached at least once a day.

5Attribution

Every answer with agenda data carries the attribution itself, in `meta.attribution`: the sentence 'Event data from PartyPPL. Link back to the event page on partyppl.nl.', the link to the event page and the link to these terms. Show that sentence, or a translation of it, with the link, visibly next to the data.

6Rate limits

• 120 requests per minute per token.
• 10,000 requests per day per token, unless we agree a different daily budget for your token.
• Every answer tells you where you stand in `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset`; one too many gets `429` with `Retry-After`.
• Use the `ETag` and poll at most once a minute. Making more tokens to get round the limits is not allowed.

7Personal data

The API gives no data about individual visitors. What you get back about your own events are counts (going, interested, tickets) and the result of a scan at your own door. A valid scan comes with the name on that ticket, as the door sees it too.

If you load tickets from another shop through the API, with e-mail addresses and names, you are the controller for that and we are the processor. The data processing agreement then applies.

Buying, transferring or refunding tickets, chats, the forum and messages are not in the API.

8Availability and liability

The API is free. We do our best to keep it reachable and stable, but promise no fixed availability and no support within a fixed time.

If you use the API on behalf of an organisation, liability is governed by the organiser terms; if you connect an app to your own account, by the terms of service.

9Revocation and changes

On misuse or a breach of these rules we may limit or revoke a token, and on repetition the connection of your organisation. We say why, unless that would harm an investigation or the security of the platform.

If the terms change, they get a new version number. We announce that at least 30 days in advance by e-mail to the owners of organisations with a token, unless security or the law requires it at once. A change to an endpoint that breaks existing integrations is announced the same way.

10Contact

Questions about the API: api@partyppl.nl. The reference is at api.partyppl.nl for anyone logged in as a member of an organisation.

What changed

• 19 October 2026: a short summary sits at the top, and corrected that the result of a valid scan gives the name on that ticket, as the API always did. The rules did not change, so the version stays 2026-09-22.
• 17 October 2026: the provider is named: PartyPPL, with its Chamber of Commerce number, VAT number and address. Connected apps (OAuth) are covered too, and a new token or connection records the acceptance with version and time. The rules did not change, so the version stays 2026-09-22 and nobody has to accept again.
• New: the API terms as a page of their own, the same as version 2026-09-22 at /v1/terms, with tokens, limits, personal data and revocation.