Skip to main content
The Forest public API exposes a subset of platform data and operations for programmatic access, useful for compliance reporting, audit log archival, SIEM integration, and external tooling. It is not the Gateway API: the Gateway API is the REST surface your own agent can serve to trusted third-party UIs, while this Forest API is Forest’s own platform API, authenticated with an API token you generate in Project Settings.

​
What the API exposes

Trigger a workflow via webhook is also available over HTTP, but it does not follow the base URL and path convention below. Its URL is not assembled from your project and environment — you copy the full, signed URL from the workflow’s trigger settings. See Trigger a workflow via webhook for the contract and Workflow triggers for how to generate the URL.
If you need data access beyond what’s exposed here, you have two options:
  • Use the Forest Agent directly, the agent serves your collections via its own REST API. See the Node.js or Ruby agent reference.
  • Connect via MCP, the MCP server exposes your data, actions, and workflows to AI agents under the same governance.

​
Base URL

All public API requests go to:
Specific endpoints use a path scoped to your project and environment:
See each endpoint page for the exact path and parameters.

​
Authentication

All requests require a Bearer token in the Authorization header:
Tokens must be generated by a user with an Admin role on the project. See Authentication for how to generate and manage tokens.

​
Rate limits

The public API enforces per-token rate limits. See Rate limits for current values, response headers, and best practices for handling throttling.

​
Common use cases

Audit and compliance

Export activity logs to a data warehouse for long-term retention. Build custom audit dashboards. Pull decision traces for regulator inquiries.

SIEM integration

Stream Forest activity into Splunk, Datadog, ELK, CloudWatch, or your existing SIEM.

External collaboration

Sync notes between Forest and external collaboration tools (Slack, Teams, internal CRMs).

Custom reporting

Pull operations data on a schedule and feed it into business reporting tools.

​
Getting started

1

Generate an application token

Project Settings → API Access → Generate New Token. The user generating the token must have Admin role on the project.
2

Make your first request

Use the token in the Authorization header. See Authentication for examples in cURL, Node.js, and Python.
3

Handle rate limits

Read the X-RateLimit-Remaining header in responses. Implement exponential backoff for 429 responses.

​
Next steps

Authentication

Generate and use API tokens.

Rate limits

Understand and handle limits.

Activity logs

The most-used endpoint group.