PermitCore’s API uses bearer-token authentication. Every request must include anDocumentation Index
Fetch the complete documentation index at: https://docs.permitcore.io/llms.txt
Use this file to discover all available pages before exploring further.
Authorization: Bearer <your-key> header.
Key format
API keys are opaque strings prefixed withpk_ (production) or pk_test_
(future test mode). Treat the entire string as secret.
Header convention
Accept header is recommended but optional — responses default to JSON.
Where to get a key
- Sign up at permitcore.io/signup
- After magic-link sign-in, visit Account → API Keys
- Your active key is shown once at creation — copy it then; we don’t store it in plain text after the initial display
Bucket 2 status: keys are issued on signup today. Programmatic
creation + rotation endpoints (
POST /v1/keys, DELETE /v1/keys/{prefix})
ship in ~3 weeks.Security best practices
- Never commit keys to version control. Use environment variables.
- Never embed keys in client-side JS. Server-to-server only.
- Rotate keys quarterly or immediately if exposure is suspected.
- Use one key per environment (production, staging, local). Easier to scope an incident if one is compromised.
- Restrict by IP when programmatic key management ships (Bucket 2).
Error responses for auth failures
| HTTP | Error code | When |
|---|---|---|
401 | missing_credentials | No Authorization header sent |
401 | invalid_token | Header sent but key is malformed / revoked / unknown |
403 | insufficient_scope | Key is valid but lacks scope for this endpoint |