Use external API keys for public developer integrations
AfriRoute’s public developer surface leads with API-key access in the Authorization header. Account login, refresh, and console session APIs are internal application concerns and should not be published as public API reference entries.
Docs mode
Reference and guide
Keep the task clear, the example nearby, and the next step obvious.
Recommended flow
Use sandbox or production external API keys for first-run testing and place the key in the Authorization header for messaging, verification, webhooks, and other public integration flows.
Keep account login, refresh, and console session mechanics inside the application boundary. The public portal should describe how developers authenticate external API requests, not expose internal session endpoints.
What to surface