Read buyer/inquiry messages
beycome_messagesPost-publish stage — read the owner's buyer/inquiry messages (GET /messages).
Read-only. Requires access_token. Two modes:
Omit
thread→ lists the ~20 most recent conversations, newest first, one row per thread (the latest message in each). Useful fields per row:address,prop_id,prop_status,msg(latest text),subject,requested_by/email(the other party),thread,read_msg("0" = unread),attachments, andmessage_type(senderif the owner wrote the latest message, elsereceiver).Pass
thread→ returns that one conversation in full, oldest-first. Use thethreadvalue from a list row to drill in.
The list is not paginated here on purpose (the upstream page param is
overloaded — it sets both page size and page number — so it is not exposed).
Soft-deleted messages are dropped after paging, so a page may hold fewer than
20 rows; that is not an error. The payload is a bare array under data.
A 401 means the token is no longer valid (logged out, or very old) —
re-authenticate with beycome_signin_start then beycome_signin_verify.
To answer a
message, use beycome_reply_message.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| thread | No | Thread id to open one full conversation (the ``thread`` value from a list row). Omit to list the user's recent conversations. | |
| access_token | Yes | Bearer access token from beycome_signin_verify, or a previously saved token from your memory for this user. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||