hosting

GET /v1/migrations/agent/conversations/{conversationId}

One conversation, every turn, with what the agent did on each.

All hosting endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/migrations/agent/conversations/{conversationId} \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Every agent turn lists the actions it ran and whether each succeeded, beside what it said. That is deliberate: an assistant that says it has started moving your site either called the action or did not, and the record lets you see which. Requires sites.view.

Parameters

NameTypeRequiredWhat it is
conversationId (path)stringYes—

Response

NameTypeRequiredWhat it is
idstringYes—
titlestringYesYour own opening words, trimmed — never a generated summary.
opened_bystring<customer, staff, agent>Yes—
site_idstringYes—
created_atstringYes—
updated_atstringYes—
turnsMigrationAgentTurn[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 422 · 429