Rocket.Chat

Rocket.Chat

Rocket.Chat organizes communication around rooms (public channels, private groups, direct messages). Teams group channels; subscriptions are the authenticated user's room memberships.

Operational order

1. Confirm credentials with the current-user profile tool (validates token + user id).
2. List or resolve rooms/channels before message history or member tools (those require room_id).
3. Resolve userId from the users tool before presence lookups.

Data model

• Channels — public rooms (t: c).
• Groups — private rooms (t: p).
• Direct messages — 1:1 rooms (t: d).
• Teams — organizational groupings of channels.
• Subscriptions — rooms the authenticated user follows.

Gotchas

• API URL: Must be the REST base https://<host>/api/v1, not the web UI root and not .../api/v1/me.
• Auth headers: REST calls require X-Auth-Token and X-User-Id. Hidden Unicode in stored token or user-id values causes Illegal header value / encoding errors — values must be plain ASCII.
• Combined token field: Legacy setups may store authToken:userId in one field; prefer separate token and user id fields.
• Message history: Requires room_id (or room_name where supported). List channels, groups, or DMs first to discover ids.
• Pagination: List endpoints use numeric offset and count (default page size 50).