Developer portal
A self-service surface where your consumers get keys and read docs without emailing you.
The developer portal is the outward-facing half of Apikee. Instead of issuing keys by hand and mailing them around, you point consumers at a page where they can read the docs, see their own usage, and manage their own credentials.
It lives at the Developer tab of an environment and is built from objects you already have — endpoints become the reference, clients become accounts, templates become tiers.
What a consumer can do
| Read the API reference | Generated from your endpoint registry |
| Issue a key for themselves | Scoped by the template you assigned |
| See their own usage | Requests, error rate, rate-limit headroom |
| Rotate or revoke | Without opening a support ticket |
A consumer only ever sees their own client. There is no cross-tenant visibility.
What you control
- Which template they are on, which sets their rate limits and how many keys they may hold.
- Whether self-service issuance is allowed at all — you can keep issuance manual and use the portal purely as docs plus usage.
- IP allow-lists, which stay yours to set.
Why it usually pays for itself
Key rotation is the common case. A consumer who can rotate a leaked key at 2am without reaching you is both better for them and less work for you — and because revocation is immediate in server mode, the old key stops working the moment they press the button.
Request logs
The same tab carries the request log viewer and inspector: every validation attempt, accepted or rejected, with credentials redacted. Useful when a consumer says "it returns 403 and I don't know why" — the log names which of the eight checks failed.
See Analytics & logs.