Responser API in detail
Under the apps sits a backend, and between them travels a consistent response format. Sociana calls that format the responser API, identified by the responser=true convention. It is how the React and TypeScript apps ask the Rails backend for agenda, members, points and everything else, and how screens receive predictable, structured answers. For a buyer, the practical meaning is stability: one format used by attendee, organiser, single-app and multi-app builds means a feature added to the engine can appear across surfaces without per-app rework. It is important to be exact about what this is not. The responser API is internal plumbing for Sociana's own apps and surfaces. Sociana does not offer a public API or a Zapier-style integration catalogue; external data movement is offered through webhooks, Sheets and Airtable connections and partner data sharing.
How Sociana uses it
The responser format belongs to the Technical layer of the platform: apps built on React and TypeScript talk to the Rails engine using it. External integrations use webhooks and connectors, not this API.
Example
Procurement reviewers asking about APIs are told that integrations run through webhooks, Sheets and Airtable and partner data sharing, not a public API.