Expenses API Updates

New Features

Attachments Support

• New endpoint: POST /expenses-api/expenses/{id}/attachments - Upload attachments to existing expenses
• Added optional attachments field to:
  • Request: POST /expenses-api/expenses - Include attachments when creating expenses
  • Response: GET /expenses-api/expenses and GET /expenses-api/expenses/{id} - View attachments associated with expenses

Tax Payee Types

• Added optional taxPayeeTypes field to:
  • Request: POST /expenses-api/expenses - Specify tax payee types when creating expenses
  • Response: GET /expenses-api/expenses and GET /expenses-api/expenses/{id} - View tax payee types associated with expenses

Improvements

More Flexible Expense Creation

• The type field in POST /expenses-api/expenses is now optional, providing greater flexibility when creating expenses
• VATPE (VAT on expense), MARF(markup on fees), and JE (manual journal entry) have been added to the chargeCode enum parameter of the /accounting-api/ endpoints:

API Documentation Updates

• Renamed API tag from "Accounting (only available for accounting add-on users)" to "Expenses (only available for accounting add-on users)" for better clarity across all expenses endpoints

Validation Changes ⚠️

New Field Length Restrictions

Added maximum length validations to POST /expenses-api/expenses request properties:

• currency: 3 characters maximum
• name: 255 characters maximum
• description: 255 characters maximum
• taxName: 255 characters maximum
• taxDescription: 255 characters maximum

Important: Please ensure your client applications respect these field length restrictions before upgrading. Requests exceeding these limits will be rejected.