Knowledge base›Endpoints›/backend-api/conversations/{id}

/backend-api/conversations/{id} `endpoint/backend-api-conversations-id`

Endpointsactive first seen 21 Aug 2026 last seen 22 Aug 2026Occurrence 33 of 33 runs on 22 Aug 2026 · instant + thinking

What it is

The endpoint through which the client loads a stored conversation. Until 20 Aug 2026 GET /backend-api/conversation/{id} delivered the canonical object as a mapping tree ({node_id: {parent, children, message}}). Since 21 Aug 2026 GET /backend-api/conversations/{id}?include_has_versions=true&num_turns=100 applies: a flat, paginated messages[] list with current_node and page_info (start_cursor, end_cursor, has_previous_page, has_next_page). Older pages are fetched with &before=<start_cursor>. The message objects themselves are unchanged; only the tree is gone.

Measured: on 20 Aug mapping in all runs, on 21 and 22 Aug messages in all 33 runs (run.conversation_format). The switch is the tracker's first confirmed structure event → [changelog 2026-08-21-conversations-endpoint].

External evidence

Suganthan Mohanadasan, 14 Jul 2026: documents the rebuild of the reference structure on 21 Jul 2026 (result_source gone, IDs as objects). The path switch itself is dated nowhere else in the field; the tracker recorded it first.

For visibility

No proven effect. The endpoint reads out the finished conversation; it decides nothing about search or citations. It matters for tool builders, not for SEO: every bookmarklet and HAR parser that checks for mapping or the old path breaks on this day. That is exactly what happened to the GPT-Spy bookmarklet on 21 Aug and prompted the Lovable quick fix.

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",
    "memory_scope",
    "messages",
    "moderation_results",
    "owner",
    "page_info",
    "pinned_time",
    "plugin_ids",
    "safe_urls",
    "sugar_item_id",
    "sugar_item_visible",
    "title",
    "update_time",
    "voice"
  ]
}

External sources

mohanadasan-2026-07-14

Change history

22 Aug 2026	confirmed	Conversation retrieval switches from /backend-api/conversation/{id} (mapping) to /backend-api/conversations/{id} (messages)
22 Aug 2026	observed	Response shape of /backend-api/conversations/{id} changed: +[context_truncation_continuation] −[]

Open

Does the old path /backend-api/conversation/{id} still answer for some accounts? On 20 Aug it was active for us, from 21 Aug no longer. The Lovable quick fix keeps both paths as a fallback.
The messages objects themselves are unchanged (author, content, metadata); only the tree is gone. Will the tree structure ever return?

/backend-api/conversation/{id} (superseded) run.conversation_format (mapping | messages) grouped_webpages / search_result_groups search_model_queries