For developers

The platform exposes two programmatic surfaces:

Surface	Base URL	Shape
REST API	https://api.actionnetwork.world	OpenAPI 3, JSON over HTTPS
MCP server	https://api.actionnetwork.world/v1/mcp	Model Context Protocol, OAuth-scoped

Refer to the API reference for the REST surface, or the MCP server reference when connecting an AI agent.

Documentation for agents

This site publishes the conventions agents expect:

• /llms.txt — the page index
• /llms-full.txt — every page as one document
• Any page as Markdown by appending .md to its URL

What the API reference covers

The reference covers the integrable surface, not the whole API. The platform’s OpenAPI description covers several hundred paths, as it describes the interface used by the portal, desktop and mobile applications. The reference publishes the portion available to an integrator: member data read with an access token — the wikis, workspaces and projects the member belongs to.

Which endpoints a token may reach is not determined here. It is read directly from the API’s own access table, so the reference tracks the platform rather than restating it.

Two endpoints require no token, as they are read before one is held: the OAuth resource metadata an MCP client retrieves to locate the authorisation server, and /v1/whoami, which reports whether a supplied token is valid and what it can reach.

The /v1/public/** endpoints are not documented here

The platform serves its own public pages — the atlas, organisation pages, the blog and the public knowledge base — from endpoints requiring no credentials. These remain reachable, but they exist to serve those pages rather than as an integration surface: no compatibility guarantee is offered, and their shapes change with the pages they support. They are omitted deliberately rather than documented for a use they are not designed for.

Every endpoint in the reference is a GET. This is not an omission; it is the full extent of the REST surface available to an external client. A token is read-only over REST and no scope alters this, so every non-GET request is refused. Writes are performed over MCP, where approximately half the tools are mutating. Documentation for creating a page or moving a task is in the MCP server reference rather than here.

What the reference does not report

Plan gates. Several capabilities require Solo or Org. An endpoint not included in the current plan returns 403, although the reference presents it as available. The plan required for each capability is listed in what your plan includes.

Token narrowing. The reference states which scope an endpoint requires. It cannot report whether a particular token was additionally narrowed to specific organisations, workspaces or spaces. A call within the token’s scopes may still be refused because the resource falls outside its resource filter — see what an external client can reach.

A 403 should therefore be read as a plan or token restriction rather than as a malformed request.

Errors

Every failure returns the same envelope and carries a ticket ID, which allows a support request to be resolved without reconstructing the failure. → Errors