Basic Auth

Use this method when the external API requires a username and password in the HTTP authorization header.

What this method does

Nected encodes username:password using Base64 and sends:

Authorization: Basic <base64(username:password)>

When to use

• Legacy APIs only support Basic Authentication

• Internal trusted systems still rely on username/password credentials

Required fields in Nected

• Username

• Password

Basic Auth configuration form

Step-by-step setup

1. Start from either location:

   • Path A: Navigate to Security > Authorization and click + New Authentication.

   • Path B: Open the REST API connector configuration sidebar and click Create Authentication from the Authentication dropdown.

2. Select Basic Auth.

3. Enter Username and Password.

4. Save configuration.

5. Attach/select this authentication in the integration/API request step.

6. Run test requests and confirm provider response.

Validation checklist

• Username/password are current and active.

• Target endpoint expects Basic Auth for this route.

• Request is sent over HTTPS.

Security considerations

• Always use HTTPS; Basic Auth is not safe over plain HTTP.

• Keep credentials scoped to least privilege.

• Replace with OAuth/API key where possible for stronger controls.

Common errors and fixes

• 401 Unauthorized: username/password mismatch.

• Credentials accepted locally but not in Nected: verify escaped/special characters.

• Frequent failures: password rotation not updated in Nected config.