A full programmatic REST API is on the roadmap for Business plan users. If you have an integration
requirement today, contact us at hello@errsol.com.
Base URL
All HTTP routes are served from the main application origin under/api.
OpenAPI and interactive docs
- OpenAPI JSON specification:
/api/docs - Interactive Swagger UI:
/api/docs/ui
Available HTTP endpoints
The following HTTP routes currently exist. All other product capabilities are available through the BrikSync web application, not as HTTP API endpoints.All other product capabilities — properties, units, tenants, leases (list/read), payments,
maintenance, documents, analytics, inspections, vendors, and more — are available through the
BrikSync web application. A programmatic API covering these resources is planned for a future
release.
Response format
Response shapes vary by endpoint type.JSON endpoints
The lease-creation endpoint returns adata payload on success:
data field on errors:
File-download endpoints
The move-out report (/api/leases/move-out-report), payment receipt (/api/payments/receipt), and GDPR export (/api/gdpr/export/[requestId]) return the file directly on success with a Content-Disposition header — not a JSON envelope. Parse the response body as a file, not as JSON.
Error codes
Rate limits
To ensure fair use and platform stability, API requests are rate limited.
If you exceed the rate limit, you will receive a
429 Too Many Requests response with a Retry-After header indicating when you can retry.
Authentication
The API uses browser session authentication. When you sign in to the BrikSync web application, a session is issued and managed automatically. HTTP endpoints that require authentication validate the active session on each request. See the API Authentication guide for details.Support
If you encounter issues, contact the BrikSync support team at briksync.com/contact or email hello@errsol.com.Built by Errsol Technologies LLP