Skip to content
↑↓ move↵ openesc close

Authorization

Where authorization applies

Request, collection, workflow and environment credentials side by side, with the exact clicks to reach each one.

2 min read

Luvin keeps authorization in four places. Each one answers a different question: which requests, which workflows, which APIs.

Request Collection Workflow Environment credentials
Covers One saved request Requests set to Inherit from collection The steps of a workflow, per API Steps whose API uses From the contract
Types All, plus Inherit from collection All except Inherit from collection All, plus From the contract and Inherit from collection One value per securitySchemes entry of the contract
Saved in requests/<name>.request.yaml collection.yaml flow-auth.yaml The environment (values encrypted on this computer)
Sign-in for OAuth 2.0 Get new token Get new token Sign in, or Run Not applicable: you paste a token
  1. Open a request from the sidebar.
  2. Click the Authorization tab.
  3. Choose a Type.

Only HTTP and GraphQL requests have this tab.

The Authorization tab of a workflow, with one card per API

  • One-off call or exploring an API: the request.
  • All your saved requests share one login: the collection, and leave the requests on Inherit from collection.
  • A workflow needs a token that expires or is requested at run time: the workflow tab with OAuth 2.0.
  • The contract already says what it needs and a pasted token is enough: the environment credentials.

The collection’s authorization is for single requests. A workflow uses it only if an API is set to Inherit from collection in the workflow tab.