Monotree Open API

The Open API lets external systems work with your Monotree platform. Read and create posts, announcements and courses, browse users and groups, push alerts into chat rooms or walls with incoming webhooks, react to events with outgoing webhooks, and build two-way integrations with HR systems, automation tools or your own backend. AI assistants connect through the MCP server instead.

New to MCP, API and webhooks? See the overview on monotree.com

LLM-friendly docs

The full reference is available as a single plain-text file. Paste it into Claude, ChatGPT or any model before asking it to write integration code.

View llms.txt

Versioning

The API is currently at v1. Breaking changes will result in a new version (e.g. v2); additive changes (new fields, new endpoints) ship within v1.

Base URL

https://customer.monotree.com/api/open/v1

Replace customer with your company's Monotree subdomain. All examples in these docs use the placeholder.

Quick start

Admins create API tokens in the Monotree CMS under Open API → API Tokens. Pick the scopes the integration needs, copy the token (it is shown once), then make your first request:

curl https://customer.monotree.com/api/open/v1/walls \
  -H "Authorization: Bearer mono_your_token_here" \
  -H "Content-Type: application/json"

What's covered

Authentication — API tokens, scopes, IP restrictions and feature-gated endpoints.
Content — Walls, Posts, Comments, Media, Articles, Handbooks, Courses, Surveys, Forms, Announcements, Staff Cards, Events, Calendar Entries, Certificates, Journeys, Achievements.
People and messaging — Users, Groups, Org Chart, Bots, Direct Messages.
Platform — Locales, Statistics, Academy Statistics, Manager Hub, Feedback.
Webhooks — Incoming, Outgoing, Outgoing Reports, and managing both over the API.
Reference — HTTP status codes, Pagination, Rate limiting, Errors, Changelog.

Feedback

Feature requests, bug reports or anything that felt awkward to build against: send it via POST /feedback with a single body string. It lands directly with the developers building the API. See Feedback.