Developers

An ATS you can build on

A REST API with workspace-scoped keys and an OpenAPI spec, plus an MCP server so AI tools like Cursor and Claude Desktop can work with your hiring data.

Start free Try the live demo

Free during early access · No credit card

List open jobs

curl https://app.otter.diy/api/v1/jobs?status=open \  -H "Authorization: Bearer $OTTER_API_KEY" # 200 OK{ "data": {  "items": [{    "code": "eng-001",    "title": "Senior Backend Engineer",    "status": "open"  }],  "next_cursor": null} }

REST API

Jobs, candidates, applications, interviews and notes under /api/v1. List and create.

Scoped keys

Each key belongs to one workspace, is read-only or read & write, and is stored hashed — shown once.

MCP server

List jobs, search candidates and read or add notes from Cursor or Claude Desktop.

Documented with OpenAPI

The full spec is at app.otter.diy/api/v1/openapi.json, and the API reference in our docs is generated from it. Authenticate with a Bearer key from Settings → API keys.

Base URL: https://app.otter.diy/api/v1
Bearer otter_sk_… keys
No tenant header needed — keys are bound to a workspace

Add a note to a candidate

curl -X POST https://app.otter.diy/api/v1/notes \  -H "Authorization: Bearer $OTTER_API_KEY" \  -H "Content-Type: application/json" \  -d '{"candidate_id": "…", "body": "Strong system design round"}' # 201 Created{ "data": { "id": "…", "visibility": "team" } }

Bring Otter into your AI tools

The Otter MCP server exposes list_jobs, search_candidates, list_notes and create_note. It uses the REST API, so it follows the same keys and permissions.

mcp.json (Cursor)

{  "mcpServers": {    "otter": {      "command": "node",      "args": ["path/to/otter/packages/mcp/dist/index.js"],      "env": { "OTTER_API_KEY": "otter_sk_…" }    }  }} # tools: list_jobs · search_candidates · list_notes · create_note