Management API

The Notiflows Management API manages your notiflows as code — create and update notiflow definitions, manage their lifecycle (publish, rollback, activate), inspect versions, edit step templates, read channels, and trigger runs. It is the surface behind the Notiflows CLI, the MCP server, and the agent toolkit.

Base URL

https://api.notiflows.com/management/v1

Authentication

All endpoints authenticate with an account token (prefix nf_at_), passed as a Bearer token:

• Authorization: Bearer nf_at_…

Create an account token in the Notiflows dashboard (Account tokens) — see Account tokens for how they're scoped, audited, and rotated. Project-scoped endpoints include the project slug in the path (/projects/{project_slug}/…).

API Endpoints

Identity

Verify the calling token and list the projects it can access (whoami).

Notiflows

Create, update (upsert), read, list, publish, rollback, activate/deactivate, archive, and run notiflows. Notiflows are addressed by their stable handle.

Versions

Inspect a notiflow's copy-on-write version history.

Steps

Update individual steps within a notiflow's draft.

Templates

Read and upsert per-step channel templates.

Channels

Read the project's configured delivery channels (read-only here — channels are configured in the dashboard).

Getting Started

1. Create an account token in the Notiflows dashboard.
2. Send it as Authorization: Bearer nf_at_… on every request.
3. Address notiflows by handle and scope requests to a project via the /projects/{project_slug} path.

The CLI and MCP server wrap these endpoints — most users interact with the Management API through those rather than directly.