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 33 lines 1.31 KB
Rendered Raw
1 ## Single verification auth and EU endpoint checks
2
3 For `KICKBOX_SINGLE_VERIFICATION_API`, the Composio credential field is `generic_api_key`. For direct/custom credential execution, customers should pass:
4
5 ```json
6 {
7 "val": {
8 "generic_api_key": "<KICKBOX_API_KEY>"
9 }
10 }
11 ```
12
13 Do not assume `api_key` is the correct field name for Composio custom credential data. The Kickbox provider API itself documents an `apikey` query parameter, but Kickbox's official quickstart also says `Authorization: Bearer <API key>` is accepted. Composio currently uses the Bearer header and `https://api.kickbox.com/v2/verify`, which is valid for standard Kickbox accounts.
14
15 If Kickbox returns 403 `Invalid API key`, verify:
16
17 - the redacted `custom_connection_data.val` shape
18
19 - key validity
20
21 - key permissions
22
23 - account/credit state
24
25 - whether the Kickbox account is EU-only
26
27 Kickbox docs say EU-only accounts that sign in from `app.eu.kickbox.com` must use `api.eu.kickbox.com`. If your account is EU-only, contact Composio support about a possible toolkit base-URL/region gap because the current toolkit uses the standard `api.kickbox.com` host.
28
29 Useful source docs:
30
31 - Single Verification API: https://docs.kickbox.com/docs/single-verification-api
32
33 - API Quickstart / authentication and EU endpoint note: https://docs.kickbox.com/docs/using-the-api