Client authors
Talking to a RIM server from your own client: the HTTP and GraphQL contract, sessions and CSRF, pagination, messaging, search and the change feed.
The API
- Talking to a server over HTTPThe HTTP contract a client sees: the routes, how a session and its CSRF token work, which origins a browser may call from, the error codes, pagination and how a client tells which server version it talks to. The GraphQL …rim-server/docs/api.md
- Pagination ContractThis repo uses cursor-based pagination for any list that can grow without bound (messages, inbox conversations, etc.). The goal is: stable ordering, no duplicates between pages, and consistent semantics across all …rim-server/docs/pagination.md
- Messaging ContractThis document describes the backend contract for conversations, messages, threads, and attachments.rim-server/docs/messaging.md
- Message Search (Full-Text Search)searchMessages runs Postgres full-text search over message text, scoped to conversations the requesting actor can see. This document covers the query operator syntax, the ranking/pagination design, and the visibility …rim-server/docs/search.md
- Message Change FeedThe change feed lets a client ask "what changed in these channels since I last synced" and get every message created, edited or deleted since then, in order, with a cursor it can store. It is the server half of the …rim-server/docs/message-change-feed.md