Every REG121 site includes an auto-provisioned REST API scoped entirely to that site’s isolated data layer. The API is created at site provisioning time and provides programmatic access to the site’s custom tables, form submissions, and other structured data stored in its dedicated Postgres schema. No additional setup is required to enable the API itself.
The endpoint list, authentication headers, request/response schemas, and API versioning details are not yet published here. This reference will be updated once the public API specification is confirmed with engineering. Do not rely on any API details not listed on this page.
API Design Principles
Each REG121 site operates within its own API endpoint namespace, which maps directly to that site’s isolated Postgres schema. The following principles reflect the current architecture:
- Per-site provisioning. The REST API is created automatically when a site is provisioned. There is no manual activation step.
- Schema-scoped access. The API exposes data from the site’s own Postgres schema only. It does not have visibility into any other site’s schema or any shared data layer.
- Custom table access. The API provides structured access to custom tables and data you define within the site. This includes data written via forms, integrations, or direct API calls.
- Per-site authentication. All API access is authenticated at the site level. Credentials issued for one site are not valid for any other site’s API.
Scope & Isolation
The API for a given site is strictly scoped to that site’s data. A request authenticated against Site A’s API cannot read from, write to, or enumerate the data belonging to Site B. This isolation is enforced at the infrastructure level — it is a property of how each site’s Postgres schema is provisioned and addressed, not solely a matter of access control logic applied at runtime.
This means:
- Cross-site queries are not possible through the REST API.
- Aggregating data across multiple REG121 sites requires an external system to collect and join that data.
- There is no multi-site API surface or tenant-wide administrative API exposed to site operators at this time.
Coming Soon
The following documentation will be added to this page once the relevant specifications are confirmed with engineering:
- Full endpoint reference — paths, HTTP methods, query parameters, and response shapes for all available resources.
- Authentication flow — how API consumers obtain and present credentials, token lifetimes, and rotation procedures.
- Request and response schema documentation — field-level descriptions, data types, and validation rules for each endpoint.
- SDK and client library details — if official client libraries are made available, their usage will be documented here.
Check back for updates, or contact REG121 directly if you have a time-sensitive integration dependency on the REST API. 