destinationUrl.
This endpoint must be called from your server. Your API key must never appear in client-side or user-facing code. Forward click events through your backend to keep your credentials secure.
Endpoint
application/json
Request example
Body parameters
The unique ID of the campaign that was clicked. Use the
id field returned by the Fetch Campaigns endpoint.The placement ID where the campaign was rendered when the user clicked (e.g.,
header_banner, article_inline). This must match the placement used when fetching and displaying the campaign.The ISO 3166-1 alpha-2 country code of the user’s geographic location (e.g.,
US, GB, FR). Including this improves reporting accuracy for advertisers.The device type of the user who clicked the campaign. Accepted values:
mobile, desktop, tablet.Response
200 — Success
400 — Bad Request
Returned when a required field is missing from the request body.401 — Unauthorized
Returned when theAuthorization header is missing or the API key is invalid.