​

API overview

FinalSay exposes an Agent API under /v1/* for automations (n8n, Zapier, scripts, MCP). It uses your Agent ID and workspace API key from the web dashboard or mobile app—not your personal login. The web dashboard and mobile app use a separate private API with your user session to show agents, approvals, and settings. You do not need that API for integrations; use only the Agent API (or MCP tools that proxy to it) documented here.

​

Other transports

​

Who this is for

​

Base URL

Use the HTTPS base URL provided by your deployment (for example https://api.example.com). All paths below are appended to that host.

​

Agent authentication

Most /v1 requests must include: Exception: GET /v1/agents lists agents for a key using X-Api-Key only (no X-Agent-Id). See Agent API. Typical errors: Details: Agent API.

​

Rate limits & quotas

• Burst limit on POST /v1/approvals: default 60 creates per agent per 60 seconds (sliding window); deployments can change this. Exceeded → 429 rate_limited. See Rate limits.
• Plan / billing caps (when enabled) → 403 USAGE_APPROVAL_LIMIT. See Automation limits & billing.

​

Callbacks & OpenAPI

• Callback contract (HTTP method, body shape, retries, no HMAC): Callback webhooks.
• OpenAPI 3 spec (download / tooling): agent-api-openapi.yaml.

​

Connectivity check

If your host exposes it, GET /health may return { "ok": true } to verify the service is up. Availability depends on your environment.

​

Related

• Agent API — full reference
• n8n · Zapier · MCP
• Credentials