Knowledge base›Endpoints›/backend-api/conversation/{id} (mapping — back since 25 Sep)

/backend-api/conversation/{id} (mapping — back since 25 Sep) endpoint/backend-api-conversation-id

Endpointsactive first seen 20 Aug 2026 last seen 6 Oct 2026Occurrence 33 of 33 runs on 6 Oct 2026 · instant + thinking

What it is

The conversation retrieval in the mapping format (tree with parent/children). The only path until 20 Aug 2026, superseded on 21 Aug 2026 by the paginated /backend-api/conversations/{id} — and active again since 25 Sep 2026: on loading a conversation the client calls this path FIRST, then the messages version, and keeps polling the singular afterwards (4 calls in 50 s observed). At the same time conversation/{id}/stream_status and conversation/{id}/textdocs disappeared — the polling evidently replaces them.

The difference to the messages version

Same conversation, same moment (evidence 30 Sep 2026, both endpoints compared with a session token plus a DevTools HAR): messages = 9 messages, mapping = 6. The mapping lacks both is_visually_hidden_from_conversation system messages AND the first web.run tool message — the only one carrying metadata.search_model_queries, although it is not hidden. Metadata keys present only in the messages version: search_model_queries, story_events, rebase_developer_message, is_visually_hidden_from_conversation, exclusive_key.

Consequences for tools

Any tool that takes the most recently seen endpoint (as our bookmarklet did up to v2.7.4) has been catching this version since 25 Sep depending on timing — and then shows zero search queries plus a false »no call texts« diagnosis. The tracker lost one run per day from 25 to 29 Sep (last-wins in the capture) until the runner got the messages priority.

For visibility

No direct effect — but a measurement trap: analyses based on this version underestimate search activity entirely.

Structure

{
  "antwort_keys": [
    "async_status",
    "atlas_mode_enabled",
    "blocked_urls",
    "context_scopes",
    "context_truncation_continuation",
    "conversation_id",
    "conversation_origin",
    "conversation_template_id",
    "create_time",
    "current_node",
    "default_model_slug",
    "disabled_tool_ids",
    "gizmo_id",
    "gizmo_type",
    "is_archived",
    "is_do_not_remember",
    "is_read_only",
    "is_starred",
    "is_study_mode",
    "is_temporary_chat",
    "mapping",
    "memory_scope",
    "moderation_results",
    "owner",
    "pinned_time",
    "plugin_ids",
    "safe_urls",
    "sectioned_conversation",
    "sugar_item_id",
    "sugar_item_visible",
    "title",
    "update_time",
    "voice"
  ]
}

Change history

22 Aug 2026confirmedConversation retrieval switches from /backend-api/conversation/{id} (mapping) to /backend-api/conversations/{id} (messages)
22 Aug 2026confirmedEndpoint /backend-api/conversation/{id} no longer observed
26 Sept 2026revertedConversation retrieval switches from ? (messages) to /backend-api/conversation/{id} (mapping)
30 Sept 2026confirmedDouble fetch since 25 Sep: the client loads every conversation via BOTH paths — conversation/{id} (mapping, first + polling replacing stream_status) and conversations/{id} (messages). The mapping does NOT carry the web.run tool message with search_model_queries.
6 Oct 2026revertedEndpoint /backend-api/conversation/{id} no longer observed

Open

Related

/backend-api/conversations/{id} run.conversation_format (mapping | messages)