What this connection covers
The Pryseflow Connect API supports approved integration work through authenticated, company-scoped endpoints and documented connector behavior.
An API connection must define the supported entities, read or write direction, authentication, scopes, validation, rate limits, retries, and source of truth before implementation.
Connector API access is separate from the planned read-only tools for future AI domains. Public availability and documentation must be confirmed with Pryseflow.
Verified capabilities and boundaries
- Resolve authenticated access and active-company scope on the server.
- Allow only approved entities and operations for the agreed connector.
- Use strict request validation and predictable response schemas.
- Define which system owns each record and how conflicts are handled.
- Apply documented limits, retries, idempotency, and failure recovery.
- Test tenant isolation and authorisation before production access is enabled.
