Developer docsInformational
Authentication Router by MP
Bearer token cu cheia API Router. Erori 401/403 și gestionare.
Raspuns scurt
Toate requesturile către Router by MP cer header `Authorization: Bearer <router_api_key>`. Cheile au prefix; pastreaza tokenul complet doar in secure store.
Problema concreta
Echipele intreaba: ce format are cheia, unde se pune, ce erori intoarce gateway-ul, cum se rotesc cheile.
Cum o rezolva Router by MP
Bearer token standard. La 401 verifica cheia, la 403 verifica whitelist model și buget. Rotire trimestriala recomandata; block instant disponibil in cabinet.
Fluxuri uzuale
- Genereaza cheia in /keys.
- Salveaza in secure store (HashiCorp Vault, AWS Secrets Manager, .env local).
- Trimite ca Authorization Bearer.
- La compromis: block instant in cabinet + rotire.
| Control | De ce conteaza |
|---|---|
| Bearer standard | Aceeasi forma ca OpenAI. |
| Erori clare | 401 = key, 403 = scope, 429 = rate limit. |
| Block instant | Cheia compromisa nu rupe altele. |
Authorization headerbash
curl https://api.megapromoting.com/v1/models \
-H "Authorization: Bearer $ROUTER_API_KEY"Reguli si limite
- Master key. Master nu se folosește in cod public; doar admin.
- Tokenul complet. Se vede o singura data la creare; salveaza imediat.
- Rotare. Calendarul rotare ramane responsabilitatea ta.
Integrare rapida
Foloseste endpointul https://api.megapromoting.com/v1, trimite cheia caAuthorization: Bearer <router_api_key> si verifica pagina/modelsinainte de productie.