---
title: "Developers"
description: "Call the Sureshake API from your own code, or connect an AI assistant to your reports."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.sureshake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Developers

Sureshake has a REST API for scripts and integrations, and an MCP server that gives an AI assistant read access to your reports.

## Base URL

```text
https://api.sureshake.com
```

Every route is under `/v2`, for example `https://api.sureshake.com/v2/organizations/me`. The version is part of the path. There is no version header.

## What you can reach

What you can call depends on the credential you hold.

| Credential       | How you get it                                 | What it reaches                                                                                                            |
| ---------------- | ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| API key          | Create one in **Settings**, under **Security** | Organizations, most of the directory, collections, company model scenarios, creating a company, and reading a report by ID |
| None             | Nothing to set up                              | Public directory search and profiles, and public search                                                                    |
| OAuth connection | Approve it when your assistant connects        | Read-only report tools over MCP. It does not work on the REST routes                                                       |

> **An API key does not reach every route**
>
> The API reference lists more routes than a key can call. Many routes accept
> only the session token that the Sureshake app gets when a person signs in, and
> you cannot get that token for your own code. Before you build on a route,
> check [which routes accept an API
> key](/developers/authentication/#which-routes-accept-an-api-key).

## Where to go next

- **Quickstart** — [Create a key and make your first call](/developers/quickstart/) with
  `curl`.
- **Authentication and API keys** — [Keys, scopes, errors, pagination and rate
  limits](/developers/authentication/).
- **Connect an assistant** — [Add Sureshake to Claude, ChatGPT, Grok or Gemini](/developers/mcp/) over
  MCP.
- **API reference** — [Every public route](/reference/), with its parameters and response schema.

## Use the spec in your tools

The public part of the API is available as an OpenAPI document, which you can feed to a client generator or an API tool:

```text
https://docs.sureshake.com/reference/openapi.json
```

The spec does not say which credential each route accepts, so use [the list of key routes](/developers/authentication/#which-routes-accept-an-api-key) alongside it.

Source: https://docs.sureshake.com/developers/index.mdx