Skip to main content

Base URL

All MCP endpoints use your Knotie AI base URL:
All requests require the Authorization: Bearer pkt_... header. The legacy X-API-Key header is deprecated. See Authentication for details.

Customer management

Create customer (onboard)

Onboard a new customer with optional portal access. Request body:
Response 200 OK:
Side effects:
  • Creates the customer record
  • Sends portal invite email (if allowPortalAccess is true)
  • Applies plan features (if planId is provided)
Errors:

Create customer (simple)

Create a customer record with minimal fields.

List customers

Returns a paginated list of all customers under your partner account. Query parameters: Response 200 OK:

Get customer

Returns full details for a single customer, including feature flags, menu visibility, credit settings, and deployment status. Response 200 OK:
Errors:

Update customer

Update any customer field. All fields are optional — only send the fields you want to change. Request body (all fields optional):
Common updatable fields include basic info, feature flags (enableAdvancedAnalytics, enableApiAccess, customerPortalEnabled), menu visibility (showKnowledgeBase, showIntegration, allowedApps, etc.), team settings (maxTeamMembers, enableTeamMembers), AI credit settings, and deployment tracking fields. Validation:
  • Email format is validated and must be unique within your partner scope
  • Credit plan IDs are validated if provided
Response 200 OK: Same shape as the GET response.

Portal access

Enable portal access

Enables customer portal access and sends an invite email with temporary credentials. Request body: None required. Response 200 OK:
Side effects:
  • Creates or updates customer credentials
  • Generates a temporary password
  • Sends a branded portal invite email

Block / unblock portal access

Toggles the customer’s portal access. If currently active, blocks it. If currently suspended, re-enables it. Request body: None required. Response 200 OK:

Reset customer password

Sends a password reset email to the customer. Response 200 OK:

Agent mapping

Map customer to Retell agent

Assign a customer to a Retell agent. Request body:
Response 200 OK:
Errors:

Unmap customer from Retell agent

Remove the customer mapping from a Retell agent.

Map customer to VAPI agent

Same request/response shape as the Retell mapping endpoint.

Unmap customer from VAPI agent

Remove the customer mapping from a VAPI agent.

Team members

Add team member

Invite a team member to a customer’s account. Request body:
Response 200 OK:
Validation:
  • Team member count is checked against the customer’s maxTeamMembers limit

List team members

Response 200 OK:

Delete team member

Response 200 OK:

Common error responses

All endpoints return standard error responses: