Materialize an API chat

curl --request POST \
  --url https://app.gc.ai/api/external/v1/chat/{id}/materialize \
  --header 'Authorization: <api-key>'

{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "title": "<string>",
  "chat_url": "<string>",
  "materialized_at": "2023-11-07T05:31:56Z"
}

Chat

Materialize an API Chat

Surface an API-created chat into chat history and return a shareable deep link.

Chats created through POST /chat/completions stay out of chat history (both the GC AI web app and chat search) until you materialize them. Use the chat_id from a completed completion response. The endpoint is idempotent. Calling it again on an already-materialized chat returns the same link without side effects.

Authorization: User-scoped keys can only materialize chats they created. Organization-scoped keys can only materialize chats created by other organization-scoped keys.

See Chat Visibility for how this works.

POST

chat

{id}

materialize

Materialize an API chat

curl --request POST \
  --url https://app.gc.ai/api/external/v1/chat/{id}/materialize \
  --header 'Authorization: <api-key>'

{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "title": "<string>",
  "chat_url": "<string>",
  "materialized_at": "2023-11-07T05:31:56Z"
}

Authorizations

Authorization

string

header

required

API key for authentication. Format: gcai_xxxxxxxxx

Create API keys in the GC AI app under Settings → API.

Path Parameters

string<uuid>

required

The chat ID

Response

Chat materialized (or already materialized)

string<uuid>

required

The chat ID

title

string | null

required

The chat title, if generated

chat_url

string<uri>

required

Deep link to open the chat in the GC AI web UI

materialized_at

string<date-time>

required

When the chat was materialized

Get Async Job Status Search Chats

⌘I