Skip to main content
Membership.io has three credential types.

Platform JWT

Use a platform JWT when a creator-side user is signed in. This is the right credential for dashboards and admin tools.
Send the returned access token on admin requests:
The admin sign-in and password guide covers Forgot password?, resetting from an emailed link, and changing a known password under Account. The same guide shows the public forgot and reset requests and the signed-in change request. A password reset signs out every session; a password change returns fresh tokens that your API client must use.

Contact JWT

Use a contact JWT when a member is signed in to a hub. Contacts can authenticate with password or magic link depending on the hub flow. Contact-auth request bodies use JSON:API envelopes:
Send the returned contact access token on member-facing routes:

Team API key

Use a team API key for server-to-server integrations, CLIs, and automation. API keys start with mio_sk_ and are sent as bearer tokens:
An API key is bound to one team. It cannot be used against another team’s routes, and it cannot manage API keys. Only the team owner can create, change and revoke keys, while signed in. Do it on the API keys page of the admin (Manage API keys in the admin) or with the API (API keys).

Which one should I use?