Skip to content
↑↓ move↵ openesc close

Authorization

Inherit from collection and No Auth

What Luvin sends with Inherit from collection and with No Auth, and which one a new request starts with.

2 min read

Inherit from collection says “use whatever the collection uses”. No Auth says “send nothing”. They add no fields: they choose where the authorization comes from.

The collection is set to Bearer Token with {{token}}. Three requests:

Request Type Luvin sends
Inherit from collection Authorization: Bearer <value of token>
Basic Auth (its own) Its own Basic header. The collection is ignored.
No Auth No authorization, even though the collection has one.
Kind of request Type at creation
HTTP Inherit from collection
GraphQL Inherit from collection
WebSocket Inherit from collection
gRPC No Auth

The collection itself starts with No Auth. So a new HTTP request goes out without authorization until you set one in the collection or in the request.

On the Authorization tab, the request says which one it uses:

  • Uses the collection’s authorization: Bearer Token.
  • The collection has no authorization set up, so this request goes without one.

Configure in the collection opens the collection’s card. In the Headers tab, the Authorization row appears as Inherited from the collection · Bearer Token.

Requests that inherit share one OAuth 2.0 token. See OAuth 2.0.

The tab says This request sends no authorization. Use it for a request that must go out without credentials, for example to check that the API answers 401.

In the collection, No Auth reads Requests that inherit from the collection are sent without authorization.

Opt out of the collection’s authorization

Section titled “Opt out of the collection’s authorization”
  1. Open the request and click Authorization.
  2. In Type, choose No Auth to send nothing, or another type to use its own.

Choose Inherit from collection to go back.