HighLevel · Schema

GetConversationByIdResponse

CompanySoftware-as-a-ServiceMarketingCRMAutomationMarketing Automation

Properties

Name Type Description
contactId string Unique identifier of the contact associated with this conversation
locationId string Unique identifier of the business location where this conversation takes place
deleted boolean Flag indicating if this conversation has been moved to trash/deleted
inbox boolean Flag indicating if this conversation is currently in the main inbox view
type number Communication channel type for this conversation: 1 (Phone), 2 (Email), 3 (Facebook Messenger), 4 (Review), 5 (Group SMS), 6 (Internal Chat - coming soon)
unreadCount number Number of messages in this conversation that have not been read by the user
assignedTo string Unique identifier of the team member currently responsible for handling this conversation
id string Unique identifier for this specific conversation thread
starred boolean Flag indicating if this conversation has been marked as important/starred by the user
View JSON Schema on GitHub

JSON Schema

highlevel-get-conversation-by-id-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/highlevel/main/json-schema/highlevel-get-conversation-by-id-response-schema.json",
  "title": "GetConversationByIdResponse",
  "x-generated": "2026-09-22",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/_original/highlevel-conversations-openapi.json#/components/schemas/GetConversationByIdResponse",
  "type": "object",
  "properties": {
    "contactId": {
      "type": "string",
      "description": "Unique identifier of the contact associated with this conversation"
    },
    "locationId": {
      "type": "string",
      "description": "Unique identifier of the business location where this conversation takes place"
    },
    "deleted": {
      "type": "boolean",
      "description": "Flag indicating if this conversation has been moved to trash/deleted"
    },
    "inbox": {
      "type": "boolean",
      "description": "Flag indicating if this conversation is currently in the main inbox view"
    },
    "type": {
      "type": "number",
      "description": "Communication channel type for this conversation: 1 (Phone), 2 (Email), 3 (Facebook Messenger), 4 (Review), 5 (Group SMS), 6 (Internal Chat - coming soon)"
    },
    "unreadCount": {
      "type": "number",
      "description": "Number of messages in this conversation that have not been read by the user"
    },
    "assignedTo": {
      "type": "string",
      "description": "Unique identifier of the team member currently responsible for handling this conversation"
    },
    "id": {
      "type": "string",
      "description": "Unique identifier for this specific conversation thread"
    },
    "starred": {
      "type": "boolean",
      "description": "Flag indicating if this conversation has been marked as important/starred by the user"
    }
  },
  "required": [
    "contactId",
    "locationId",
    "deleted",
    "inbox",
    "type",
    "unreadCount",
    "id"
  ]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/highlevel-get-conversation-by-id-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.