Access to individual endpoints can be restricted per account. If a request to this endpoint returns
403 with error code endpoint_not_enabled and you expect to have access, contact your account representative.GET /v1/reports/outclick endpoint returns the outclick events recorded
for your account — product clicks by default, or merchant clicks with offer_type=merchant.
A product event includes the click metadata, the price and provider data captured at click time,
the product name and direct URL from the stored offer snapshot, and the client details; a merchant
event carries the merchant/network identity but no product snapshot (see Merchant outclicks).
Requires a token with API product access.
Endpoint
Key behavior
- Each query is limited to a 24-hour window and excludes the most recent 5 minutes.
- Returns product and merchant outclicks — pick with
offer_type(defaults toproduct). Promotion outclicks are intentionally excluded. - All filters are exact matches.
- Robot clicks are excluded unless
include_robots=true. - Results are ordered newest first (
created_atdescending). - Prices are returned as floats (e.g.
131.25). - Each request bills one API unit, regardless of how many rows are returned.
Merchant outclicks
Passoffer_type=merchant to return clicks on merchant outclick links — the outclick field of a providers[] entry (e.g. a homepage link to a service merchant such as HelloFresh or Avis), including AdMedia merchant links. A merchant click carries the merchant identity but no product snapshot:
offer_typeismerchant, and the top-levelmerchant(id,object_id,name) andnetwork(id,object_id,name) objects are populated.productisnull— a merchant has no offer/feed row, so there is nothing to snapshot.sub_id,client.*,country, andorigin_query_parametersare populated as usual.
merchant_object_id (nmer_…), network_object_id (rnet_…), or sub_id.
Tag a click with your own reference
Add your own query parameter to an outclick link (for example&customer_ref=abc123) to tag a click with your own reference. The parameter is stored with the click and returned in the report’s origin_query_parameters. It is not forwarded to the provider.
affiliate_id, sub_id, format, click_tracking, aff_id, cid and ref_id.
Each report request covers up to 24 hours, so pull the report on a schedule and keep the rows you need. A conversion can arrive well after its click.
Troubleshooting — a click isn’t showing
The most common cause of an empty result right after a test click is the 5-minute window, not missing data.
- Wait 5 minutes.
end_atmust be at least 5 minutes in the past, so a click isn’t queryable until ~5 minutes after it happens. A window whoseend_atis older than the click returns nothing. - Match the account. A click is owned by the account whose API key minted the outclick (baked in at link-build time), not the one that clicks it. Query with that same key — a different account won’t see it.
sub_idis exact, and stored verbatim. If you leave the{AFF_ID}/{SUB_ID}(or@@@/###) placeholders in the link unreplaced, they’re recorded literally (e.g.sub_idbecomes{SUB_ID}), so a tag filter won’t match. Replace the slots with real values before clicking.- Robots are excluded by default. Add
include_robots=trueif you’re testing with a tool or headless browser. - Product-snapshot timing. The click row is written synchronously, but the
productsnapshot is enriched by a background job — so on a product click the row can appear a moment before itsproductblock is fully populated under load. Merchant clicks have no snapshot, so nothing lags.
Headers
Query parameters
Inclusive start of the window. Accepts an RFC 3339 timestamp (e.g.
2026-07-23T00:00:00Z) or a UTC date (2026-07-23). A bare date resolves to midnight UTC. Maximum 64 characters.Exclusive end of the window. Accepts an RFC 3339 timestamp or a UTC date. A bare date resolves to midnight UTC of the next day, so passing the same bare date as
start_at requests the full UTC day. Must be after start_at, no more than 24 hours after start_at, and at least 5 minutes in the past. Maximum 64 characters.product or merchant. Selects which kind of outclick to return. See Merchant outclicks.Exact Affiliate.com merchant object ID. Requires the
nmer_ prefix (e.g. nmer_01khfmtj1vpvy6345xfhwepz9t).Exact Affiliate.com network object ID. Requires the
rnet_ prefix (e.g. rnet_01kkgbyq466tn06cgev3b1dnaa).When
true, includes both robot and non-robot clicks. Defaults to false (non-robot clicks only).Comma-separated string or
fields[] array selecting which fields to return. Between 1 and 50 fields. Omitting it returns all fields. Accepts any leaf field path listed under Response fields, plus the parent paths product, product.urls, product.merchant, product.network, and client (which select the whole sub-object).Example requests
Retrieve one day of outclicks:Response
Response fields
meta object
Event object (data[])
Query parameters captured from the origin URL, including any custom parameters you added (e.g.
affiliate_id, sub_id, customer_ref).Merchant identity (
id, object_id, name). Populated for merchant outclicks; on product clicks the merchant is under product.merchant.Network identity (
id, object_id, name). Populated for merchant outclicks; on product clicks the network is under product.network.