Cookies ahead

Our support chat tool "Intercom" would like to collect some more data on you. See the related link for more details.

Docs

fortrabbit / features

🔌

Talk to the platform directly.

Public API

A REST interface to apps, environments, deployments and domains at api.fortrabbit.com/v1. It authenticates with a personal token and is the foundation the CLI and the MCP server build on.

Try for free

Everything the dashboard does, scriptable. Apps, environments, deployments and domains over HTTP, addressed by the same short IDs the dashboard shows. What gets done by clicking can be done by a pipeline, a script or an agent instead.

The layer under everything else

The CLI is a client of this API, and the MCP server is how agents reach it. Anything built directly against it sits at the same level as the tools fortrabbit ships — no second-class interface, no scraping a dashboard that was not built to be scraped.

A reference that cannot drift

The endpoint reference is generated from the API itself, so it always describes what the API actually accepts.

API reference
https://api.fortrabbit.com/v1/docs

Tokens, the entry point and the rate limits, with worked examples:

Public API documentation
https://docs.fortrabbit.com/platform/automation/api
See trust center

Different by design

Frequently asked

What does the API cover?
The dashboard objects

The dashboard objects - Apps, environments, deployments, domains, teams, people and payment methods. Objects are addressed by the same short public IDs the dashboard shows, and collections take a repeated `publicId[]` parameter to fetch several known objects in one call.

#
How does authentication work?
A personal token

A personal token - A token is created in the dashboard and passed as a bearer credential on every request. It acts as the person who created it and sees exactly what that person sees. Tokens do not expire; unused ones are deleted, which takes effect immediately and leaves every other token working.

#
Are there rate limits?
Around 20 per minute

Around 20 per minute - Requests are counted per token in a sliding one-minute window. Every response carries the limit, the remainder and the reset; a rejected request answers `429` with the seconds to wait. Failed authentications are counted separately, per IP address.

#
Is the API stable?
It is in beta

It is in beta - The API is in beta like the platform around it, so breaking changes are possible. The `/v1` prefix marks the shape of the API — pin nothing that cannot be adjusted.

#

Software

Solutions

Workflows

Use cases

Company

Legal

Contact us