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:

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