Skip to main content
The FirstTouch Public API exposes the same supported operations as FirstTouch MCP through conventional HTTP requests. Use it for server-to-server integrations that need to work with audiences, flows, contacts, enrichment, tasks, queues, metrics, and other FirstTouch workflows without running an MCP client. The staging API currently contains 65 operations generated from the full FirstTouch MCP tool catalog. Tool names, descriptions, input schemas, validation rules, permissions, and business behavior stay aligned with MCP.

Authentication

Create a user-scoped API key for the selected team and send it through the X-API-Key header.

Quickstart

Call get_current_user, inspect the JSON response, and discover more operations.

API Operations

Open the complete human-readable operation catalog in ReDoc.

​
Staging Endpoints

Every tool operation uses POST. Replace <tool_name> with the MCP tool name shown in the API Operations reference. Example:

​
How It Relates To MCP

The Public API and MCP are two transports over the same FirstTouch operations:
  • The Public API accepts a JSON request body and returns normal JSON.
  • MCP uses the Model Context Protocol and can use browser OAuth or a compatible API key.
  • Both enforce the current user, team, permissions, feature access, credit rules, and workflow validation.
  • Rotating or revoking an API key immediately affects both Public API and MCP requests using that key.
The Public API does not bypass FirstTouch permissions or product entitlements. An API key can only perform operations its creator is currently allowed to perform in the key’s team.

​
Request And Response Format

Send a JSON object matching the selected operation’s input schema. Operations without arguments accept an empty object:
Successful calls return the operation result directly as JSON rather than an MCP JSON-RPC or content envelope.

​
Next Steps