URL

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. This page covers the URL operation — POST /api/validation/v1/campaign/receipt-validation/url (application/json). To send the receipt as a file instead, use Upload File.

The URL must resolve to a supported file type; see Document Types & File Requirements for the current requirements.

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

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required
length ≤ 50

The campaign ID to validate against. Maximum 50 characters.

string
required

HTTPS URL of the receipt or invoice, reachable by Taggun. HTTP, localhost, loopback, link-local, and private-network targets are rejected.

headers
object

HTTP headers to forward when fetching a protected HTTPS resource.

string

Optional language hint; leave empty for automatic detection. Recommended for Arabic (ar), Khmer (kh), Thai (th), and Hebrew (he). Full code list: Language detection and hints.

string

A location (city, state, country) to help search for the merchant.

string
length ≤ 100

End user's IP address, used for GeoIP lookup.

boolean
Defaults to false

Per-request storage opt-out. See Security, Privacy & Data Residency.

string
length ≤ 50

End-user identifier associated with the submission and returned with matched receipts, when available, so cross-user reuse can be investigated.

string
length ≤ 100

Attribute usage to a client or other subdivision within your Taggun account for reporting. Maximum 100 characters on receipt-validation requests. This does not create a separate Taggun account or subscription.

string
length ≤ 50

Caller-supplied identifier. See Duplicate & Similarity Detection.

Responses

413

Request body exceeds the 20 MiB (20,971,520-byte) HTTP body limit. See Document Types & File Requirements.

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json