Skip to main content

Overview

Domestic general bills use the document extraction API.
The API returns extracted fields and classification results based on the preset application configuration. To include invoice verification in the current extraction, pass enable_invoice_verify: true. If omitted, the saved application setting is used. For large files or longer-running extractions, create an asynchronous task first and use its task_id to query the result:
To verify an invoice directly from its invoice details, call the standalone invoice verification API:
The API supports 11 invoice types. fpNumber and fpDate are common required fields, while other fields are conditionally required by type_key. Existing three-field requests can continue to omit type_key; they are handled as vat_electronic_invoice_new and must include fpAmount. Use YYYY-MM-DD for the date. HTTP 200 with code=success means that the API completed processing. Read data.result.fpVerification to determine whether the invoice passed verification. See the standalone endpoint page for the required-field matrix, request examples, and response schema.

Request parameters

Example

This example extracts a file from a URL and enables invoice verification for this request:

Supported bill types

Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields
Table fields

Response

The response uses the common document extraction structure.
The field list is long and may change with preset application updates. Actual returned fields depend on the configuration for the app_id.