How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

AppZen Invoices API

The Invoices API from AppZen — 3 operation(s) for invoices.

AppZen Invoices API is one of 19 APIs that AppZen publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Invoices. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 3 operations across 3 paths, and defines 36 schemas. It is described by OpenAPI 3.2.0, at version 2.0.3.

Requests are made against a single base URL, https://.appzen.com/dictionary-data-services.

3 operations 3 paths 36 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.3
Base URL
https://api.appzen.com/dictionary-data-services
Authentication
API Key, API Key, API Key, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 6

AppZen Invoices API declares 6 security schemes for authenticating requests. An API key is passed in the header as x-api-key (API_Key_Header). An API key is passed in the header as customer-id (Customer_Id_Header). An API key is passed in the header as customer-key (Customer_Key_Header). An API key is passed in the header as x-api-key (API Key Header). An API key is passed in the header as customer-id (Customer Id Header). An API key is passed in the header as customer-key (Customer Key Header). By default, every request must be authenticated.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Invoices 3
POST
/invoice
Creates/Updates an invoice
3 params → 200201400401403404500
POST
/invoice/search
Returns all invoices uuid that match the search criteria
1 param → 200400401403404500
GET
/invoice/{uuid}
Returns an invoice's details
1 param → 200400401403404500

Schemas 36

The contract defines 36 schemas that model the data the API accepts and returns. The most detailed are invoice-json-schema (71 properties), invoice-get-json-schema (65 properties), invoice-line (41 properties), payment (21 properties). Each schema is shown below with its type and property counts.

invoice-line-condition
object
Represents a PO condition associated with an invoice line (used for subsequent invoice types like freight, tax, etc.)
6 properties
invoice-goods-receipt
object
3 properties
find-invoice-query-spec
object
7 properties 2 required
invoice-header-custom-json
object
Maximum of 20 fields allowed, 500 chars per field. The following is the list of predefined reserved field names. They are the only field names that can have pr…
exchange-rate
object
Optional. If the exchangerate is provided, then all three fields (fromcurrencycode, tocurrencycode and conversionrate) are required.
3 properties 3 required
http-404-error-response
object
4 properties
payment
object
21 properties
date-time
string
date should be in UTC format
http-401-error-response
object
4 properties
po_policy_match_type
string
custom_json_object
object
Set of key value pairs, where each value is an object with two keys - name and id
invoice_line_type
string
find-invoice-result-spec
object
5 properties
withholding-tax
object
4 properties
address
object
8 properties 1 required
invoice-line
object
41 properties 5 required
invoice-line-allocation
object
Specify an allocation for an invoice line. Either amount/tax or percentage is required.
10 properties 3 required
payment_type
string
abridgedAddresses
array
addressCore
object
14 properties 3 required
http-400-error-response
object
4 properties
invoice-account-segment
object
5 properties 5 required
uuid-updated
object
2 properties
http-403-error-response
object
4 properties
uuid
object
2 properties
discount
object
3 properties
vat-breakdown-item
object
5 properties
invoice-get-json-schema
object
65 properties 7 required
http-500-error-response
object
4 properties
amount
object
2 properties
po_policy
object
3 properties
invoice-line-custom-json
object
Maximum of 20 fields allowed, 500 chars per field. The following is the list of predefined reserved field names. They are the only field names that can have pr…
po_receipt_type
string
invoice-json-schema
object
71 properties 7 required
appzen-vat-breakdown-item
object
2 properties
addresses
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

appzen-invoices-api-openapi.yml Raw ↑

Other APIs AppZen publishes across the network.

AppZen Chart of Accounts API
AppZen Custom Data Sets API
AppZen Documents API
AppZen Entities API
AppZen Externally Processed Invoices API
AppZen Goods Receipt API
AppZen Invoice Audit Results API
AppZen Invoice Status Sync API
AppZen Lookup Item API
AppZen Lookup Table API
AppZen Payment Terms API
AppZen Processed Invoices API
Where this information came from

This is an independent, third-party profile of AppZen Invoices API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.