Developer

API Docs

Mondaily exposes two ways in from outside the app today: a read-only MCP server that lets AI clients search your workspace, and signed webhooks that tell your systems when records change. Both are scoped to a single workspace.

MCP server (read-only)

Endpoint, using the MCP Streamable-HTTP transport (JSON-RPC 2.0 over POST):

https://api.mondaily.com/api/mcp

Authenticate with a workspace API key, created by an admin in Settings → Integrations:

Authorization: Bearer md_live_…

A key can search and read that workspace's records; it cannot create, change or delete anything. Revoking a key stops it immediately. Available tools:

  • search_records — find records by keyword
  • get_record — fetch one record and its fields by id
  • list_recent — the most recently updated records, optionally of one type

Webhooks

Admins add webhook URLs (https only) in Settings → Integrations and choose the events to receive, such as a record being created, updated or deleted, a deal changing stage, or an invoice being paid. Each delivery is a JSON POST signed in the X-Mondaily-Signature header as t=<unix time>,v1=<hex>, where the hex value is the HMAC-SHA256 of <t>.<raw body> using that webhook's secret. Verify it by recomputing it on your side.

Not public yet

The REST API at /api/v1 is the one the Mondaily app itself uses. It only accepts a signed-in browser session, so API keys don't work there. A full public API reference is on the roadmap.

Need something specific?

Email support@mondaily.com and tell us what you're building.