Some APIs require authentication credentials to be passed as URL query parameters rather than HTTP headers — for example, ?api_key=your_key appended to every request. Previously, elvex only supported header-based authentication for custom integrations, which meant these APIs couldn't be connected.
elvex supports query parameter authentication for Custom API and MCP integrations, so you can connect APIs that use this authentication pattern.
You might need this when:
The API you're connecting requires an
api_keyortokenappended to every request URLYour internal tooling uses query-string-based authentication rather than HTTP headers
You need to pass both header credentials and query parameters simultaneously to satisfy an API's auth requirements
How to configure query parameter authentication
Navigate to Settings → Integrations and click Add. Select API or MCP Server
Under the Authentication section, select Custom (under API Key / Headers)
Add your authentication credentials:
Under Headers, add any header-based credentials (e.g.
Authorization: Bearer your_token)Under Query Parameters, add any query parameter credentials (e.g. key:
api_key, value:your_api_key_here)
Save the integration
elvex will automatically append the configured query parameters to every request made through this integration.
Common Questions
Is this available for all integration types?
Query parameter authentication is available for Custom API integrations and MCP integrations. It is not applicable to OAuth-based integrations like Google or Slack, which use their own authentication flows.
Can I use both headers and query parameters at the same time?
Yes — you can configure both simultaneously. Add your header credentials under Headers and your query parameter credentials under Query Parameters in the same integration configuration.
Are my credentials stored securely?
Yes — credentials configured in elvex integrations are stored securely and are never exposed to end users in conversations.