Encoded File (verbose)

Send a base64-encoded receipt or invoice in a JSON body and return Taggun's broader verbose extraction response — product line items, helper arrays, detailed merchant data, per-field metadata, and enabled feature envelopes when applicable. Useful where multipart uploads are awkward (queue pipelines, some serverless platforms). Only need totals? Use Encoded File (simple).

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

See a complete example verbose response, then use Understanding Your Results and Data Fields That Taggun Extracts to interpret it. Authentication and common parameters are defined once in the Taggun API Reference.

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

The base64-encoded file content. The field is named image for legacy reasons but accepts any supported file type, including PDF.

string
required

The file name.

string
required

The file content type. For example: image/jpeg.

boolean
Defaults to true

Set to false to skip product line-item extraction. See Line Item Extraction.

boolean
Defaults to false

Set to true to return the time when found on the receipt. Otherwise, time is set to 12:00:00.000.

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. When context is available, a verbose response can include a root location object for this IP; it is separate from the extracted merchant address.

string

Specify a merchant name to ignore if it is detected on the file, such as a customer name mistaken for the merchant.

boolean
Defaults to false

Set to true to force reprocessing if the receipt is already stored.

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 ≤ 50

Scopes duplicate and similarity checks to scans with the same caller-defined value. Omit to compare account-wide.

string
length ≤ 50

Attribute usage to a client or other subdivision within your Taggun account for reporting. 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 — multipart framing and base64 expansion count toward the measured body. 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