Docs

Build around decisions already solved in Mongeflow.

Read structured decisions, request deliverables, subscribe to signed events and inspect the exact limits of the API. Decisions themselves are created in the product.

auth.sh

# Authenticate with a bearer key
curl https://mongeflow.com/api/v1/decisions \
  -H "Authorization: Bearer mf_live_xxxxxxxxxxxxxxxxx"

Authentication

Authorization: Bearer mf_live_…

Keys are mf_live_ and mf_test_ bearers, hashed at rest. Create and revoke them in the dashboard.

Decisions

GET /api/v1/decisions

GET /api/v1/decisions lists solved decisions; GET /api/v1/analyses/{id} returns one with includes for scenarios, actions, outcomes, and alerts.

Exports

POST /api/v1/exports

POST /api/v1/exports with an analysis_id and one of eight formats; poll or subscribe to export.ready.

Webhooks

X-Mongeflow-Signature

Every event signed with HMAC-SHA256 in X-Mongeflow-Signature. Verify before trusting.

Rate limits

X-RateLimit-Remaining

30, 120, or 600 requests per minute by plan, with X-RateLimit headers on every response.

OpenAPI

GET /api/v1/openapi.json

The full schema is published at /api/v1/openapi.json (OpenAPI 3.1).

The full reference, with request and response shapes for every endpoint, lives in the developer documentation.

Build on it

The first request is one command away

Keys live in your dashboard, the schema is published, and every event carries a signature you can check.

Get your API keys Full reference