When creating or editing a custom tool, navigate to its 'Authentication' tab or section. Here, you can select and configure the appropriate method.
API Keys are common for simpler authentication. They are essentially secret tokens that grant access.
Choose 'API Key' from the available authentication types.
Securely paste the API key provided by the external system into the designated field. Treat this key like a password – keep it confidential.
Determine how the API key should be sent with the request:
Authorization
, X-API-Key
, x-api-token
). Some systems might require a prefix before the key in the header (e.g., Bearer YOUR_API_KEY
). If so, add the prefix (like Bearer
including the space) in the designated prefix field or directly in the header value construction if only one field is provided.api_key=YOUR_API_KEY
).Save the authentication settings for the tool.
Bearer token authentication is commonly used with JWT (JSON Web Tokens) and other token-based authentication systems.
Choose 'Bearer Token' from the authentication types.
Paste the token value provided by the external system into the designated field. The system will automatically add the 'Bearer' prefix when sending the token in the Authorization header.
Bearer tokens are typically sent in the Authorization header. The system will use the standard format: Authorization: Bearer your_token_here
.
Save the authentication settings for your tool.
Basic Authentication uses username and password credentials encoded in base64 format.
Choose 'Basic Auth' from the authentication types.
Provide the username and password required by the external API in the designated fields. The system will handle the base64 encoding automatically.
The system will automatically format and send your credentials in the standard format: Authorization: Basic base64(username:password)
.
Save the authentication settings for your tool.
If the external system uses a different method (e.g., custom authentication schemes), you might need to configure it manually using the Request Header settings within the main tool configuration, potentially using tool variables to store credentials securely (though dedicated authentication methods are preferred).