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 77 lines 2.06 KB
Rendered Raw
1 ---
2 type: "reference"
3 title: "Custom Connection Data Field Names"
4 description: "Public support knowledge for Custom Connection Data Field Names."
5 category: "authentication"
6 visibility: "public"
7 timestamp: "2026-06-24T00:00:00Z"
8 tags:
9 - "custom-connection-data-fields"
10 ---
11 # Custom Connection Data Field Names
12
13 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.
14
15 ## Field names are toolkit-specific
16
17 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:
18
19 ```json
20 {
21 "val": {
22 "api_key": "<token>"
23 }
24 }
25 ```
26
27 Crowdin expected:
28
29 ```json
30 {
31 "val": {
32 "bearer_token": "<token>"
33 }
34 }
35 ```
36
37 To verify the required field names, inspect toolkit metadata:
38
39 ### Python
40
41 ```python
42 toolkit = composio.toolkits.get("crowdin")
43 print(toolkit.auth_config_details)
44 ```
45
46 ### TypeScript
47
48 ```typescript
49 import { Composio } from "@composio/core";
50
51 const composio = new Composio();
52 const toolkit = await composio.toolkits.get("crowdin");
53 console.log(toolkit.authConfigDetails);
54 ```
55
56 ### API
57
58 ```bash
59 curl --location 'https://backend.composio.dev/api/v3.1/toolkits/crowdin' \
60 --header "x-api-key: $COMPOSIO_API_KEY"
61 ```
62
63 Look under:
64
65 ```text
66 auth_config_details[].fields.connected_account_initiation.required
67 ```
68
69 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.
70
71 Example response:
72
73 ```text
74 Could you share the `custom_connection_data` shape you're sending, with the secret value removed?
75
76 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.
77 ```