API reference / Messaging reads
Read a conversation thread (live)
Written and maintained by The ProspectAPIs team
GET/v1/messages/thread
GET /v1/messages/thread is the ProspectAPIs operation readMessageThread, in the Messaging reads group of the REST API. Read the messages of one conversation thread, incremental by since/cursor. $0.01 per read. Billed per call once the messaging reads are live; while they are not yet on sale the call is free (GET /pricing reports messaging_reads.available). Cost: Launching soon. Send your API key as a Bearer token in the Authorization header.
The quickstart shows this call in context, next to the first requests most integrations make.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| thread_id required | query | string | The thread id from GET /v1/messages. |
| since | query | string | Read only what changed after this value from a previous read. |
| cursor | query | string | Opaque cursor from the previous page. |
| count | query | integer | Messages per page, 1 to 50. |
An unknown query parameter is refused with a 400 rather than ignored, so a typo never widens a search you pay for.
Responses
| Status | Meaning |
|---|---|
| 200 | The thread's messages, read fresh, with coverage. |
| 400 | The request was invalid (e.g. a bad filter or input); nothing was charged. |
| 401 | The API key is missing or invalid. |
| 402 | Out of credits. The body carries top_up_url; nothing was charged. |
| 429 | Too many requests; retry after the window. |
| 503 | This read is temporarily unavailable. Nothing was charged. |
Every error answers with the same JSON body, an error string and sometimes a code; the errors page lists each status and when it happens. A per-key 429 carries Retry-After; see rate limits.
200 response fields
The thread's messages, read fresh, with coverage. The body is a PeopleReadResult.
| Field | Type | Description |
|---|---|---|
| data required | object | The read result. For search, posts, engagers and followers this is { items, page }; for a profile it is the profile object. |
| coverage required | object | How complete the source was. |
| coverage.filled | integer | |
| coverage.of | integer |
| Header | Meaning |
|---|---|
| RateLimit-Limit | Requests this API key may make per minute. |
| RateLimit-Remaining | Requests left in the current one-minute window. |
| RateLimit-Reset | Seconds until the current window resets. |
Code samples
Each sample sends the same request. Set PROSPECTAPIS_KEY in your environment first. Values come from the spec's examples; replace them with your own.
curl -G https://api.prospectapis.com/v1/messages/thread \
-H "Authorization: Bearer $PROSPECTAPIS_KEY" \
--data-urlencode "thread_id=thread id"const params = new URLSearchParams({ thread_id: "thread id" });
const res = await fetch(`https://api.prospectapis.com/v1/messages/thread?${params}`, {
headers: { Authorization: `Bearer ${process.env.PROSPECTAPIS_KEY}` },
});
if (!res.ok) throw new Error(`${res.status}: ${(await res.json().catch(() => ({}))).error ?? res.statusText}`);
const data = await res.json();
console.log(data);import os, requests
res = requests.get(
"https://api.prospectapis.com/v1/messages/thread",
headers={"Authorization": f"Bearer {os.environ['PROSPECTAPIS_KEY']}"},
params={"thread_id": "thread id"},
timeout=30,
)
res.raise_for_status()
data = res.json()
print(data)Billing
Billing reserves before it serves: the call holds what it may cost, serves at most what that hold covers, and refunds the rest when the response closes. Any non-2xx answer refunds the whole hold, so a failed call costs nothing. The response reports your balance in X-Credits-Remaining.
Related
Previous operation: Start a conversation. Next operation: List your connections (live). Every operation, grouped by area, is on the API reference index.
Create a free account to get a key, then run the samples above with your own values.
Was this page helpful?