Authentication
Nouto has a dedicated Auth tab in the request editor for configuring authentication. The auth type you select determines which fields appear and how the credentials are sent with each request.
Auth Types
Section titled “Auth Types”| Type | Best for |
|---|---|
| Basic | HTTP Basic auth, legacy APIs, internal tools |
| Bearer Token | JWT tokens, OAuth access tokens, API tokens |
| API Key | API keys sent as a header or query parameter |
| OAuth 2.0 | APIs using standard OAuth flows |
| AWS Signature v4 | AWS services (S3, DynamoDB, API Gateway, etc.) |
| NTLM | Windows-integrated auth, IIS, corporate intranets |
| Digest | Legacy systems, network appliances, some enterprise APIs |
| None | Public endpoints, or when auth is set via headers manually |
Accessing the Auth Tab
Section titled “Accessing the Auth Tab”Open any request and click the Auth tab. Select a type from the dropdown. The fields below update immediately to match the selected type.
Variable Support
Section titled “Variable Support”Every auth field accepts {{variable}} syntax. Store credentials in environment variables rather than entering them directly, especially for secrets like tokens and passwords.
{{API_TOKEN}}{{AWS_ACCESS_KEY}}{{OAUTH_CLIENT_SECRET}}Auth Inheritance
Section titled “Auth Inheritance”Requests inside collections and folders can inherit auth from their parent instead of configuring it separately. This is useful when all requests in a collection share the same credentials.
See Auth Inheritance for the full configuration guide.
Security
Section titled “Security”Sensitive fields (passwords, tokens, client secrets) are always masked in the UI. When you send a request over unencrypted HTTP to a non-localhost URL, Nouto shows a security warning.