Skip to main content
The generated endpoint pages are the exact API contract for production integrations. Production requests use https://api.member.dev plus the canonical /api/v1 path prefix. Bare /api routes may still respond for backward compatibility, but new integrations should use /api/v1. Use it for:
  • Exact paths and methods.
  • Path, query, and body parameters.
  • Request and response schemas.
  • Current endpoint tags.
Use the authored guides for:
  • Which endpoints to combine for a workflow.
  • Which credential to use.
  • What product concepts mean.
  • Alpha caveats that are not obvious from OpenAPI alone.

​
Authentication in the playground

Most endpoints use bearer authentication. Paste one of these into the auth field:
  • A platform access token.
  • A contact access token.
  • A team API key beginning with mio_sk_.
Some public and webhook endpoints do not require a bearer token even though the global docs auth field is shown.