Developers · product API · OpenAPI 3.1

Same permissions. Same holds. No /serve.

Everything in the interface is available over the API except serving and signing a notice. The OpenAPI document is public, keys come from your own account — no partner programme, no sales call — and every operation an assistant may use is also an MCP tool for Claude, ChatGPT and other assistants.

Open the developer platform Issue a key Download OpenAPI

Not available over the API. There is no POST /serve. Generate, preview and sign a prescribed form over the API. Recording service is POST /api/v1/issued-documents/{id}/record_service — a human confirmation that a notice was served, not a machine that serves it.

What the API is for

Let Claude or ChatGPT work in your account, alongside your email and accounts
Push tenancies from the CRM you already run
Pull the rent range into a pricing tool
Add comparable lettings to a rent review from your own records
Put tribunal referral deadlines into your case management
Show landlords the activity feed in your own portal
Feed the rent roll into finance
Pull service records into case management
Build an integration for other agencies

Working docs

Integrations, getting started, the OpenAPI reference and MCP are on the developer platform.

Integrations API reference MCP and AI

CRM connectors and outbound webhooks are planned and are not live yet. Import a CSV or use the API until they are. Serving a notice is never available over the API. The API and MCP are on Portfolio and the free trial; Solo, the free plan, has no API access. AI assistants connect to the MCP server by signing in as a person, not with an API key.

Run your own properties on it for a month, free

Issue a key in the product. Serving a notice stays a recorded human act. One-month free trial of every feature. No card needed.

Start your free trial