Data Fields That Taggun Extracts

Taggun turns receipts and invoices into structured JSON. This page is the documented public catalogue of extractable fields: what each field contains, where to find it in the response, which endpoints return it, and whether it is enabled by default.

These fields apply to the six data extraction endpoints:

• Upload File (verbose)
• Upload File (simple)
• Encoded File (verbose)
• Encoded File (simple)
• URL (verbose)
• URL (simple)

Unless explicitly required, response properties and nested data may be omitted. Some documented envelopes and values explicitly allow null; do not assume that every top-level or feature envelope does. Arrays may be omitted or empty unless a page documents a nullable array, and properties within returned items may be absent. Guard the object and usable value before use. Types below describe populated values, not a guarantee that a property is returned for every document.

Core Fields

Product Line Item Fields

Product line items are returned as entities.productLineItems[]. Each entry represents one extracted line item. Repeated products or duplicate-looking lines may appear; entries are not guaranteed unique.

These are line-item fields; the public response schema does not contain a standalone serialNumber field. For the full set of line item fields—including per-item discount and category—and a worked example, see Line Item Extraction.

Detailed Merchant Location Fields

For standardised merchant names and verified locations, see Merchant Intelligence.

Detailed Tax Fields

Payment Fields

How the transaction was paid. General → Payment Type controls the documented payment-method field. Card last-four output remains account-configured; no separate public last4 control is documented.

Payment type is matched against a keyword table rather than free-form extraction, so values come back normalised. When the receipt shows a card network (a Visa or Mastercard sale, for example), the network is the paymentType value — there is no separate card-network field. The card's last four digits are the separate entities.last4.data field. The value list above is representative, not exhaustive.

Fraud Detection Fields

These fields are part of the Fraud Detection Suite (Advanced plan and above).

Extraction and Validation Response Paths

Validation moves these result envelopes to the response root, but their inner shapes are not uniform: tamper values are flattened while digital values remain under digitalDetection.data. See Validating Receipts. Build decisions on the boolean flags and set your own thresholds on the scores — each check's page explains how.

Analysis Fields

Simple named field objects can contain data and confidenceLevel. Verbose responses add raw text, location and index metadata, currency metadata where applicable, scan metadata, and feature envelopes. For how these properties fit together, see Understanding Your Results.

Verbose Helper Arrays

Verbose responses can include helper arrays that expose candidate values found during extraction. Use the named fields above (totalAmount, taxAmount, entities.productLineItems[], and so on) for production decisions; use these arrays when you need to inspect or debug all candidate amounts or numbers returned by the model.

Feature-Specific Response Envelopes

Some account settings add their own objects under entities. These properties remain optional even when a setting is enabled. Depending on the feature-specific schema, a returned envelope may contain confidenceLevel: 0, an empty array, omitted data, or an explicitly nullable value. Check the feature page and the nested usable value before use. Other settings can change processing behaviour without adding a dedicated response object.

Customer and additional receipt properties

These fields are optional and available on verbose endpoints when the corresponding account setting is enabled:

Region-Specific Fields

Taggun extracts additional data fields depending on the receipt's country of origin — tax ID validation, document type classification, country-specific QR formats or workflows, and more. These are documented on the country pages:

• Australia · Brazil · Chile · Colombia · India · Spain

For the full list of supported countries and languages, see Supported Countries & Languages.

📘

Receipt validation returns different fields

The fields on this page apply to the data extraction endpoints. Receipt validation endpoints return validation results instead — see the Campaign Settings Reference and Validating Receipts.

Don't See What You Need?

If a specific data field is not available, we want to hear from you. Contact us at [email protected] to request support for additional fields — see Contacting Support.