Voyager API authentication
Set how a request authenticates once, in the same panel as its headers and body, instead of
hand-assembling an Authorization header every time.
What it does
The authentication editor supports Bearer tokens, Basic auth, API keys (sent as a header or a query parameter), and OAuth 2.0 using the client-credentials grant — pick a type, fill in its fields, and Voyager applies it to the request's headers or query params at send time.
Use cases
- Testing an endpoint that requires a bearer token without rebuilding the header by hand.
- Working against an internal API that uses Basic auth or a simple API key.
- Exercising an OAuth 2.0 client-credentials flow end to end.
Frequently asked questions
Which authentication methods are supported?
Bearer token, Basic auth (username/password), API key (as a header or query parameter), and OAuth 2.0 with the client-credentials grant.
Can a request inherit auth from its collection?
There’s an “Inherit from parent” option in the auth editor, but inheritance resolution isn’t wired up yet — today it behaves the same as “No auth.” Set auth explicitly on the request until that lands.
Are credentials I enter stored securely?
Credentials are stored in Voyager’s local secret storage on the platform you’re using. Review the source before relying on this for production credentials — the project is under active development.
Related: API authentication methods explained · Request builder