Tools & Integrations

Integrate the Turris Public API into your development workflow with the tools below.

MCP Server

The Turris Public API documentation is available as a Model Context Protocol (MCP) server. MCP connects AI tools directly to our documentation, so you get accurate, up-to-date answers about the API without leaving your editor.

Cursor

Install the MCP server in Cursor with one click

VS Code

Install the MCP server in VS Code with one click

Manual Setup

Add the following to your MCP client configuration:

{
  "mcpServers": {
    "turris-public-api": {
      "url": "https://docs.turrisfi.com/mcp"
    }
  }
}

Compatible with any MCP client including Claude Desktop, ChatGPT, Cursor, VS Code, Windsurf, and more.

Postman Collections

Explore and test the Turris Public API directly in Postman with our pre-built collections.

Turris Public APIs on Postman

Browse all collections, fork them into your workspace, and start making requests immediately.

What is inside

One collection, Turris Public API, with four top-level folders:

Folder	Contents
Authentication API	OAuth and Restricted Access Token flows. Shared by both versions.
Health Check	Service heartbeat. Shared by both versions.
v1	The frozen carrier surface: 41 requests across 12 sub-folders, paths shaped `/v1/agents`. No persona segment.
v2	Two persona folders. `Upstream` holds 38 requests across 12 sub-folders, paths shaped `/v2/upstream/agents`. `Downstream` holds 39 requests across 12 sub-folders, paths shaped `/v2/downstream/producers`.

v1 and v2 > Upstream use the same 12 sub-folder names, so a carrier migrating from v1 finds each request in the same place on both. v2 > Downstream does not mirror them. Only Contacts, Licenses and Appointments share a name with a v1 sub-folder; the other nine (Licensed Entities, Producers, Licensing Overview, License Requests, Markets, Corporate Registrations, Compliance Configurations, Documents, Surplus Lines) exist on the agency surface only, and there is no v1 agency surface for them to mirror.

Your credential works in exactly one persona folder and returns 403 in the other. The collection says so in its own folder descriptions: Upstream warns that “an agency credential gets 403 on all of them”, and Downstream that “a carrier credential gets 403 on all of them”. If every request in a folder is refused, you are in the wrong folder rather than misconfigured. Read Which API is mine? to confirm which surface your credential is for and what that 403 looks like.

Choosing a version

Pick the version by picking the folder. Each one sets {{api-version}} for the requests inside it, so a request cannot reach the version you did not choose. You do not need to edit anything to switch.

Getting Started with Postman

Visit the Turris Public APIs workspace on Postman
Fork the collection into your own workspace
Select an environment, or set base-url, client-id and client-secret yourself
Open the version folder you want, then send Authentication API → Get OAuth Token once
Start exploring endpoints

Step 4 stores your token in turris-access-token, and every other request inherits it from the collection. Tokens are interchangeable between versions of the same surface, not across surfaces. A carrier or MGA token works in both v1 and v2 > Upstream, so you can migrate endpoint by endpoint. An agency token works in v2 > Downstream only.

The collection covers the endpoints most integrations use, not the entire API. Each surface has its own complete reference: the Carrier & MGA reference covers /v2/upstream/* and v1, and the Agency reference covers /v2/downstream/*, which is v2 only. Every endpoint in either reference works whether or not it appears in Postman. If you are not sure which reference applies to you, start at Which API is mine?.

Start Here

API Conventions