Skip to main content
POST
Approve Agent Onboarding

Overview

This endpoint is called from the browser by the dashboard during the agent onboarding flow, after the owner signs up (or logs in) and either starts the Agent Phone Plan or chooses to connect the bot on the org’s free credits. It isn’t called directly by the bot, the bot only ever sees its effect through /v1/agent/onboarding/poll.
Requires an authenticated dashboard session for an org (not a personal account, and not an API key). The response never includes the api_key, only the bot’s later poll call receives it.

Body Parameters

string
required
The short code shown to the owner by /v1/agent/onboarding/start.
boolean
Pass true to connect the bot without an Agent Phone Plan, on the org’s free credits. Strictly a boolean; "true" as a string is rejected. Without it, an org that has no active plan gets 402 PLAN_REQUIRED. An org that already has an active plan ignores skip_plan entirely: the plan payload is returned as usual, including the PLAN_NUMBER_PENDING wait while its number is provisioned.

Response

object
Confirmation that the code was claimed for this org.
string
approved.
string
The org the code was claimed for.
string | null
The number provisioned for this org’s Agent Phone Plan, or null when the code was approved with skip_plan: true and the org has no plan.
string
The client_name the bot passed to /start, if any.
string
The first 14 characters of the API key that will be issued to the bot, the same handle Settings > API Keys shows. Display only, never the key itself.
null | array
null on success.

Docs for agents: llms.txt