API Availability
A stable customer-facing REST API and outgoing webhook contract have not been released. This page documents the current boundary so teams do not build against internal interfaces.
Current Integration Boundary
Internal application requests are not a supported public API contract.
No public endpoint contract: do not reuse browser credentials, Supabase public keys, internal RPC names or observed network calls as an integration API. Availability must be confirmed and provisioned by Opsis.
Administrative Records
Authorized company administrators can manage available API-key and integration records in their workspace. A stored record is not evidence that a public endpoint or connector is enabled.
Coordinated Availability
Opsis must confirm the supported scope, authentication method and data permissions for each integration.
Candidate Resource Domains
Future contracts may cover operational domains such as projects, equipment, users and reports, but no routes below are promised today.
- Projects and commercial records
- Equipment and maintenance
- Employees, schedules and approved hours
- Authorized analytics and reports
Subscription Rules Still Apply
An eventual integration cannot grant a company access to a module or source domain outside its plan.
Limits & Versioning
No public rate limit, pagination scheme, response format or version lifecycle is committed. Those details will be documented with a supported release.
Do Not Guess
Internal status codes and request shapes can change without public compatibility guarantees.
Webhooks & Credentials
Outgoing webhooks and managed OAuth connectors are not available in the current product.
- Never place secrets in browser code
- Never commit credentials to source control
- Use least-privilege, scoped credentials when provisioned
- Rotate a credential immediately after suspected exposure
Security Review
Data direction, tenant scope, module entitlements and secret storage must be reviewed before activation.
Evaluating an Integration?
Describe the system, data direction and business event. Opsis will confirm whether the use case is supported, planned or unavailable.