Convertmax exposes two distinct HTTP APIs. 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 tenant-scoped platform operations:

  • Writeback — queue product, contact, and order upserts and deletes for the app-side writer
  • Read-through — fetch a single product (by SKU), contact, or order record from the app

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.

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

Convertmax APIEvent API
Hostapi.convertmax.ioevent.convertmax.io
Primary useProducts, contacts, ordersAnalytics and conversion events
Key typeprivate-... scoped keysTracking API key
Typical response202 Accepted (writeback) or record JSON (read){} on successful ingest