Missing Transactions
Create Missing Transaction
File a missing transaction claim when a conversion isn't tracked. The transaction date must be at least 24 hours old. Claims are only accepted for the current and previous month, with a monthly cutoff (see date restrictions below).
POST/pub_api/v3/missing_transactionswrite:missing_transactions
Request body
campaign_idrequired integer | Campaign the transaction belongs to. |
order_numberrequired string | Merchant order number. Must be unique per campaign. |
transaction_daterequired date (YYYY-MM-DD) | Date of the transaction. Must be at least 24h old. Only current and previous month accepted. For previous month claims: cutoff is the 7th of the current month. |
sale_amountrequired number | Sale amount. Cannot be 0. |
coupon_codeoptional string | Coupon code used. |
additional_infooptional string | Additional details about the order. |
reference_idoptional string | Reference ID (required for certain campaigns). |
sourceoptional string | mobile, desktop, or app. |
Date restrictions
Minimum age | Transaction date must be at least 24 hours old. |
Allowed months | Only transactions from the current month or the previous month are accepted. Older transactions are rejected. |
Monthly cutoff | Previous month claims are only accepted until the 7th of the current month. After the cutoff, only current month transactions can be filed. |
Order number format | Some campaigns enforce a specific order-number format — e.g. Myntra orders must match XXXXXXX-XXXXXXX-XXXXXXX. A format mismatch is returned as a validation error. |
Request
curl -X POST https://developers.cuelinks.com/pub_api/v3/missing_transactions \ -H "Authorization: Token YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "campaign_id": 101, "order_number": "OD123456789", "transaction_date": "2026-04-08", "sale_amount": 1500, "coupon_code": "SAVE10" }'
201 Created201
{ "data": { "id": 789, "order_number": "OD123456789", "campaign_name": "Flipkart", "status": "pending", "sale_amount": "1500" } }