Field Information
Before you start to build your requests, review the required fields.
This topic lists information about mandatory, deprecated and inactive fields.
Mandatory fields
Mandatory fields can be grouped as:
- Schema Mandatory Fields: Some fields, like
custom_idorrefund_reasonare a required part of the schema. You do not have to include a value but the schema must include these fields. - Fields that are mandatory due to business requirements. For example, some specific fields are required for Canadian invoices.
Schema mandatory fields
The following fields are mandatory for a valid schema. This means the schema does have to include a value for the field but it must include the field:
custom_idfor transaction lines but not transactions.refund_reasoncountry_codecurrency_codeproduct_class
Mandatory fields per request
The following fields are mandatory for a successful Calculate Tax request:
country_codeamountortotal_amountcurrency_codeproduct_class
The following fields are mandatory for a valid Store Transaction request:
buyer_nameamount or total_amountcountry_codecurrency_codeproduct_class
Response-only fields (Service Generated)
The following fields are generated by the service. You should not add values to the these fields in your requests:
| Field | Description |
|---|---|
line_key | Transaction line identifier. |
update_timestamp | Timestamp for updates. |
tax_address_kind | Identifier for the type of address. |
Inactive fields
The following fields are inactive and should not be used:
carrier_iddiscountsvoucherspayment_addressdiscounted_tax_amountproduct_cn_codeproduct_reference_numberparcel_referencediscounted_total_amountdiscounted_amount
The following fields cannot be used with the Calculate Tax request:
invoice_timestampexternal_unique_id
Deprecated fields
The following fields are deprecated. You can use the alternative field instead:
| Deprecated Field | Replaced by |
|---|---|
tax_name | No longer returns valid results. |
Updated 7 months ago
