Account API Keys
An Account API Key authenticates programmatic calls to MewCP's management APIs. Your backend uses this key to start OAuth flows for audience, get hosted credential form URLs, and manage audience member credential state via the MewCP Auth API.
Format
Code
Example: mewcp_acct_7df44e73e8cd42bbf4860ffc66520efb62d973615dc2c0f7fb5607fb82d75b53
How to get one
- Go to Dashboard -> Developer -> Account API Keys
- Click Generate Key, give it a label, and copy the key
How to use it
Pass it as a Bearer token in the Authorization header. Every MewCP Auth API endpoint also requires an x-mewcp-key header: the API Key of the specific business-mode server you're acting on (see API Key). The two are not interchangeable and both are required:
Code
TypeScript:
Code
Python:
Code
What you can do with it
| Action | Endpoint |
|---|---|
| Start OAuth flow for a user | POST /oauth/{provider}/start |
| Get hosted static credential form | POST /credentials/static/{providerSlug}/connect |
| List audience for a server | GET /end-users |
| Get an audience member's credentials | GET /end-users/{externalUserId} |
| Revoke a user's credential | DELETE /end-users/{externalUserId} |
Every action above is scoped to the single server identified by x-mewcp-key. There's no call that lists or manages audience across every server at once.
Full reference in the MewCP Auth API docs.
Best practices
- Keep it server-side only. Never expose Account API Keys in frontend code or mobile apps.
- One key per environment. Use separate keys for production, staging, and local development.
- Revoke if compromised. Go to Developer -> Account API Keys and click Revoke.