Integration · Data, exports and APIs
Sociana + REST API & partner web
Sociana's apps talk to a Rails backend through an app-facing API, and a v3 partner-web surface exists for approved outside teams. There is no published public API, no developer portal and no API keys for self-serve use. If you need programmatic access, ask the team.
Built per event
What it does inside Sociana
The technical stack is React and TypeScript apps over a Rails backend with Firebase and Firestore, an app-facing API format (responser=true) and surfaces for attendee, organiser, single-app, multi-app, public-direct and v3 partner web. Partner data sharing gives a scoped view to an agreed outside team. The API serves Sociana's own apps; there is no public documentation.
What the organiser configures
- Which partner team needs which records
- Scoped access rather than full admin access
- Public web flows that sit outside the app, such as registration pages
- Domain and branding for the partner surface
Data that flows, and where it is stored
| Data | From | To | Stored |
|---|---|---|---|
| Scoped records (for example arrivals for a transport vendor) | Sociana database | Approved partner via partner web | Sociana database; the partner sees but does not own the record |
| Public form submissions | Visitor on a public web flow | Sociana | Sociana database (hosting region on request) |
Data protection (DPDP)
The organiser is the Data Fiduciary and Sociana acts as processor. Ask us for the hosting region and retention period that apply to your occasion; the sub-processor list is on the Sub-processors and integrations page. We do not state a region or retention period on this page.
Security notes
- Partner access is a data-sharing decision for the organiser as Data Fiduciary.
- Ask us about access logging and review.
Set-up checklist
- Name the outside team and the exact data they need.
- Agree read-only or write permissions in writing.
- Set up the partner login model with the team.
- Test with a dummy partner account.
- Review access after the occasion and remove it.
Limits, stated plainly
- No public API, no API keys, no developer docs, no rate-limit policy published.
- Not a headless platform; custom builds are scoped separately.
- Partner access is configured by the team, not self-serve.
Not offered yet
- Public API and developer docs
- Self-serve API keys
At a glance
- Provider
- REST API & partner web
- Status
- Built per event
- Set up by
- The Sociana delivery team, with your accounts
Questions people ask
Can our developers call the Sociana API?
Not as a published product. The API serves Sociana's own apps. If you need a data feed, ask for webhooks, Sheets or partner data sharing.
What is partner web?
A scoped surface where an agreed outside team, such as a hotel or a transport vendor, sees the records it needs without admin access.
Will a public API arrive?
A public API is on the roadmap. There is no date yet; webhooks, Sheets and partner data sharing are the routes today.
Need this connected for your event?
Tell us which tools your team already uses. We will show you where the data lands and who sees it.