AppZen · Authentication Profile

Appzen Authentication

Authentication

AppZen secures its APIs with apiKey across 3 declared security schemes, as derived from its OpenAPI definitions.

CompanyFinanceAccounts PayableExpense ManagementInvoice ProcessingSpend AuditArtificial IntelligenceERP Integration
Methods: apiKey Schemes: 3 OAuth flows: API key in: header

Security Schemes

API Key Header apiKey
· in: header (x-api-key)
Customer Id Header apiKey
· in: header (customer-id)
Customer Key Header apiKey
· in: header (customer-key)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/appzen-autonomous-ap-openapi-original.yml
docs: https://support.appzen.com/hc/en-us/articles/12905088759571-Authentication-Overview
guidelines: https://api-docs.appzen.com/api_guidelines.html
summary:
  types:
  - apiKey
  api_key_in:
  - header
  notes: >-
    AppZen's Autonomous AP public APIs use API-key header authentication. Three
    values, all issued by the AppZen Support team, must be sent on every request:
    x-api-key, customer-id, and customer-key. The docs describe the model as
    "API key-based authentication (OAuth1.0)". Every response returns an
    x-correlation-id header to be quoted to AppZen support when troubleshooting.
schemes:
- name: API Key Header
  type: apiKey
  in: header
  parameter: x-api-key
  description: API key issued by AppZen Support.
  sources:
  - openapi/appzen-autonomous-ap-openapi-original.yml
- name: Customer Id Header
  type: apiKey
  in: header
  parameter: customer-id
  description: Customer identifier issued by AppZen Support.
  sources:
  - openapi/appzen-autonomous-ap-openapi-original.yml
- name: Customer Key Header
  type: apiKey
  in: header
  parameter: customer-key
  description: Customer key issued by AppZen Support.
  sources:
  - openapi/appzen-autonomous-ap-openapi-original.yml
response_headers:
- name: x-correlation-id
  description: Present on every response (success and failure); provide to AppZen Support for troubleshooting.