Part of the API Studio: Complete Tutorial Series, 46 short videos covering every feature.
AUTHENTICATION
Supported Types
All authentication types available in the Auth tab dropdown:
| Type | Description | When to Use |
|---|---|---|
| None | No authentication applied | Public endpoints with no auth requirement |
| Basic | Username + password Base64-encoded in Authorization header | Simple internal APIs, dev servers |
| Bearer | Token sent as Authorization: Bearer <token> | JWT tokens, OAuth access tokens |
| API Key | Key-value pair added to header or query parameter | Third-party APIs with static keys |
| OAuth 2.0 | Authorization Code or Client Credentials grant flow | User-authorized flows, third-party integrations |
| AWS SigV4 | HMAC-SHA256 signature with access key, secret, region, service | AWS services (S3, Lambda, API Gateway) |
| Digest | Challenge-response authentication (MD5/SHA-256) | Legacy systems requiring RFC 7616 digest auth |
How Auth Works
Auth is the first step in the request pipeline — injected before pre-request scripts and HTTP execution:
Authorization header manually in the Headers tab and configure auth in the Auth tab, both will be sent. Avoid duplicates by using one or the other.
The Auth Tab
The Auth tab in the request builder is where you configure authentication for each request:
collections.jsonrequest → folder → ... → collection. The first ancestor with a non-"none" auth config wins.
Variable Support
All auth fields support {{variable}} placeholders — resolved at send time from the active environment, vault secrets, and collection variables.
| Source | Priority | Example |
|---|---|---|
| Collection variables | Lowest | {{base_url}} |
| Global environment | ↑ | {{global_key}} |
| Vault secrets | ↑ | {{api_token}} |
| Local environment | Highest (wins) | {{token_override}} |
Common pattern — store tokens in the vault:
// Vault secret: api_token → sk-abc123...
// Secret set maps: api_token → {{api_token}}
// Bearer token field: {{api_token}}
// At send time resolves to: Authorization: Bearer sk-abc123...
Choosing a Type
Use this decision table to pick the right auth type for your API:
| Scenario | Recommended Type | Why |
|---|---|---|
| Simple internal APIs, dev servers | Basic | Minimal setup — just username and password |
| JWT tokens, OAuth access tokens | Bearer | Standard token-based auth, one field |
| Third-party APIs with static keys | API Key | Flexible — header or query param, custom key name |
| User-authorized flows, third-party integrations | OAuth 2.0 | Full OAuth flow with token exchange |
| AWS services (S3, Lambda, API Gateway) | AWS SigV4 | Required by AWS — signs request with HMAC-SHA256 |
| Legacy systems requiring challenge-response | Digest | Server challenges, client responds with hash — avoids plaintext passwords |
Authorization header examples. Bearer xyz = Bearer type. Basic abc== = Basic type. X-API-Key: xyz = API Key type.