Checks the submission against the rules stored under campaignId (dates, merchants, products, balance owing, fraud checks, and configured SmartValidate prompts) and returns pass/fail per rule — synchronously, in the response. Define rules first with Create Campaign Settings.

📘

Availability

Available on Advanced plans and above. Enable Campaign Validation in your account Feature Settings when it is available on your plan — see Plans & Feature Access.

Two request variants share this operation's contract. The console below covers the file operation — POST /api/validation/v1/campaign/receipt-validation/file (multipart/form-data). The URL variant — POST /api/validation/v1/campaign/receipt-validation/url (application/json) — takes url (HTTPS URL of the receipt, reachable by Taggun; HTTP, localhost, loopback, link-local, and private-network targets are rejected) and optional headers (HTTP headers to forward when fetching a protected resource) in place of file; all other fields are the same.

Use a supported file type. A request-size limit applies; see Document Types & File Requirements for the current requirements.

See complete example responses. Guides: Validating Receipts · Setting Up Validation Campaigns · SmartValidate.