Legacy API v0

API v0 is the legacy SiteGPT API. It stays available for existing integrations. For new work, use API v2. To move an integration, see Move from API v0 to v2.

Base URL

https://sitegpt.ai/api/v0

One endpoint uses v1 in its path: POST https://sitegpt.ai/api/v1/chatbots/{chatbotId}/links (“Add Content to Chatbot”). It uses the same API key and response format as v0.

API key

API v0 and v1 use the legacy API key. Scoped sgpt_ tokens from the Agents page do not work with v0.

Plan: Growth plan and above. See Plans and limits.
Where to find it: Open the Billing page. The key shows in the line “Your API Key is …”.
SiteGPT creates the key for you. You cannot create or rotate it yourself. If your plan includes API access but you do not see a key, contact support.

See Authentication for more about the legacy key. Send the key in the Authorization header:

curl https://sitegpt.ai/api/v0/chatbots \
  -H "Authorization: Bearer YOUR_API_KEY"

Keep the key on your server. Anyone with the key can read and change your chatbots.

Response format

Success:

{
  "success": true,
  "message": "...",
  "data": { }
}

Error:

{
  "success": false,
  "message": "...",
  "data": null,
  "error": {
    "code": "ERROR_CODE",
    "message": "Readable error message",
    "details": null
  }
}

When validation fails, error.details is a list of field errors. Each item has a path and a message:

{
  "success": false,
  "message": "...",
  "data": null,
  "error": {
    "code": "REQUEST_VALIDATION_FAILED",
    "message": "...",
    "details": [
      { "path": ["chatbotName"], "message": "Required" }
    ]
  }
}

Error codes

Code	Meaning
`AUTHORIZATION_HEADER_REQUIRED`	The request has no `Authorization` header.
`AUTHORIZATION_HEADER_NOT_VALID`	The header is not in the form `Bearer YOUR_API_KEY`.
`API_KEY_NOT_VALID`	The key is wrong, or your plan does not include API access.
`REQUEST_VALIDATION_FAILED`	The request body is not valid. See `error.details`.
`REQUEST_METHOD_NOT_ALLOWED`	The endpoint does not support this HTTP method.
`CHATBOT_ID_REQUIRED`	The chatbot ID is missing.
`CHATBOT_LIMIT_REACHED`	You have reached the chatbot limit of your plan.
`CHATBOT_LINKS_LIMIT_REACHED`	You have reached the pages limit of your plan. Returned with status `429`.
`ACCOUNT_INACTIVE`	The account has no active subscription.
`CONVERSATION_CLOSED`	The conversation is resolved. You cannot send messages to it or escalate it.
`HUMAN_TAKEOVER`	A person on your team has taken over the conversation. You cannot escalate it.

Pagination

API v0 has no pagination. List endpoints return all items in one response. If you need pagination, use API v2. See API conventions.

Rate limits

API v0 has no per-request rate limit and sends no rate-limit headers. A 429 status means that a plan quota is used up.

SDKs

The official SDKs use API v2, not v0:

TypeScript SDK (@sitegpt/sdk)
Python SDK (sitegpt)
Go SDK

Names in API v0

API v0 uses older names for some features:

API v0 name	Name in the dashboard
Threads	Conversations
Prompts	Instructions
Quick prompts, conversation starters	Conversation starters
Follow-up prompts	Follow-up suggestions
Custom content	Text snippets
Links	Website pages and other content sources

Move from API v0 to v2 maps every v0 endpoint to its v2 endpoint.

Webhooks

Webhooks are set up per chatbot in Settings > Webhooks. With API v0 you can also set a messages webhook for one conversation. See Webhooks.

Support

Email support@sitegpt.ai with the endpoint, the request, and the full error response.

Chatbots

Appearance

Custom Content

Follow-up Prompts

Icons

Content & Training

Messages

Personas

Instructions

Conversation Starters

Settings

Threads

Whitelabel (Deprecated)

Legacy API v0

Base URL

API key

Response format

Error codes

Rate limits

SDKs

Names in API v0

Webhooks

Support

​Base URL

​API key

​Response format

​Error codes

​Pagination

​Rate limits

​SDKs

​Names in API v0

​Webhooks

​Support

Base URL

API key

Response format

Error codes

Pagination

Rate limits

SDKs

Names in API v0

Webhooks

Support