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
https://api.sureshake.comEvery 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 |
Where to go next
Quickstart
Create a key and make your first call with
curl.
Authentication and API keys
Connect an assistant
API reference
Every public route, 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:
https://docs.sureshake.com/reference/openapi.jsonThe spec does not say which credential each route accepts, so use the list of key routes alongside it.