For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • Overview
    • Introduction
    • Response Codes
  • API Reference
          • GETGet thread messages
          • GETList seat messages
          • GETGet message
          • PUTUpdate message
          • DELDelete message
LogoLogo
API ReferenceInboxEmailMessages

Get thread messages

||View as Markdown|
GET
https://hublinks.io/rest/accounts/:account_id/seats/:seat_id/inbox/email/threads/:thread_id/messages
GET
/rest/accounts/:account_id/seats/:seat_id/inbox/email/threads/:thread_id/messages
$curl -G https://hublinks.io/rest/accounts/account_id/seats/seat_id/inbox/email/threads/thread_id/messages \
>     -H "X-API-KEY: <apiKey>" \
>     -d limit=100
200Retrieved
1{}

List messages within an email thread. Supports cursor pagination via last_key: make the first request without it, then if the response last_key is non-null, URL-encode the JSON cursor and pass it as ?last_key= on the next request. Repeat until last_key is null.

Was this page helpful?
Previous

Delete thread

Next

List seat messages

Built with

Authentication

X-API-KEYstring
API Key authentication via header

Path parameters

account_idstringRequired
seat_idstringRequired
thread_idstringRequired

Query parameters

limitintegerOptional<=500Defaults to 500
Maximum number of messages to return. Values above 500 are clamped to 500. Defaults to 500 when omitted.
last_keystringOptional

Pagination cursor. Take the last_key object from the previous response, JSON-stringify it, then URL-encode it (e.g. encodeURIComponent(JSON.stringify(last_key))) and pass it here. Omit on the first request. When the response last_key is null, you have reached the end.

Response

Successful response