Skip to content

Start

Get a key

You make a token for the REST API yourself, in your organisation's portal. It costs nothing. The MCP server needs no token: you sign in there with OAuth.

How to make a token

  1. Sign in on partyppl.nl with your e-mail address and the code you receive. No account yet? You make one when you sign in.
  2. Create an organisation at partyppl.nl/organiser/start, or have yourself added to an existing one. Tokens can be made as Eigenaar (owner) or Beheerder (admin).
  3. Open API in the portal: partyppl.nl/organiser/api. Give the token a name you will recognise later, for instance your app's name.
  4. Pick the scopes. For the public agenda read is enough. The other scopes are under Authentication.
  5. Copy the token straight away. It starts with ppl_live_ and you see it once: we only keep a hash. Put it in your password manager or your server's secrets, never in code that runs in a browser or an app.

Managing and revoking

The same page shows for each token when it was last used, how many requests it made today and this month, and its daily quota. Leaked or no longer needed? Revoke it there; it stops working at once. Make a token per app, so you can revoke one without stopping the rest.

You can also see what your token does yourself: GET /v1/me says which organisation and scopes it has and how much it used today per endpoint. See Token.

For an assistant: no token

Whoever connects Claude or another MCP client signs in with their PartyPPL account (OAuth) and chooses on whose behalf: Read only is open to anyone, an organisation to its members. See MCP and Claude.

The admin scope

The admin scope exists only on tokens of the platform itself, made by the PartyPPL team in /admin/api. An organisation cannot request it, and an organisation's token that carries it anyway is refused.

Updated