Developer API
開発者API

究極の開発者 API ガイド

安全な Chirps 連携を構築するために検証されたサーバー間 API です。ダッシュボード専用の請求・OAuth、公開ウィジェットコールバック、プロバイダー Webhook、Cron、内部ルートは意図的に除外しています。

Developer API

1. 認証とコア原則

ベースURL: https://chirps.cc

すべてのAPIエンドポイントは、AuthorizationヘッダーにChirps APIキーを必要とします。APIキーは、ダッシュボードの開発者セクションにあるAPIマネージャーから生成できます。

http
Authorization: Bearer <YOUR_CHIRPS_API_KEY>

リクエスト例:

bash
curl -X GET https://chirps.cc/api/billing/usage \
  -H "Authorization: Bearer <YOUR_CHIRPS_API_KEY>" \
  -H "Content-Type: application/json"

標準的なエラー処理

ステータスコード, 説明
ステータスコード説明
200 OKリクエストは成功しました。
400 Bad RequestJSONペイロードの検証に失敗しました。詳細配列が含まれます。
401 Unauthorizedトークンが不足しているか、期限切れです。
402 Payment Requiredワークスペースが請求制限に達しました。
403 Forbiddenユーザーに必要なRBAC権限がありません。
404 Not Found要求されたリソースは存在しません。
500 Server Error予期せぬプラットフォームエラーです。
409 ConflictThe request conflicts with current state, such as a booking slot that is no longer available.
413 Payload Too LargeThe request exceeds the endpoint's documented size limit.
429 Too Many RequestsThe API-key request limit was reached; retry after the current window resets.
503 Service UnavailableA required safety or rate-limit dependency is unavailable. Retry with backoff; the request is rejected rather than processed without protection.

スコープと最小権限

各キーは選択されたスコープだけに制限されます。可能な限り読み取り専用キーを使い、連携ごとに別のキーを作成してください。書き込みスコープに対応する読み取り権限は自動では含まれません。

scopes
assistants:read
assistants:write
analytics:read
artifacts:read
artifacts:write
billing:read
bookings:read
bookings:write
chat:write
connectors:read
connectors:write
conversations:read
conversations:write
knowledge:read
knowledge:write
leads:read
leads:write
telephony:read
telephony:write
widget:write
API key security
APIキーは機密情報です。サーバー側だけで保管し、Webサイトやモバイルアプリに埋め込まず、漏えいした場合は直ちに失効させてください。

API-key rate limit

Each developer key is limited to 300 requests per rolling minute by default. The limit is atomic across all application instances and can be changed by the platform with API_KEY_RATE_LIMIT_PER_MINUTE. A rejected request returns 429; retry only after the window resets.

Developer API

2. アシスタントのライフサイクル(作成)

GET /api/assistants

アシスタントの一覧表示

APIキーのワークスペースに関連付けられたすべてのアシスタントのリストを取得します。

アシスタントの作成

POST /api/assistants

すべての基本設定を持つ新しいアシスタントを作成します。

json
{

  "businessName": "Acme Corp",
  "businessUrl": "https://acme.com",
  "knowledgeBaseType": "both",
  "knowledgeBaseUrl": "https://acme.com/help",
  "knowledgeBaseText": "Raw text content of a document...",
  "knowledgeBaseFileName": "company_handbook.pdf",
  "language": "en",
  "isMultiLanguage": false,
  "tonePersonality": "professional",
  "isCustomPersonality": false,
  "supportEmail": "[email protected]",
  "maxPages": 5,
  "maxDepth": 2,
  "welcomeMessageDelay": 2
}
パラメーター, 型, 必須, 説明
パラメーター型必須説明
businessNameStringはいビジネス名(2~100文字)。
businessUrlStringはいビジネスウェブサイトの有効なURL(最大500文字)。
knowledgeBaseTypeEnumはい次のいずれか: "url"、"document"、"both"、"none"。
knowledgeBaseUrlStringいいえタイプが"url"または"both"の場合に指定する必要があります。
knowledgeBaseTextStringいいえタイプが"document"または"both"の場合の生テキスト。
knowledgeBaseFileNameStringいいえテキストを提供する場合は、アップロードされたファイルの名前。
languageStringはい言語コード(例: "en"、"es")。
isMultiLanguageBooleanいいえ自動翻訳を有効にします。デフォルトはfalseです。
tonePersonalityStringはい例: "professional"、"friendly"。最大100文字。
isCustomPersonalityBooleanいいえカスタムトーンを有効にします。デフォルトはfalseです。
customPersonalityDescriptionStringいいえカスタムトーンが有効な場合の指示(最大2000文字)。
additionalInstructionsStringいいえコアプロンプトの指示(最大10000文字)。
supportEmailStringはいエスカレーション用の有効なメールアドレス。
maxPagesNumberいいえクロールするページ数。最小1、最大100。デフォルトは5です。
maxDepthNumberいいえクロール深度。最小1、最大20。デフォルトは2です。
welcomeMessageDelayNumberいいえ挨拶までの遅延時間(秒)。最小0、最大6。デフォルトは2です。

アシスタントの削除

DELETE /api/assistants/:id

アシスタントを完全に削除し、そのすべてのナレッジノードと履歴を連鎖的に削除します。ペイロードは不要です。

Creation validation and quota safety

Input, Contract
InputContract
knowledgeBaseUrlFor url or both: 1–20 comma-separated public HTTP(S) URLs, with at most 2,000 characters in total.
knowledgeBaseTextRequired for document or both; maximum 2,000,000 characters.
knowledgeBaseFileNameOptional source label; maximum 255 characters.
maxPages / maxDepthRequested values are bounded by both the documented hard limits and the workspace plan.

Creation allowance is reserved atomically before insertion, so concurrent requests cannot exceed the monthly quota. Database insertion failures refund that reservation. A created assistant starts inactive in developer mode; call the setup endpoint and wait for its successful terminal event before publishing it.

Developer API

3. アシスタント分析と統計

アシスタントの作成と利用後すぐに、そのパフォーマンス指標をプログラムで取得できます。

GET /api/analytics/overview?assistantId=uuid&range=30

指定されたアシスタントの利用統計、総メッセージ数、獲得リード数、および一般的なエンゲージメント指標を取得します。range パラメータはオプションです(日数、最小7日、最大365日、デフォルト30日)。

期待されるレスポンス

json
{

  "totalConversations": 1245,
  "totalMessages": 8420,
  "totalLeads": 156,
  "totalBookings": 42,
  "satisfactionRate": 94,
  "avgMessagesPerSession": 6.7,
  "avgSessionsPerDay": 41.5,
  "liveNow": 3,
  "onlineNow": 12,
  "dailySeries": [
    {
      "date": "2026-07-15",
      "conversations": 45,
      "messages": 310,
      "leads": 5,
      "bookings": 2
    }
  ],
  "agentStats": [
    {
      "name": "Jane Doe",
      "messagesSent": 120,
      "csat": 98
    }
  ]
}
プロパティ, 型, 説明
プロパティ型説明
totalConversations数値アシスタントが処理したチャットセッションの総数。
totalMessages数値すべての会話で送信されたメッセージ(ユーザー + AI)の総数。
totalLeads数値抽出されたユニークなリード(名前、メールアドレス、電話番号)の総数。
totalBookings数値正常に予約されたカレンダーアポイントメントの総数。
satisfactionRate数値総評価数に対する肯定的なフィードバック評価の割合(0-100)。
avgMessagesPerSession数値会話あたりの平均メッセージ交換数。
avgSessionsPerDay数値リクエストされた範囲内での1日あたりの平均会話数。
liveNow数値現在、人間のエージェントが引き継いでいるアクティブな会話の数。
onlineNow数値過去2分以内にAIと活発にチャットしているユーザーの数。
dailySeries配列日付ごとの conversations、messages、leads、bookings のカウントを含む日次オブジェクトの配列。
agentStats配列messagesSent および csat(顧客満足度スコア)を含む、人間のエージェントのパフォーマンス指標。
Developer API

4. ナレッジとトレーニング

アシスタントが作成されたら、「ナレッジノード」を介してその頭脳を管理します。各ノードは、データのチャンク(クロールされたURL、アップロードされたドキュメント、または手動のテキストスニペット)を表します。

ナレッジノードの管理

GET /api/assistants/:id/nodes - このアシスタントのすべてのナレッジノードを一覧表示します。

POST /api/assistants/:id/nodes - 新しいナレッジブロックを手動で挿入します。

json
{

  "title": "Return Policy",
  "refined_content": "We offer a 30-day return policy for all unused items...",
  "type": "text",
  "metadata": {}
}

PATCH /api/assistants/:id/nodes/:nodeId - 既存のノードのコンテンツを変更するか、そのアクティブ状態を切り替えます。

json
{

  "title": "Updated Return Policy",
  "refined_content": "We offer a 60-day return policy now...",
  "is_active": true
}

DELETE /api/assistants/:id/nodes/:nodeId - ナレッジブロックを完全に削除します。

POST /api/assistants/:id/nodes/:nodeId/re-crawl - スクレイパーにこのノードに関連付けられたURLを再クロールさせ、そのコンテンツを更新するよう強制します。ペイロード: {}。

AIトレーニング

POST /api/assistants/:id/train - すべてのis_activeナレッジノードをコンパイルし、AIオーケストレーターを使用して新しいマスターシステムプロンプトを動的に合成します。ペイロード: {}。

Upload, crawl, and index consistency

Operation, Limits and guarantees
OperationLimits and guarantees
Manual nodeTitle: 1–200 characters; content: 1–200,000 characters; metadata: object up to 20,000 serialized characters.
File uploadPNG, JPEG, WebP, PDF, DOCX, TXT, or Markdown; maximum 10 MB. Failed extraction creates a disabled repairable node and returns vector_sync_pending: true.
Deep crawlmaxPages is a positive integer capped by the plan (100 hard maximum); depth is capped at 20. Only public HTTP(S) destinations are allowed, including redirects and browser subrequests.
Enable / disableDisabled nodes are removed from the vector index and are also filtered at retrieval time. Re-enable or edit an active node to rebuild its vectors.
Safe replacement
Deep crawl and document re-indexing prepare replacement data before retiring the previous searchable copy. If preparation fails, existing knowledge remains available. A vector_sync_pending response means the record was saved but is not yet guaranteed searchable; call the sync endpoint or retry the edit.
Retired endpoint
POST /api/knowledge/urls is retained only to return an explicit 410 Gone; it never stores data. Migrate to POST /api/assistants/:id/nodes/deep-crawl.
Developer API

5. ウィジェットの外観と動作

Every accepted PATCH field, its real default, bounds, plan behavior, and nested shape.

PATCH /api/assistants/:id/widget-config

Send only the fields you want to change. The API rejects unknown keys and invalid nested data instead of silently storing configuration the widget cannot use.

json
{
  "designPreset": "corporate-soft",
  "primaryColor": "#1972F5",
  "theme": "dark",
  "bubbleStyle": "branded-drawer",
  "bubbleText": "Talk to our team",
  "welcomeMessages": [
    {
      "text": "Hello! How can I help?",
      "delay": 1.5
    }
  ],
  "welcomeSuggestions": [
    "View pricing",
    "Book a demo"
  ],
  "pageVisibility": {
    "mode": "exclude",
    "paths": [
      "/checkout/*"
    ]
  },
  "voiceEnabled": true,
  "voiceName": "Aoede",
  "copilotEnabled": true,
  "gdprConsentEnabled": true,
  "privacyPolicyUrl": "https://example.com/privacy"
}
Field, Type / bounds, Default, Effect, Plan behavior
FieldType / boundsDefaultEffectPlan behavior
primaryColorhex color#00000016進数カラーコード(例: "#000000")。—
designPresetenumdefaultVisual system: default, legacy, corporate, corporate-soft, editorial.—
positionenumbottom-right"bottom-right"、"bottom-left"、"top-right"、"top-left"。—
themeenumlight"light" または "dark"。—
fontFamilyenumdefault"default" (Inter) または "inherit"。—
bubbleStyleenumcircle"circle"、"bar"、"drawer"、"branded-circle"、"branded-bar"、"branded-drawer"。Branded launcher styles require custom-branding access.
bubbleTextstring (1–80)Chat with usバブルの横に表示するテキスト(バー/ドロワースタイル用)。—
customLogoUrlHTTP(S) URL or nullnullカスタムヘッダーロゴ画像へのURL。Requires custom-branding access. Prefer HTTPS or the widget-logo upload endpoint.
titlestring (1–50)business nameウィジェットヘッダーのタイトル。—
headerSubtitlestring (0–100)We typically reply instantlyウィジェットヘッダーのサブタイトル。—
welcomeMessagestring (0–300)Hi! How can I help you today?最初の挨拶メッセージ。—
welcomeMessagesarray (1–5)one greetingOrdered greeting objects with text (1–300) and delay in seconds (0–10).—
welcomeMessageDelaynumber (0–10)2挨拶までの遅延時間(秒単位)。—
welcomeSuggestionsstring[] (max 3)[]最初のクイック返信チップ用の文字列の配列。—
inputPlaceholderstring (1–100)Type your message...メッセージ入力のプレースホルダーテキスト。—
languagelanguage codeassistant languageウィジェットの言語コード(例: "en"、"fr")。—
showBrandingbooleantrueShow the Powered by Chirps attribution.Plans without branding removal always force true.
voiceEnabledbooleantrue音声通話を有効にします。Plans without voice access always force false.
voiceModelstringplatform defaultRealtime voice model identifier. Normally leave unchanged so Chirps can use the supported platform model.—
voiceNameenumFenrir音声応答の音声識別名。利用可能な音声は以下を参照してください。—
fileUploadEnabledbooleantrueユーザーが添付ファイルをアップロードできるようにします。Plans without file uploads always force false.
dictationEnabledbooleantrue音声入力(音声認識)を有効にします。—
copilotEnabledbooleanplan defaultAllow the DOM-navigation Copilot experience.Plans without Copilot always force false.
pageVisibilityobject{ mode: all, paths: [] }ウィジェットが表示されるページを決定します(mode、paths)。—
humanizerEnabledbooleantrueApply the conversational response-style pass.—
promptInjectionProtectionEnabledbooleantrueScreen visitor and uploaded-file prompt injection attempts and keep lower-trust content from overriding assistant instructions.—
rateLimitEnabledbooleantrueチャットのレート制限を有効にします。デフォルトはtrueです。—
rateLimitMaxMessagesinteger (1–500)30ウィンドウ内の最大メッセージ数。デフォルトは30です。—
rateLimitTimeWindowinteger minutes (1–1440)60時間枠(分単位)。デフォルトは60です。—
privacyPolicyUrlHTTP(S) URLemptyプライバシーポリシーへのURL。—
gdprConsentEnabledbooleanfalseShow the compact chat privacy notice before the visitor sends data.—
gdprDataMaskingEnabledbooleanfalse保存前にPIIをマスクします。デフォルトはfalseです。—
cookieConsentEnabledbooleanfalseEnable widget cookie preferences and consent UI.—
cookieConsentAnalyticsEnabledbooleantrueOffer optional analytics in cookie preferences. Analytics events remain blocked until the visitor affirmatively consents.—

Page visibility matching

Use exact paths such as /pricing, or append /* to include descendants such as /docs/*. include shows only matches; exclude hides matches; all ignores paths. Full URLs are normalized to their pathname by the widget.

Available voice names

Zephyr, Aoede, Kore, Leda, Callirrhoe, Despina, Erinome, Laomedeia, Achernar, Pulcherrima, Gacrux, Algenib, Sulafat, Puck, Charon, Fenrir, Orus, Enceladus, Iapetus, Umbriel, Algieba, Autonoe, Rasalgethi, Alnilam, Schedar, Sadachbia, Achird, Zubenelgenubi, Sadaltager

Public runtime configuration
The installed browser widget reads GET /api/assistants/:id/widget-config without an API key. That read is intentionally origin-bound to the authorized business domain in production mode and returns plan-normalized public configuration. It is not a server-to-server developer endpoint; never treat it as a way to read private assistant settings.
Plan enforcement
Chirps normalizes plan-gated settings on both write and public config reads. Custom branding, file uploads, voice, and Copilot cannot be enabled by bypassing the dashboard.
Developer API

6. インタラクティブアーティファクト

The complete configuration model for forms, bookings, cards, CSAT, and custom tools.

GET /api/assistants/:id/artifacts · PUT /api/assistants/:id/artifacts · PATCH /api/assistants/:id/artifacts

Artifacts are tool-driven UI. The model calls the enabled tool and Chirps renders it; integrations must send configuration JSON, never {{ARTIFACT: ...}} strings.

json
{
  "form": {
    "enabled": true,
    "title": "Request a quote",
    "description": "Collect the details needed for a quote.",
    "triggerRules": "When a visitor explicitly asks for a quote.",
    "fields": [
      {
        "key": "name",
        "label": "Full name",
        "type": "text",
        "required": true,
        "placeholder": "Jane Doe"
      },
      {
        "key": "email",
        "label": "Work email",
        "type": "email",
        "required": true
      }
    ],
    "submitLabel": "Request quote"
  },
  "booking": {
    "enabled": true,
    "title": "Book a consultation",
    "description": "Choose an available time.",
    "triggerRules": "When a visitor asks to book a meeting.",
    "services_enabled": false,
    "meetings_enabled": true,
    "requiresScheduling": true,
    "timezone": "Europe/Paris",
    "slotDuration": 30,
    "bufferMinutes": 10,
    "workingHours": {
      "monday": {
        "enabled": true,
        "start": "09:00",
        "end": "17:00"
      },
      "tuesday": {
        "enabled": true,
        "start": "09:00",
        "end": "17:00"
      },
      "wednesday": {
        "enabled": true,
        "start": "09:00",
        "end": "17:00"
      },
      "thursday": {
        "enabled": true,
        "start": "09:00",
        "end": "17:00"
      },
      "friday": {
        "enabled": true,
        "start": "09:00",
        "end": "17:00"
      },
      "saturday": {
        "enabled": false,
        "start": "10:00",
        "end": "14:00"
      },
      "sunday": {
        "enabled": false,
        "start": "10:00",
        "end": "14:00"
      }
    },
    "blockedDates": [
      "2026-12-25"
    ],
    "meeting_intake_fields": [
      {
        "key": "email",
        "label": "Email",
        "type": "email",
        "required": true
      }
    ],
    "submitLabel": "Book meeting"
  },
  "card": {
    "enabled": false,
    "ctaLabel": "View details",
    "ctaUrl": "",
    "description": "",
    "triggerRules": ""
  },
  "csat_survey": {
    "enabled": true,
    "title": "How was your experience?",
    "description": "One-click feedback.",
    "triggerRules": "Only after the request is resolved."
  },
  "custom": []
}
Section, Accepted properties, Runtime behavior
SectionAccepted propertiesRuntime behavior
formenabled, title, description, triggerRules, fields, submitLabelLead capture and structured intake through show_form.
bookingenabled, title, description, triggerRules, services_enabled, meetings_enabled, requiresScheduling, timezone, slotDuration, bufferMinutes, workingHours, blockedDates, categories, services, meeting_intake_fields, submitLabelMeeting or service scheduling through show_booking; supplied values can be prefilled and exact requested slots are verified.
cardenabled, ctaLabel, ctaUrl, description, triggerRulesTransactional rich-card behavior when verified product data exists.
csat_surveyenabled, title, description, triggerRulesThumbs-up/down feedback through show_csat_survey.
customArray of enabled, name, type, description, triggerRules, schema, isCustomPlan-gated custom tool-backed artifacts.

Field schema

Field, Type / bounds, Effect
FieldType / boundsEffect
keystringStable machine key used by prefilled_data and requested_fields.
labelstringVisitor-facing label.
typeenumtext, email, tel, textarea, number, date, url, dropdown, radio, checkbox, slider, select, or location.
requiredbooleanBlocks submission until a valid value is supplied.
placeholderstring (max 200)Optional hint shown inside the control.
optionsstring[]Choices for dropdown, radio, and select controls.
min, max, stepnumberNumeric and slider bounds.
geo_scopeobjectLocation boundary: worldwide, continent, country, state, city, or custom; optional value and map bounds.

Booking service schema

Field, Type / bounds, Effect
FieldType / boundsEffect
id, name, descriptionstringStable service identity and visitor-facing copy.
durationminutesService duration; the configured slot duration is the fallback.
category, pricestringOptional filtering and display metadata.
routing.typeenumvirtual, physical, or phone.
routing.platformenumgoogle_meet, teams, or custom for virtual services.
routing.link, routing.addressstringDestination appropriate to the selected routing type.
intake_fieldsfield[]Service-specific information requested during booking.

Validation limits and scheduling rules

Field, Type / bounds, Effect
FieldType / boundsEffect
fields, meeting_intake_fields, intake_fieldsmax 50 eachEvery field needs a unique machine key, label, and supported type.
services / categoriesmax 100 eachService IDs should remain stable after clients begin storing them.
slotDurationinteger 5–480 minutesLength of generated calendar slots.
bufferMinutesinteger 0–1440 minutesUnavailable gap inserted around bookings.
timezoneIANA time-zone nameBusiness schedule zone, for example Europe/Paris; visitor times are converted for display and calendar invitations.
workingHoursseven day objectsEach enabled day uses 24-hour HH:mm and must end after it starts.
blockedDatesYYYY-MM-DD[] (max 366)Dates unavailable in the business time zone.
custommax 20Custom tools are plan-gated; names and types are required.

Tool-call prefill behavior

Field, Type / bounds, Effect
FieldType / boundsEffect
prefilled_dataobjectValues already learned in chat, keyed by configured field key.
requested_fieldsstring[]Show only the configured fields relevant to this intent.
modemeeting or serviceSelect the general meeting flow or a configured service flow.
selected_service_idstringPreselect a configured service; never invent an ID.
requested_categoriesstring[]Restrict the visible service list to configured categories.
preferred_start_time_isoISO-8601Ask the widget to verify one visitor-requested instant before showing approval.
Structured delivery for custom clients
Artifacts originate from model tool calls. Non-streaming chat responses include an artifacts array; streaming responses emit event: artifacts with { artifacts: [...] }. Chirps also keeps compatibility tags in message text for existing widgets and stored history. New clients should consume the structured field/event and treat message text as display copy.
PUT versus PATCH
PUT requires complete built-in sections and replaces the configuration. PATCH merges each supplied built-in section with the current normalized configuration. Unknown top-level sections are rejected.
Developer API

7. コネクターとツール

Discover provider schemas at runtime, store credentials securely, then activate only the tools an assistant needs.

Start with GET /api/marketplace/connectors. Its provider definitions are the source of truth for credential fields, configuration fields, available tools, defaults, and required values; this keeps custom and future providers discoverable without a documentation release.

json
{
  "provider": "shopify",
  "name": "Shopify",
  "credentials": {}
}
  1. Install the workspace connector record with POST /api/assistants/:id/connectors; credentials must be omitted or {}.
  2. Read its exact field schema from GET /api/marketplace/connectors and activate it with POST /api/assistants/:id/connectors/:connectorId/activate.
  3. Send configValues, optional enabledTools, and optional instructions. Chirps verifies non-custom connectors and discovers the tools before saving the integration.
  4. Rotate secrets by calling the activation endpoint again. PUT only renames a named Custom API.
  5. Use DELETE /api/assistants/:id/connectors with { connectorId } to disable it for one assistant. Use the nested DELETE .../:connectorId only to permanently remove it from the workspace and every assistant.
Field, Type / bounds, Effect
FieldType / boundsEffect
configValuesobject (max 100 scalar values)Exact keys from the marketplace schema. Values are bounded and secrets are write-only.
enabledToolsstring[] (max 200)Optional allow-list of tools discovered from the verified connector.
instructionsstring (max 10,000)Assistant-specific constraints for tool use.
namestring (max 120)Optional rename during activation, supported only for named Custom APIs.
Credential handling
Connector secrets are write-only. API responses return safe metadata, never raw stored credentials. Use one least-privilege provider credential per integration. Remote SSE MCP and Custom API endpoints must use a publicly routable HTTPS URL; local and private-network targets are rejected.
Developer API

8. 連携とデプロイ

アシスタントの設定とトレーニングが完了したら、主に2つの方法でデプロイできます。

オプションA: ウェブ埋め込み (フロントエンド)

アシスタントを標準的なウェブサイト(WordPress、Shopify、Reactなど)に統合する最も簡単な方法です。埋め込みコードは完全に決定論的です。取得するためのエンドポイントは必要ありません。サイトの<head>にこれを追加するだけです。

html
<script>
  window.chirpsConfig = { assistantId: "YOUR_ASSISTANT_ID" };
</script>
<script src="https://chirps.cc/embed.js" async></script>

オプションB: ヘッドレス連携 (バックエンド / CRM / ボット)

カスタムクライアント(Discordボット、Telegram連携、ネイティブiOSアプリなど)を構築している場合、ウェブ埋め込みは使用しません。代わりに、/api/chatエンドポイントと直接やり取りします。

POST /api/chat または /api/chat?stream=true

重要: ヘッドレスおよびサーバー間の呼び出しには Authorization: Bearer <YOUR_CHIRPS_API_KEY> が必要です。公開のオリジン制限フローを使うのは、設置済みブラウザーウィジェットだけです。APIキーをフロントエンドJavaScriptに入れないでください。

json
{

  "assistantId": "123e4567-e89b-12d3-a456-426614174000",
  "sessionId": "unique-session-id-for-user",
  "conversationId": "optional-uuid",
  "message": "Hello, I need help with my billing."
}

*(multipart/form-dataがtrueの場合、添付ファイル用にfileフィールドを持つfileUploadEnabledもサポートします。)*

パラメーター, 型, 必須, 説明
パラメーター型必須説明
assistantIdStringはいアシスタントのUUID。
sessionIdStringはいご自身で生成してください。 チャット履歴をグループ化するための、ご自身のシステムからのユニークな識別子(例:DiscordユーザーID、TelegramチャットID、またはランダムなUUID)。
messageStringはいメッセージのテキストコンテンツ(最大5000文字)。
conversationIdStringいいえ会話のUUID(最初のリクエストで返されます)。
idStringいいえ重複排除を防ぐためのオプションのクライアント側メッセージID。

モード1: 標準JSONレスポンス (デフォルト)

/api/chatにPOSTリクエストを送信する(ストリームパラメーターなしで)と、完全なAI応答を待ち、標準のJSONオブジェクトを受け取ります。

json
{

  "message": "Here is the information you requested...",
  "conversationId": "uuid-of-conversation",
  "messageId": "uuid-of-message"
}

*(is_active_agent: trueが返された場合、人間がチャットを引き継いでおり、messageはnullになります。)*

モード2: サーバー送信イベントストリーミング (?stream=true)

URLに?stream=trueを追加すると、リアルタイムのサーバー送信イベント(SSE)ストリームを受信します。コードは以下の特定のイベントタイプをリッスンする必要があります。

  • `event: token`: {"text": "chunk"}を含みます。AIの応答テキストの各チャンクに対して発火します。
  • `event: status`: {"text": "Searching knowledge base..."}を含みます。バックエンドツールの実行状態を表します。
  • `event: done`: {"messageId": "uuid", "conversationId": "uuid", "message": "full text"}を含みます。生成が完全に完了したときに発火します。
  • `event: error`: {"error": "Error message"}を含みます。レート制限またはエラーが発生した場合に発火します。

ライブ引き継ぎエンドポイント

GET /api/chat/sessions

過去のセッションを取得します。

POST /api/chat/toggle-agent

人間による引き継ぎのためにAIを一時停止します。ペイロード: { "sessionId": "...", "isActive": true }

POST /api/chat/agent-message

人間のメッセージを送信します。ペイロード: { "sessionId": "...", "message": "..." }

Complete chat response contract

json
{
  "message": "I've opened the booking calendar for you.",
  "messageId": "uuid",
  "conversationId": "uuid",
  "artifacts": [
    {
      "type": "booking",
      "title": "Book a consultation"
    }
  ],
  "sources": []
}

A human takeover returns { message: null, conversationId, is_active_agent: true }. A streaming request can therefore return JSON before an SSE stream begins; check the response Content-Type.

Complete SSE event reference

Event, Payload and behavior
EventPayload and behavior
token{ text } — committed assistant text chunk.
status{ text } — tool or retrieval progress for user-facing status UI.
artifacts{ artifacts: [...] } — structured tool-generated UI payloads.
sources{ sources, tag } — structured citations when enhanced streaming is enabled.
provisional{ text } — temporary pre-tool text with X-Chirps-Stream-Version: 2.
reset{} — discard accumulated provisional text.
commit{} — commit accumulated provisional text.
done{ messageId, conversationId, message } — authoritative final message.
error{ error } — terminal generation error.
Enhanced streaming
Send X-Chirps-Stream-Version: 2 to receive provisional/reset/commit and structured source events. Clients that do not implement those events should omit the header and rely on token, artifacts, done, and error.
Developer API

9. 高度なアシスタント設定

PATCH /api/assistants/:id

コア設定の更新

アシスタントのコア設定、ペルソナ、およびスクレイピング範囲を変更します。

json
{

  "business_name": "Acme Corp",
  "business_url": "acme.com",
  "business_description": "We sell anvils.",
  "system_prompt": "You are a helpful assistant.",
  "language": "en",
  "tone_personality": "Friendly",
  "support_email": "[email protected]",
  "additional_instructions": "Never mention the Roadrunner.",
  "is_multi_language": true,
  "is_dev_mode": false,
  "is_active": true,
  "max_pages": 15,
  "max_depth": 2,
  "widget_config_merge": {
    "rateLimitEnabled": true
  }
}

*注: すべてのフィールドはオプションです。更新したいフィールドのみを送信してください。*

アシスタントの削除

DELETE /api/assistants/:id

アシスタントを完全に削除し、すべてのナレッジノード、会話、メッセージに削除をカスケードします。アシスタントが完全に設定されていなかった場合、月間作成クォータが返金されます。

Developer API

10. 電話機能と音声

GET /api/phone-numbers - 利用可能な番号を一覧表示します。

POST /api/phone-numbers/:subscriptionId/assign assigns an already-purchased Chirps phone subscription to an assistant. Send { "assistantId": "uuid" }; send { "assistantId": null } to unassign it. This endpoint does not purchase or provision a new number.

POST /api/assistants/:id/outbound - 発信をトリガーします。 Payload: { "phoneNumber": "+123...", "callReason": "Confirm the requested appointment", "conversationId": "optional-uuid" }

Developer API

11. リード抽出

GET /api/leads?assistantId=uuid&page=1&limit=50&status=new - AIが会話中に抽出した、ページ分割された構造化リードを取得します。

GET /api/leads?id=leadId - 完全な会話トランスクリプトを含む、単一リードの詳細を取得します。

Public lead response

Lead objects contain id, assistant_id, conversation_id, session_id, name, email, phone, status, notes, artifact_id, ai_score, ai_summary, form_data, created_at, and the assistant business name. Internal voice-confirmation/idempotency identifiers are never returned.

Developer API

12. 予約とカレンダー

GET /api/bookings?assistantId=uuid&start=ISO-8601&end=ISO-8601 - アシスタントによってスケジュールされたカレンダーの予定を取得します。日付でフィルタリングすることも可能です。

GET /api/bookings?id=bookingId - 会話のトランスクリプトを含む、単一の予約の詳細を取得します。

DELETE /api/bookings/cancel?id=bookingId - 有効な予約をキャンセルします。Chirpsの代替キャンセルメールを連携側で意図的に抑止する場合に限り、&silent=true を追加してください。

POST /api/bookings/reschedule - 予約を調整します。ペイロード: { "bookingId": "uuid", "newStartTime": "ISO-8601", "newEndTime": "ISO-8601" }

Public booking response and time zones

Booking objects contain the public appointment, guest, status, notes, and timestamp fields plus business_timezone. Times are ISO-8601 instants; format them in the viewer's time zone while preserving the returned business zone for schedule context. Internal confirmation IDs, provider calendar-event IDs, and database range columns are omitted.

Developer API

13. アカウントと請求の使用状況

GET /api/billing/usage

ワークスペースの請求サイクル使用状況、サブスクリプションプランの制限、およびアシスタントの総数を取得します。注: APIキーを使用する場合、リクエストは自動的にAPIキーのワークスペースにスコープされるため、teamIdを提供する必要はありません。

レスポンス (`200 OK`):

json
{

  "planName": "Pro",
  "periodStr": "2023-10-01",
  "assistantCount": 3,
  "usage": {
    "message_count": 1450,
    "harvest_count": 12,
    "recrawl_count": 5,
    "train_count": 2,
    "assistants_created_count": 1,
    "voice_minutes_used": 0,
    "sms_count": 0,
    "email_count": 0,
    "whatsapp_count": 0
  },
  "limits": {
    "messages": 5000,
    "assistants": 5,
    "training": 50,
    "recrawls": 20
  },
  "workspaceOwnerId": "uuid"
}
Developer API

14. 完全なエンドポイント一覧

The reviewed, API-key-compatible surface. Paths and JSON property names are never translated.

What belongs in the public developer API

These routes accept a scoped Chirps API key and enforce its workspace boundary. Dashboard-only billing/OAuth routes, browser widget callbacks, provider webhooks, cron jobs, and internal MCP routes are intentionally excluded.

Retries and idempotency
Only chat messages accept a stable client id for duplicate protection. Do not automatically retry other write operations unless the response is clearly safe to retry. 402 means a plan quota was reached; 429 means throttled; 5xx may be transient.

Assistants

Method, Path, Scope, Request, Successful result
MethodPathScopeRequestSuccessful result
GET/api/assistantsassistants:read—Assistant array; credential fields omitted
POST/api/assistantsassistants:writeAssistant creation JSONCreated assistant and setup identifiers
GET/api/assistants/:idassistants:read—Assistant configuration; secrets omitted
PATCH/api/assistants/:idassistants:writeSupported fields onlyUpdated assistant
DELETE/api/assistants/:idassistants:write—Deletion confirmation
GET/api/assistants/:id/setupassistants:read—Setup and crawl status
POST/api/assistants/:id/setupassistants:writeEmpty bodySSE setup progress stream
GET/api/analytics/overview?assistantId=:id&range=30analytics:readQuery: range 7–365Engagement, lead, booking and agent metrics

Knowledge and training

Method, Path, Scope, Request, Successful result
MethodPathScopeRequestSuccessful result
GET/api/assistants/:id/nodesknowledge:read—Knowledge node array
POST/api/assistants/:id/nodesknowledge:write{ title, refined_content, type?, metadata? }Stored and vectorized node
PATCH/api/assistants/:id/nodes/:nodeIdknowledge:write{ title?, refined_content?, is_active? }Updated and re-vectorized node
DELETE/api/assistants/:id/nodes/:nodeIdknowledge:write—Node deletion confirmation
POST/api/assistants/:id/nodes/:nodeId/re-crawlknowledge:writeEmpty bodyRefreshed URL node
POST/api/assistants/:id/nodes/uploadknowledge:writemultipart/form-data: file, title?Extracted knowledge node
POST/api/assistants/:id/nodes/deep-crawlknowledge:write{ maxPages? }SSE crawl progress stream
POST/api/assistants/:id/nodes/syncknowledge:writeEmpty bodyVector store synchronization result
POST/api/assistants/:id/trainknowledge:writeEmpty bodyCompiled assistant prompt
POST/api/assistants/:id/harvestknowledge:writeEmpty bodyConversation insights added to knowledge
POST/api/knowledge/urlsknowledge:writeDeprecatedAlways returns 410 with the assistant-scoped deep-crawl replacement path

Widget, artifacts and connectors

Method, Path, Scope, Request, Successful result
MethodPathScopeRequestSuccessful result
PATCH/api/assistants/:id/widget-configwidget:writePartial widget configurationNormalized widget configuration
POST/api/assistants/:id/widget-logowidget:writemultipart/form-data: file (PNG/JPEG/WebP, max 2 MB)Public logo URL
GET/api/assistants/:id/artifactsartifacts:read—Form, booking, card and CSAT configuration
PUT/api/assistants/:id/artifactsartifacts:writeComplete artifact configurationNormalized configuration
PATCH/api/assistants/:id/artifactsartifacts:writePartial artifact configurationMerged normalized configuration
GET/api/marketplace/connectorsconnectors:read—Installable connector definitions; no credentials
GET/api/assistants/:id/connectorsconnectors:read—Workspace connectors and assistant integrations
POST/api/assistants/:id/connectorsconnectors:write{ provider, name, credentials?: {} }Installed connector record; no operational access yet
PUT/api/assistants/:id/connectors/:connectorIdconnectors:write{ name } (named custom APIs only)Renamed connector; credentials omitted
DELETE/api/assistants/:id/connectorsconnectors:write{ connectorId }Connector disabled for this assistant only
DELETE/api/assistants/:id/connectors/:connectorIdconnectors:write—Workspace connector and all assistant integrations deleted
POST/api/assistants/:id/connectors/:connectorId/activateconnectors:write{ configValues, enabledTools?, instructions?, name? }Activated integration and tool list

Conversations, leads and bookings

Method, Path, Scope, Request, Successful result
MethodPathScopeRequestSuccessful result
POST/api/chat or /api/chat?stream=truechat:write{ assistantId, sessionId, message, conversationId?, id? }JSON reply with artifacts/sources or SSE token/artifacts/status/done events
GET/api/chat/sessions?assistantId=:idconversations:read—20 most recent session summaries
GET/api/assistants/:id/conversations?limit=20&status=activeconversations:readQuery: limit 1–50, status optionalConversation summaries
DELETE/api/assistants/:id/conversationsconversations:write{ conversationIds: [uuid] } (max 100)Deletion confirmation
POST/api/chat/toggle-agentconversations:write{ sessionId, isActive }Takeover state
POST/api/chat/agent-messageconversations:write{ sessionId, message }Stored human-agent message
POST/api/chat/typingconversations:write{ assistantId, sessionId, isTyping }Typing-state confirmation
POST/api/chat/followup-draftconversations:write{ conversationId|leadId, assistantId?, channel? }AI-generated draft; consumes AI-message usage
POST/api/chat/conversation-followupconversations:write{ conversationId|leadId, channel, recipient, subject?, message }Dispatched follow-up result
GET/api/leadsleads:readQuery: id, or assistantId with page, limit, statusLead detail with transcript or paginated leads; internal confirmation identifiers omitted
POST/api/leadsartifacts:writeArtifact submission JSONCaptured lead/booking result
PATCH/api/leadsleads:write{ leadId, status?, notes? }Updated lead
DELETE/api/leadsleads:write{ leadId } or { leadIds: [uuid] }Deletion count
GET/api/bookingsbookings:readQuery: id, or assistantId with start and endBooking detail or booking array; provider and idempotency identifiers omitted
DELETE/api/bookings/cancel?id=:idbookings:writeQuery: silent=true optionalCancellation and calendar-sync state
POST/api/bookings/reschedulebookings:write{ bookingId, newStartTime, newEndTime }Updated booking or available alternatives

Telephony and account

Method, Path, Scope, Request, Successful result
MethodPathScopeRequestSuccessful result
GET/api/phone-numberstelephony:read—Numbers and assignable assistants in this workspace
POST/api/phone-numbers/:subscriptionId/assigntelephony:write{ assistantId } or { assistantId: null }Routing update confirmation
POST/api/assistants/:id/outboundtelephony:write{ phoneNumber, callReason, conversationId? }Provider call SID and conversation ID
GET/api/billing/usagebilling:read—Workspace plan, limits and current usage
GET/api/metadata?url=:httpsUrlartifacts:readQuery: public HTTP(S) URLBounded page title, description and image metadata
始める準備はできていますか?

アシスタントを起動する
10分以内に。

サインアップし、サイトでトレーニングし、アラートをカスタマイズし、Web サイトに埋め込みます。