Test mode

Test mode lets you, or an AI agent, call the Tracking API against production with your real program API key and get real responses, without creating a real sale, commission or platform fee. There is no separate test server or test account: you send the same requests to https://api.affitor.com and mark them as test.

Turn it onCopy Anchor Link

Add "test_mode": true inside additional_data on a click, lead or sale request.

# Replace $AFFITOR_API_KEY with your program API key (Program settings > API keys).
curl -X POST https://api.affitor.com/api/v1/track/sale \
  -H "Authorization: Bearer $AFFITOR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "additional_data": { "test_mode": true } }'

{
  "success": true,
  "message": "Test sale event tracked successfully",
  "data": { "eventId": 1234, "programId": 42, "test_mode": true }
}

On a sale, "livemode": false does the same thing as test_mode. "livemode": true does not turn test mode off.

What a test event recordsCopy Anchor Link

Each successful test call stores one event flagged is_test: true and answers with test_mode: true and the new eventId.

• Click: a test click event. affiliate_url is not required.
• Lead: a test lead event. click_id and customer_key are optional (placeholders are stored when they are missing).
• Sale: a test sale event. transaction_id and amount_cents are optional (amount_cents defaults to 9999). A test sale accepts USD, EUR or VND only (422 unsupported_currency otherwise). Sending the same transaction_id twice returns 409 duplicate_transaction, as for a real sale.

A test event is inserted directly. It does not resolve a partner, so it creates no commission and no platform fee, and it never takes over a real customer's attribution. Test sales are also left out of your revenue analytics.

Test clicks and leads count toward your setup checklist: they are how the script and signup checks pass. When the request carries your program API key, it also starts a recalculation of your program's integration status in the background. The response does not wait for it, so the checklist can update a moment later. A test event sent without a key does not trigger it. A test sale never counts as your first real sale.

Test the whole chainCopy Anchor Link

A successful test sale proves your key authenticates, because the sale endpoint refuses a missing or unknown key. A test click or lead can succeed without a valid key, so it proves only that the event was recorded. No single test event proves attribution. To run a synthetic click, signup and sale through the real attribution and commission pipeline, use one of:

• npx affitor onboard, which runs the chain and then polls readiness (CLI commands)
• the MCP tools affitor_run_verification, then affitor_readiness
• Run check on the Payments step of program setup

The steps and limits are in Testing your integration. To send one test event from the terminal: npx affitor test click, lead or sale.

Going liveCopy Anchor Link

Remove test_mode (and livemode: false). Live calls use the same key and the same endpoints. A live sale needs a transaction_id, a positive amount_cents and a customer that already carries attribution: see Track a sale.