curl --request POST \
  --url https://adp-global.laiye.com/open/agentic_doc_processor/{tenant_name}/v1/app/invoice/verify \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "fpNumber": "23322000000000000000",
  "fpDate": "2026-08-25",
  "fpAmount": "106.00"
}
'

{
  "code": "success",
  "message": "",
  "tips": null,
  "data": {
    "result": {
      "type_key": "vat_electronic_invoice_new",
      "instance_id": "customer-order-001",
      "invoice_pdf_page_number": 1,
      "fpVerification": "查验成功发票一致",
      "fpVerificationMsg": "",
      "fpIsVoided": "未作废",
      "fpType": "电子发票普通发票",
      "fpCode": null,
      "fpNumber": "23322000000000000000",
      "fpDate": "2026-08-25",
      "fpAmount": "106.00",
      "fpNoTaxAmount": "100.00",
      "fpTotalTaxAmount": "6.00",
      "fpSellerName": "示例销售方有限公司",
      "fpSellerID": "91310000XXXXXXXXXX",
      "fpPayerName": "示例购买方有限公司",
      "fpPayerID": "91320000XXXXXXXXXX",
      "fpRemarks": "",
      "fpItems": [
        {
          "itemName": "技术服务",
          "itemModel": null,
          "itemUnit": "次",
          "itemQuantity": "1",
          "itemUnitPrice": "100.00",
          "itemAmount": "100.00",
          "itemTaxRate": "6%",
          "itemTaxAmount": "6.00"
        }
      ]
    },
    "metadata": {
      "trace_id": "94fe9b74e0e311f091505e345594c618",
      "attempt_verify_page_count": 1,
      "actual_consume_page_count": 1,
      "billable_pages": [
        1
      ]
    }
  }
}

Domestic general bills

Verify a domestic invoice

Verify one domestic invoice from its invoice type and the required verification fields.

Compatibility rules

The request body remains flat; do not use a batch array or a nested verify_params object.
type_key is optional. If omitted, the request is handled as vat_electronic_invoice_new.
fpNumber and fpDate are common to every invoice type. Other fields are conditionally required by type_key.
Send codes, numbers, dates, amounts, and check codes as JSON strings to preserve leading zeros and numeric precision.
Do not infer an invoice type from its field combination. Pass type_key for every non-default invoice type.

Required fields by invoice type

type_key	Invoice type	Required fields
`vat_special_invoice`	VAT special invoice	`fpCode`, `fpNumber`, `fpDate`, `fpNoTaxAmount`
`vat_electronic_special_invoice`	VAT electronic special invoice	`fpCode`, `fpNumber`, `fpDate`, `fpNoTaxAmount`
`vat_common_invoice`	VAT common invoice	`fpCode`, `fpNumber`, `fpDate`, `fpCRC`
`vat_electronic_invoice`	VAT electronic common invoice	`fpCode`, `fpNumber`, `fpDate`, `fpCRC`
`vat_roll_invoice`	VAT roll invoice	`fpCode`, `fpNumber`, `fpDate`, `fpCRC`
`vat_electronic_special_invoice_new`	Fully digitalized electronic special invoice	`fpNumber`, `fpDate`, `fpAmount`
`vat_electronic_invoice_new`	Fully digitalized electronic common invoice	`fpNumber`, `fpDate`, `fpAmount`
`motor_vehicle_sale_invoice`	Motor vehicle sales invoice	`fpCode`, `fpNumber`, `fpDate`, `fpNoTaxAmount`
`used_car_purchase_invoice`	Used-car sales invoice	`fpCode`, `fpNumber`, `fpDate`, `fpAmount`
`electronic_air_transport`	Electronic air transport itinerary invoice	`fpNumber`, `fpDate`, `fpAmount`
`electronic_train_ticket`	Electronic railway ticket invoice	`fpNumber`, `fpDate`, `fpAmount`

Interpreting the result

HTTP 200 with code=success means that the API processed the request. It does not mean that the invoice passed verification. Read data.result.fpVerification for the verification conclusion. Missing conditional fields and downstream verification failures can still return HTTP 200, with details in fpVerification and fpVerificationMsg.

Billing metadata

attempt_verify_page_count is the number of invoices with complete fields submitted to the verification service. For this single-invoice API, it is 0 or 1. actual_consume_page_count is the number of invoices that reached a billable state and is also 0 or 1. A feature package can still cover the actual credit consumption.

POST

open

agentic_doc_processor

{tenant_name}

app

invoice

verify

curl --request POST \
  --url https://adp-global.laiye.com/open/agentic_doc_processor/{tenant_name}/v1/app/invoice/verify \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <api-key>' \
  --data '
{
  "fpNumber": "23322000000000000000",
  "fpDate": "2026-08-25",
  "fpAmount": "106.00"
}
'

{
  "code": "success",
  "message": "",
  "tips": null,
  "data": {
    "result": {
      "type_key": "vat_electronic_invoice_new",
      "instance_id": "customer-order-001",
      "invoice_pdf_page_number": 1,
      "fpVerification": "查验成功发票一致",
      "fpVerificationMsg": "",
      "fpIsVoided": "未作废",
      "fpType": "电子发票普通发票",
      "fpCode": null,
      "fpNumber": "23322000000000000000",
      "fpDate": "2026-08-25",
      "fpAmount": "106.00",
      "fpNoTaxAmount": "100.00",
      "fpTotalTaxAmount": "6.00",
      "fpSellerName": "示例销售方有限公司",
      "fpSellerID": "91310000XXXXXXXXXX",
      "fpPayerName": "示例购买方有限公司",
      "fpPayerID": "91320000XXXXXXXXXX",
      "fpRemarks": "",
      "fpItems": [
        {
          "itemName": "技术服务",
          "itemModel": null,
          "itemUnit": "次",
          "itemQuantity": "1",
          "itemUnitPrice": "100.00",
          "itemAmount": "100.00",
          "itemTaxRate": "6%",
          "itemTaxAmount": "6.00"
        }
      ]
    },
    "metadata": {
      "trace_id": "94fe9b74e0e311f091505e345594c618",
      "attempt_verify_page_count": 1,
      "actual_consume_page_count": 1,
      "billable_pages": [
        1
      ]
    }
  }
}

Authorizations

X-API-Key

string

header

required

ADP API Key.

Path Parameters

tenant_name

string

required

Tenant name. This path parameter must be provided explicitly.

Body

application/json

Fields for verifying one invoice. Examples show request structure only; replace them with values from the invoice.

Compatibility mode: omit type_key
VAT special invoice
VAT electronic special invoice
VAT common invoice
VAT electronic common invoice
VAT roll invoice
Fully digitalized electronic special invoice
Fully digitalized electronic common invoice
Motor vehicle sales invoice
Used-car sales invoice
Electronic air transport itinerary invoice
Electronic railway ticket invoice

Select a request model by invoice type. After choosing type_key, the API reference shows only the verification fields for that type. Existing callers can use compatibility mode and omit type_key.

fpNumber

string

required

Invoice number. Send it as a string.

fpDate

string<date>

required

Invoice date, issue date, or travel date in YYYY-MM-DD format.

fpAmount

string

required

Tax-inclusive total, total amount, or fare, without a currency symbol or thousands separator.

Response

The request result. code=success means processing completed; use data.result.fpVerification for the invoice verification conclusion.

API response envelope.

code

required

API processing code. It is success after entering the verification flow; success does not mean that the invoice passed verification.

message

string

required

API-level message.

tips

string | null

required

Optional information.

data

object | null

Verification data when the request enters the business flow. It can be null or omitted for framework-level business errors.

Show child attributes

Product docs

Other docs

Verify a domestic invoice

Authorizations

Path Parameters

Body

Response