Appearance
Changelog
All notable changes to the InvoisX API.
Versioning
The API uses semantic versioning. The current version is v1.
2024-12-30
Added
- Invoice-level discounts and fees
invoiceDiscountAmount/invoiceDiscountDescriptioninvoiceFeeAmount/invoiceFeeDescription
- Draft buyer support with
is_draftflag is_readyfield to indicate buyer readiness for LHDN
Changed
- Response format standardization
- All amounts returned as strings with 2 decimal places
- All success responses include
"success": true - Field names use camelCase consistently
2024-12-15
Added
- Self-billed document support
/self-billed-invoices/self-billed-credit-notes/self-billed-debit-notes/self-billed-refund-notes
- On-behalf seller management
/on-behalf-sellersendpoints
- Pre-e-invoicing support with
isPreEinvoicingflag
2024-12-01
Added
- Bulk document submission
POST /documents/submit-bulk
- PDF generation
GET /documents/{id}/pdf
- Direct image response for QR codes
- Accept:
image/pngorimage/jpeg
- Accept:
Changed
- Increased rate limit from 30 to 60 requests per minute
2024-11-15
Added
- Document operations
POST /documents/{id}/validatePOST /documents/{id}/submitGET /documents/{id}/statusGET /documents/{id}/qr
- Auto-calculate mode with
autoCalculate: true
2024-11-01
Added
- Initial API release
- Buyer management
- CRUD operations for
/buyers
- CRUD operations for
- Invoice management
- CRUD operations for
/invoices
- CRUD operations for
- Credit notes, debit notes, refund notes
- Reference data endpoints
/states,/countries/classifications,/unit-types/tax-types,/currencies/payment-modes,/id-types
Migration Notes
Upgrading to Latest
No breaking changes in the current version. All existing integrations should continue to work.
Response Format Changes
The API now consistently returns:
- Amounts as strings:
"1000.00"instead of1000 - Success flag:
"success": trueon all successful responses - CamelCase field names in responses
These changes are backward-compatible. If you're parsing amounts as numbers, the string format will still work with most JSON parsers.
Deprecation Policy
- Deprecated features are announced at least 3 months before removal
- Deprecated endpoints continue to work but may not receive new features
- Breaking changes are only introduced in major version updates (v2, v3, etc.)
API Status
Check API status and incidents: status.invoisx.com
