Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 04:45 UTC
| 1 | 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. |
| 2 | |
| 3 | ## Field names are toolkit-specific |
| 4 | |
| 5 | 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: |
| 6 | |
| 7 | ```json |
| 8 | { |
| 9 | "val": { |
| 10 | "api_key": "<token>" |
| 11 | } |
| 12 | } |
| 13 | ``` |
| 14 | |
| 15 | Crowdin expected: |
| 16 | |
| 17 | ```json |
| 18 | { |
| 19 | "val": { |
| 20 | "bearer_token": "<token>" |
| 21 | } |
| 22 | } |
| 23 | ``` |
| 24 | |
| 25 | To verify the required field names, inspect toolkit metadata: |
| 26 | |
| 27 | ### Python |
| 28 | |
| 29 | ```python |
| 30 | toolkit = composio.toolkits.get("crowdin") |
| 31 | print(toolkit.auth_config_details) |
| 32 | ``` |
| 33 | |
| 34 | ### TypeScript |
| 35 | |
| 36 | ```typescript |
| 37 | import { Composio } from "@composio/core"; |
| 38 | |
| 39 | const composio = new Composio(); |
| 40 | const toolkit = await composio.toolkits.get("crowdin"); |
| 41 | console.log(toolkit.authConfigDetails); |
| 42 | ``` |
| 43 | |
| 44 | ### API |
| 45 | |
| 46 | ```bash |
| 47 | curl --location 'https://backend.composio.dev/api/v3.1/toolkits/crowdin' \ |
| 48 | --header "x-api-key: $COMPOSIO_API_KEY" |
| 49 | ``` |
| 50 | |
| 51 | Look under: |
| 52 | |
| 53 | ```text |
| 54 | auth_config_details[].fields.connected_account_initiation.required |
| 55 | ``` |
| 56 | |
| 57 | 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. |
| 58 | |
| 59 | Example response: |
| 60 | |
| 61 | ```text |
| 62 | Could you share the `custom_connection_data` shape you're sending, with the secret value removed? |
| 63 | |
| 64 | 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. |
| 65 | ``` |