Skip to main content
Turris is a compliance platform for insurance distribution. The Public API exposes that data programmatically, as two APIs: one for carriers, MGAs and wholesalers reading about the agencies they appoint, and one for agencies and brokerages reading their own record. They run on one platform and share a host, an OAuth flow and an error envelope. Their pagination differs: agency lists are paged, carrier lists mostly return complete arrays. Your credential works on exactly one of them.

ā€‹
Start here

Which API is mine?

One question decides it: do you appoint agencies, or are you the agency? The answer gives you your path prefix, the versions available to you, and the errorType you get back if you call the wrong surface.
Everything else on this site follows from that answer.

ā€‹
How this site is organized

ā€‹
Conventions you need either way

Authentication

OAuth M2M and Restricted Access Tokens. Both methods reach the same endpoints, and a credential belongs to one organization.

Environments

Sandbox and live hosts. Both environments serve both APIs.

Versioning

What v1 and v2 mean, and which version each surface has.

Error handling

The error envelope, and why you branch on errorType rather than on message text.