Resolve a chat link
POST/chat.link.resolve
Parse a Roam chat deep link (e.g. https://ro.am/r/#/d/...) and return the
referenced message.
When the caller has access to the referenced chat, the full message is
returned and readable is true. The message object is the same
shape as a chat.history/chat.search message — same fields, same
mention rendering. When the caller lacks access, the response still
includes the message key (chatId, timestamp, and threadTimestamp
if applicable) with readable: false and no message content — suitable
for rendering a reference without leaking content.
Use /chat.link.create for the reverse
operation — minting a shareable Roam link from a message the caller can
already read.
Access: Organization and Personal.
Required scope: chat:history
OpenAPI Spec: chat-v1.json
Request
Responses
- 200
- 400
- 401
- 404
- 405
- 500
Link resolved. When readable is false the caller lacks access to the chat; only the message key is returned.
Bad request. Common causes:
- Missing
link - Link cannot be parsed
- Link does not contain a message reference
Presented invalid authentication credentials.
The referenced message does not exist.
An unsupported method was requested.
An internal error occurred.