Skip to main content
The REST API covers the parts of Rally that connect to your own systems. It is not a second way to run the program; for that, use the app or an agent over MCP.

Base URL and authentication

Create a key under Settings → API keys, pick the scopes it needs, and send it as a bearer token:
Keys start with co_ and are shown once. Requests and responses are JSON; amounts are in minor units (cents); times are RFC 3339.
API keys are for the REST API. Agents connecting over MCP use agent keys from Settings → Agents & MCP, which carry a role rather than scopes.

Scopes

Endpoints

Attribution

See Tracking and attribution for where these fit.

Events

POST /v1/events records something a customer did that a reward rule may pay for. Fields: kind (signup, activation, install, connect, action, lead or custom) and name (your own event name), who it was (external_customer_id, or creator_email / creator_code for things a creator did), occurred_at, a free-form payload, and a dedupe_key so retries are safe. 201 new, 200 seen before.

Creators

Benefits

Exports

GET /v1/exports/{kind} returns a zip of CSV files. Kinds: creators, candidates, applications, briefs, resources, content, analytics, attribution, ledger, payouts, audit, full. The ledger, payouts and full kinds need the * scope.

Embed tokens

POST /v1/embed/tokens mints a token that signs one creator into one portal module inside your app. See Embed the creator portal.

Webhooks

GET, POST and DELETE /v1/webhooks, plus GET /v1/webhooks/events for the event names. The same can be done under Settings → Webhooks. See Webhooks.

Errors

Errors are JSON with an error message and a code. 401 is a missing or revoked key, 403 a scope the key does not have, 404 an id not in your workspace, 409 a state conflict, 429 too many requests.