API Reference

Convertmax exposes HTTP APIs and a remote MCP server. They use different hosts, credentials, and use cases. Pick the reference that matches what you are integrating.

Convertmax API

Base URL: https://api.convertmax.io

Use the Convertmax API when you need to send product, contact, and order data to Convertmax, or to read subscription reports (subscriptions:read).

Authentication uses private API keys (private-...) with OAuth-style scopes. Tenant scope is derived from the key, not from request parameters.

Event API

Base URL: https://event.convertmax.io

Use the Event API when you need to ingest analytics and behavioral events (page views, conversions, clicks, and custom events):

• POST /v1/track/ for first-party event payloads
• Optional Segment-compatible routes (see Segment Compatibility)

Authentication uses your tracking API key via Authorization: Bearer or the ?key= query parameter.

Convertmax MCP

Base URL: https://mcp.convertmax.ai/mcp

Use Convertmax MCP when an AI client (Cursor, Claude, ChatGPT, and others) should query revenue and attribution for a workspace. Connect over Streamable HTTP with OAuth, or an API key when there is no browser.

Event tracking

• Event Tracking — supported event names, payload shapes, and client examples

Webhooks

Send events from external systems (Make.com, your backend, Segment-style payloads) into Convertmax:

• Webhooks — routes, authentication, and payload reference

Quick comparison