Messages

Search conversations

Search your conversations two ways at once, and get back the matching conversations, most-recent match first:

  • Message text: matches words inside message bodies. Case-insensitive and accent-insensitive, exact tokens only (no substrings, no stemming). Each hit carries up to 3 most-recent matching messages. With direction=outgoing you can collect examples of how you write to customers, for example to teach an AI agent your tone of voice.
  • Contact identity: matches the participant's name, username, or phone number as a case-insensitive substring. These hits have matchCount 0 and an empty matches array.

A conversation that matches both ways is returned once, carrying its message matches.

Only platforms whose messages are stored by Zernio are searchable: WhatsApp, SMS, Telegram, Facebook, Instagram, X and Reddit. Bluesky conversations are fetched live from the platform and cannot be searched; those accounts are listed in meta.accountsSkipped.

Billing: Read (free unless it says otherwise) · Rate limit: 120/min

get/v1/messaging/inbox/conversations/search

Request

  • Base URL: https://apihub.co.il
  • URL: https://apihub.co.il/v1/messaging/inbox/conversations/search
  • Auth: HTTP bearer

Query parameters

limitinteger

Maximum number of conversations to return

querystring required

Text to search for, in message content and in the contact's name, username, or phone number

cursorstring

Opaque pagination cursor. Pass back pagination.nextCursor verbatim; do not construct one.

platform'facebook' | 'instagram' | 'telegram' | 'whatsapp' | 'sms' | 'rcs' | 'slack' | 'imessage'

Filter by platform (searchable platforms only)

accountIdstring

Filter by specific account ID

direction'incoming' | 'outgoing'

Only match messages sent to you (incoming) or by you (outgoing). Contact-identity matching is not applied when this is set.

Headers

Idempotency-Keystring

Replay-safe: the same execution is returned instead of charging twice

X-Tagstring

Group calls into one job (e.g. one video) — see GET /v1/usage?tag=…

Response

Completed

idstring

Execution id — stable across internal retries; use it with GET /v1/executions/{id}

status'pending' | 'processing' | 'completed' | 'partial' | 'failed' | 'cancelled' | 'timeout'
operationstring
tagstring nullable

Your X-Tag, if sent

created_atstring date-time
completed_atstring date-time nullable
errorstring nullable

Changes

No recorded changes to this operation across all 2 revisions of this API.