API Reference/Endpoints

Retrieve a message

GET/api/linkedin/gateway/messages/{message_id}

Looks up a single message by its id and returns the full record — the same shape you get back from List messages in a chat or List all messages, handy when you only have an id on hand (say, from a stored reference) and need the rest of it.

Authentication

Send your personal API key as a bearer token. A missing, malformed or revoked key returns 401.

Path parameters

FieldTypeDescription

message_id *stringThe id of the message to retrieve.

Query parameters

FieldTypeDescription

account_id *stringThe connected account this message belongs to. Must belong to the calling key.

Response fields

FieldTypeDescription

idstringThe message's id.

chat_idstringThe chat the message belongs to.

sender_idstringThe attendee id of whoever sent the message.

textstring | nullThe message body. Null for attachment-only messages.

timestampstringWhen the message was sent, as an ISO 8601 datetime.

is_sender0 | 11 if the connected account sent this message, 0 if it was received.

attachmentsarrayAny images, files, links or other embeds carried by the message.

reactionsarrayEmoji reactions left on the message, each with the reacting attendee's id.

seen0 | 1Whether the message has been read.

edited0 | 1Whether the message text was changed after sending.

deleted0 | 1Whether the sender has since deleted the message.

The full record carries a few more provider-specific bookkeeping fields (delivery state, per-recipient read receipts, and so on) beyond the ones listed above — treat this table as the fields worth building against, not an exhaustive schema.

Errors

·401 Unauthorized. The key is missing, malformed or has been rotated.·403 Forbidden. account_id doesn't belong to this key.·404 Not Found. No message exists with that id on that account.