API Docs
Build with Fortiris data safely
Fortiris API access is designed around scoped, permissioned workflows. Public developer documentation starts here; production integration access is coordinated through Fortiris support so account, billing, and risk data stay protected.
Authentication
Fortiris API access is scoped by authenticated user, workspace, and entitlement. Do not send raw broker credentials through client-side integrations.
Account and Risk Data
Use canonical Fortiris account IDs and server-side validation when reading analytics, connector state, and risk intelligence outputs.
Webhooks
Use webhooks for lifecycle events that need durable processing. Event handling should be idempotent and fail closed on unknown payloads.
Integration Planning
For platform or business workspace integrations, Fortiris supports scoped planning before production API access is enabled.
Need API access?
Tell us what you are integrating, which Fortiris workspace it belongs to, and what data you need. We will help confirm the correct API boundary before credentials are provisioned.
How to get support