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 46 lines 1.51 KB
Rendered Raw
1 ---
2 type: "reference"
3 title: "Kickbox"
4 description: "Public support knowledge for Kickbox."
5 category: "authentication"
6 visibility: "public"
7 timestamp: "2026-06-24T00:00:00Z"
8 tags:
9 - "kickbox"
10 ---
11 # Kickbox
12
13
14 ## Single verification auth and EU endpoint checks
15
16 For `KICKBOX_SINGLE_VERIFICATION_API`, the Composio credential field is `generic_api_key`. For direct/custom credential execution, customers should pass:
17
18 ```json
19 {
20 "val": {
21 "generic_api_key": "<KICKBOX_API_KEY>"
22 }
23 }
24 ```
25
26 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.
27
28 If Kickbox returns 403 `Invalid API key`, ask the customer to verify:
29
30 - the redacted `custom_connection_data.val` shape
31
32 - key validity
33
34 - key permissions
35
36 - account/credit state
37
38 - whether the Kickbox account is EU-only
39
40 Kickbox docs say EU-only accounts that sign in from `app.eu.kickbox.com` must use `api.eu.kickbox.com`. If the customer is EU-only, escalate as a possible toolkit base-URL/region gap because the current toolkit uses the standard `api.kickbox.com` host.
41
42 Useful source docs:
43
44 - Single Verification API: https://docs.kickbox.com/docs/single-verification-api
45
46 - API Quickstart / authentication and EU endpoint note: https://docs.kickbox.com/docs/using-the-api