Format
Request and response bodies use the application/json content type and should be encoded in UTF-8.
Date formats
All dates should use the ISO 8601 format. By default, the eezi system will store generated dates (created, modified, etc.) using UTC.
Status and Error Codes
All API call status and error codes are aligned with the HTTP protocol (RFC 2616 specification) status codes.
Rate limiting and Throttling
The API has a sane default set for integration per environment. Rate limiting and throttling enhance security, mitigate DDoS attacks, and ensure a high level of API availability. When the rate-limiting algorithm is triggered, the API returns a 429 Too Many Requests error.
Rounding and Validation
eezi's API supports more than two decimal places for invoice fields, ensuring accurate totals, taxes, and discounts—critical for high-volume transactions and compliance with industry regulations. However, some tax reporting formats may require only two decimal places. Therefore, eezi automatically rounds totals and tax amounts as needed for validation and as required by destination formats.