---
title: "Get conversation"
method: GET
path: "/v1/inbox/conversations/{conversationId}"
tags: ["Messages"]
---

# Get conversation

`GET /v1/inbox/conversations/{conversationId}`

Retrieve details and metadata for a specific conversation. Requires accountId query parameter.

## Path parameters

- `conversationId` string, required

## Query parameters

- `accountId` string, required

## Response `200`

Conversation details

- object
  - `data` object
    - `id` string
    - `accountId` string
    - `accountUsername` string
    - `platform` string
    - `status` 'active' | 'archived'
    - `participantName` string
    - `participantId` string
    - `participantVerifiedType` 'blue' | 'government' | 'business' | 'none', nullable — X/Twitter verified badge type. Only present for Twitter/X conversations.
    - `lastMessage` string
    - `lastMessageAt` string, date-time
    - `updatedTime` string, date-time
    - `participants` object[]
      - `id` string
      - `name` string
    - `instagramProfile` object, nullable — Instagram profile data for the participant. Only present for Instagram conversations.
      - `isFollower` boolean, nullable — Whether the participant follows your Instagram business account
      - `isFollowing` boolean, nullable — Whether your Instagram business account follows the participant
      - `followerCount` integer, nullable — The participant's follower count on Instagram
      - `isVerified` boolean, nullable — Whether the participant is a verified Instagram user
      - `fetchedAt` string, date-time, nullable — When this profile data was last fetched from Instagram
    - `metadata` object, nullable — Ad-click attribution for a conversation that started from a Meta ad. Absent when the conversation did not originate from an ad click. Captured once, on the first inbound message after the click, and never overwritten. If the same person later clicks a different ad, the original values are kept. Meta only sends the referral on that first message. This operation currently returns only the `meta_ad_*` family, which covers Instagram Click-to-Direct and Facebook Messenger Click-to-Message. WhatsApp Click-to-WhatsApp attribution (the `ctwa_*` keys, where the ad ID is `ctwa_source_id`) is returned by `GET /v1/inbox/conversations` instead. Every key is optional and only the keys Meta supplied are returned, so read defensively. Meta does not send a campaign or ad set ID, so none is exposed here. More keys may be added over time. Treat any key you do not recognise as an opaque string. Key names differ from the `message.received` webhook on purpose. The webhook forwards Meta's referral verbatim (`ad_id`, `source`, `type`) while the stored conversation record uses the prefixed names below. Renaming either side would break existing integrations, so both spellings are kept.
      - `meta_ad_id` string — The Meta ad ID the user clicked. Always present when a referral was captured.
      - `meta_ad_source` string — Meta-supplied source identifier, for example ADS.
      - `meta_ad_type` string — Meta-supplied referral type, for example OPEN_THREAD.
      - `meta_ad_ref` string — The ref parameter passed through from the ad creative.
      - `meta_ad_title` string — Title of the ad creative at click time.
      - `meta_ad_photo_url` string — Image of the ad creative at click time.
      - `meta_ad_video_url` string — Video of the ad creative at click time.
      - `meta_ad_post_id` string — The organic post the ad promoted, when the ad was a boosted post.
      - `meta_ad_product_id` string — The catalogue product the user clicked, for product ads.
      - `meta_ad_flow_id` string — The Meta flow the ad launched, for flow ads.
      - `meta_ad_captured_at` string, date-time — When Zernio stored this referral. Always present when a referral was captured.

## Other responses

- `401` — Unauthorized
- `403` — Inbox addon required
- `404` — Conversation not found

---

[API](https://skmtc.net/zernio/apis/zernio-api.md) · [All operations](https://skmtc.net/zernio/apis/zernio-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/zernio/zernio-api/revisions/d0ab3b4eb0ae/schema)