Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 2.06 KB

type: "reference" title: "Custom Connection Data Field Names" description: "Public support knowledge for Custom Connection Data Field Names." category: "authentication" visibility: "public" timestamp: "2026-06-24T00:00:00Z" tags:

- "custom-connection-data-fields"

Custom Connection Data Field Names

Use this when a customer creates a custom/API-key style connected account and tool execution fails with No authentication provided, 401/403 provider errors, or a provider-specific auth error even though the credential itself works directly against the upstream API.

Field names are toolkit-specific

Do not assume every API-key or bearer-token toolkit accepts custom_connection_data.val.api_key. The required field name is toolkit-specific. For example, this shape is incorrect for Crowdin:

{
  "val": {
    "api_key": "<token>"
  }
}

Crowdin expected:

{
  "val": {
    "bearer_token": "<token>"
  }
}

To verify the required field names, inspect toolkit metadata:

Python

toolkit = composio.toolkits.get("crowdin")
print(toolkit.auth_config_details)

TypeScript

import { Composio } from "@composio/core";

const composio = new Composio();
const toolkit = await composio.toolkits.get("crowdin");
console.log(toolkit.authConfigDetails);

API

curl --location 'https://backend.composio.dev/api/v3.1/toolkits/crowdin' \
  --header "x-api-key: $COMPOSIO_API_KEY"

Look under:

auth_config_details[].fields.connected_account_initiation.required

If the mismatch continues, share a request ID or log ID with Composio support. If no request ID is available, share how custom_connection_data is being constructed, with secrets removed.

Example response:

Could you share the `custom_connection_data` shape you're sending, with the secret value removed?

The field name is toolkit-specific. For example, some toolkits expect `bearer_token` rather than `api_key`. We can verify the required field from the toolkit metadata and make sure the credential is landing in the right field.