assistant

Rename or pin an AI Assistant thread

Rename a thread, pin or unpin it, or both. The rename is kept beside the store's own title, so the list shows it and the store keeps naming the thread after its first message. A thread that is not yours answers 404, the same as one that does not exist.

patch/assistant/threads/{origin}/{thread_id}/

Request

  • Base URL: https://api.getoneprofile.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.getoneprofile.ai/assistant/threads/{origin}/{thread_id}/
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Path parameters

origin'chat' required

Which store a thread lives in.

ONE MEMBER, on purpose. There were four assistants and four transcript tables; three were retired and there is one assistant now. The enum stays rather than collapsing to nothing, because origin is still half of how a meta row names a thread and is still on the wire, and because a second store arriving is a change to this list rather than to every signature that carries it.

table, find_leads and agent were the other three. Their rows are deleted by a release task in the same release that drops their tables: every read here coerces the column back into this enum, so a row naming a member that no longer exists raises rather than being skipped.

thread_idstring uuid required

Request body

pinnedboolean nullable

True pins the thread to the top; false unpins.

titlestring nullable

The new title. Kept beside the store's own title rather than written into it, so the store keeps naming the thread after its first message and this is what the list shows instead.

Response

Successful Response

created_atstring date-time required
last_message_atstring date-time nullable required
open_pathstring required

Where the dashboard navigates to reopen the thread: its chat.

origin'chat' required

Which store a thread lives in.

ONE MEMBER, on purpose. There were four assistants and four transcript tables; three were retired and there is one assistant now. The enum stays rather than collapsing to nothing, because origin is still half of how a meta row names a thread and is still on the wire, and because a second store arriving is a change to this list rather than to every signature that carries it.

table, find_leads and agent were the other three. Their rows are deleted by a release task in the same release that drops their tables: every read here coerces the column back into this enum, so a row naming a member that no longer exists raises rather than being skipped.

origin_ref_idstring uuid nullable required

The table or saved agent the thread is bound to; null for a lead search or the general chat.

origin_ref_labelstring nullable required

That table's or agent's name, or what a lead search was for; null when the thread is bound to nothing, or its agent is gone.

pinnedboolean required
sharedboolean required

A legacy table thread nobody is recorded as starting, which the whole workspace sees and may rename, pin or delete.

thread_idstring uuid required
titlestring required

Changes

No recorded changes to this operation across all 1 revision of this API.