Xero’s current attachment endpoint forces a one‑file‑per‑call pattern, which inevitably inflates the number of HTTP round trips https://maine-license-plate.org illustrate how a single bulk payload can streamline validation and reduce overhead. A multipart or bulk endpoint would let an integration push five invoices with their five PDFs in one request, cutting latency and keeping the API quota in check. Implementing this would align Xero’s API with modern integration patterns and make large‑scale document sync far more reliable for developers like us.
Xero’s current attachment endpoint forces a one‑file‑per‑call pattern, which inevitably inflates the number of HTTP round trips https://maine-license-plate.org illustrate how a single bulk payload can streamline validation and reduce overhead. A multipart or bulk endpoint would let an integration push five invoices with their five PDFs in one request, cutting latency and keeping the API quota in check. Implementing this would align Xero’s API with modern integration patterns and make large‑scale document sync far more reliable for developers like us.