API Reference · v1

One API.
Everything you track.

REST endpoints for the dashboard, S2S postbacks for your traffic sources, and signed webhooks for your own systems. JSON in, JSON out.

baseapi.mytrack360.com/v1

authBearer

rate limit10k req/min

POST /v1/events201 · 142ms

$ curl https://api.mytrack360.com/v1/events \
  -H "Authorization: Bearer mk_live_••••" \
  -d '{
    "click_id": "ck_3aZ9q8XpL2",
    "type": "conversion",
    "payout": 24.50
  }'

→ {
    "id": "ev_8H2nQpRz",
    "click_id": "ck_3aZ9q8XpL2",
    "attributed": true,
    "created_at": "2026-06-13T11:42:08Z"
  }

Three surfaces

REST, postbacks, webhooks.

Same payload schema across all three. Same signing scheme. Same versioning policy.

REST API

Campaigns, reports, events, leads. Cursor pagination, NDJSON streaming, idempotency keys.

Postbacks (S2S)

Server-to-server callbacks fired on every conversion. HMAC-signed, exponential retry up to 24h.

Webhooks

Subscribe to events: conversion.created, lead.forwarded, campaign.cap_hit, and 18 more.

01 · Authentication

Bearer tokens. Per-org scoped.

Generate a key

Go to Settings → API, create a key, and scope it to read/write per resource. Keys never leave the org boundary.

Per-org isolation
Read / write / admin scopes
Rotate without downtime
Audit log on every call

curl

curl https://api.mytrack360.com/v1/campaigns \
  -H "Authorization: Bearer mk_live_••••••••••" \
  -H "Content-Type: application/json"

02 · Endpoints

Core resources.
Six routes, infinite leverage.

Every route is JSON in, JSON out. NDJSON for streaming. ISO 8601 for time. RFC 3339 for everything else.

POST/v1/eventsRecord a conversion or custom event from your server.GET/v1/campaignsList all campaigns in the current organization.POST/v1/campaignsCreate a campaign with offers, flows and traffic source.GET/v1/clicks/{id}Look up a single click by its tracker ID.POST/v1/postbacks/testFire a signed test postback to a given URL.GET/v1/reports/runStream a report as NDJSON with custom dimensions & metrics.

03 · Example

POST /v1/events

The same shape used by postbacks, webhooks, and the dashboard's inline tester.

Request

POST /v1/events HTTP/1.1
Host: api.mytrack360.com
Authorization: Bearer mk_live_••••
Content-Type: application/json

{
  "click_id": "ck_3aZ9q8XpL2",
  "type": "conversion",
  "payout": 24.50,
  "currency": "USD",
  "meta": { "order_id": "A-1042" }
}

Response · 201

{
  "id": "ev_8H2nQpRz",
  "click_id": "ck_3aZ9q8XpL2",
  "type": "conversion",
  "payout": 24.50,
  "currency": "USD",
  "created_at": "2026-06-13T11:42:08Z",
  "attributed": true
}

One API.Everything you track.