Skip to main content

No Authentication

Some HTTP endpoints don't require authentication or use API keys passed in headers.

When to Use​

Use the "No Authentication" option when:

  • The endpoint is publicly accessible
  • Authentication is handled via custom headers
  • The endpoint uses IP whitelisting for security

Configuration​

When configuring an HTTP connector with no authentication:

  1. Select "None" from the Authentication dropdown
  2. Ensure any required API keys are included in the Headers section

Example Headers​

If the API requires an API key in the header:

Content-Type: application/json
X-API-Key: your_api_key_here

Testing the Connection​

To test an HTTP connector with no authentication:

  1. Configure the connector with the appropriate URL and headers
  2. Click "Test Connection"
  3. Verify that the test request succeeds
  4. Check the response for any error messages

Security Considerations​

When using HTTP connectors without authentication:

  • Ensure the receiving endpoint has appropriate security measures
  • Consider using HTTPS to encrypt data in transit
  • Implement IP restrictions on the receiving end if possible
  • Regularly rotate any API keys used in headers

Next: Bearer Token Authentication →