> ## Documentation Index > Fetch the complete documentation index at: https://docs.vocobase.com/llms.txt > Use this file to discover all available pages before exploring further. # Connect a single-key tool for a customer > Submits a customer's credential directly, for connectors that authenticate with one API key (Cal.com, Calendly) rather than OAuth. Use this when you already hold the key and do not want to send the customer through the hosted flow. ## OpenAPI ````yaml /openapi.json post /customers/{id}/connections/api-key openapi: 3.1.0 info: title: Vocobase API version: '2.0' description: >- API for managing voice AI agents, documents, and calls on the Vocobase platform. servers: - url: https://api.vocobase.com/api/v2 description: Production security: - bearerAuth: [] tags: - name: Config description: >- Read and update account configuration, webhook settings, and telephony credentials. - name: Agents description: Create, read, update, and delete voice AI agents. - name: Voices description: >- List voice tiers, available voices, and stream preview audio for agent configuration. - name: Documents description: Upload, manage, and delete knowledge base documents. - name: Agent Documents description: Link and unlink documents to agents for knowledge base integration. - name: Calls description: Initiate outbound calls and view call history. - name: Phone Numbers description: >- Import DIDs, assign agents for inbound routing, and re-sync carrier Application bindings. - name: Inbound Routing Policies description: >- Define pre-answer routing decisions for inbound calls before AI sessions are created. - name: Telephony Connections description: Create, list, rename, and disconnect named V2 telephony connections. - name: VoiceLink Management description: Manage VoiceLink reseller clients, DID mapping, and readiness sync. - name: Projects description: Organize agents into projects. Every agent belongs to exactly one project. - name: Dictionaries description: Speech-recognition dictionary CRUD and agent attachment. - name: Sessions description: Browser-initiated WebRTC voice sessions for in-app voice agents. - name: Campaigns description: Batch outbound calling. - name: Billing description: Balance, transactions, and usage summaries. - name: Custom Functions description: HTTP endpoints the agent can call mid-conversation. - name: Extraction Sets description: Reusable sets of post-call extraction fields. - name: Lifecycle Hooks description: Automatic pre-call and post-call integration steps. - name: Messaging description: Bring-your-own WhatsApp sending. - name: Integration Logs description: Audit trail for integration calls. - name: Connectors description: Catalog of tools an agent can be connected to. - name: Customers description: B2B2B sub-tenants and their tool connections. - name: Agent Tools description: Binding connectors and connections to an agent. paths: /customers/{id}/connections/api-key: post: tags: - Customers summary: Connect a single-key tool for a customer description: >- Submits a customer's credential directly, for connectors that authenticate with one API key (Cal.com, Calendly) rather than OAuth. Use this when you already hold the key and do not want to send the customer through the hosted flow. operationId: createApiKeyConnection parameters: - name: id in: path required: true schema: type: string format: uuid description: Customer ID. requestBody: required: true content: application/json: schema: type: object required: - tool_slug - api_key properties: tool_slug: type: string enum: - calcom - calendly description: >- The connector slug. Only `calcom` and `calendly` accept a direct API key; anything else returns `400 TOOL_NOT_API_KEY`. api_key: type: string description: Stored encrypted; never returned. example: tool_slug: calcom api_key: cal_live_... responses: '200': description: Success. content: application/json: schema: type: object properties: success: type: boolean const: true data: type: object properties: connection_id: type: string format: uuid tool_slug: type: string example: success: true data: connection_id: uc_b4c5d6e7-f809-1223-3445-566778899aab tool_slug: calcom '400': description: >- `INVALID_TOOL_SLUG` when `tool_slug` is missing, `TOOL_NOT_API_KEY` when the connector does not accept a direct API key, `INVALID_API_KEY` when the key is empty. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: TOOL_NOT_API_KEY message: tool "cal_com" does not accept direct API keys '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' '409': description: '`CUSTOMER_NOT_ACTIVE` when the customer has been archived.' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: CUSTOMER_NOT_ACTIVE message: Customer is not active '429': $ref: '#/components/responses/RateLimitExceeded' '500': $ref: '#/components/responses/InternalError' components: schemas: ErrorResponse: type: object properties: success: type: boolean const: false error: type: object properties: code: type: string message: type: string required: - code - message required: - success - error responses: Unauthorized: description: Missing or invalid API key. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: UNAUTHORIZED message: Invalid or missing API key NotFound: description: Resource not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: NOT_FOUND message: Resource not found RateLimitExceeded: description: Per-account rate limit exceeded. Retry after a short backoff. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: RATE_LIMITED message: Rate limit exceeded. Retry after 60 seconds. InternalError: description: Unexpected server error. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false error: code: INTERNAL_ERROR message: An unexpected error occurred securitySchemes: bearerAuth: type: http scheme: bearer description: >- API key in format: `rg_live_xxxx`. Pass as a Bearer token in the Authorization header. ````