Webhook payload update to decrease API calls
We use Xero Invoice Webhook to create the electronic invoices needed to comply with Argentina tax laws.
We have discovered some updates that could be made to the invoice webhook in order to dramatically decrease the API calls we send to Xero (to get the invoices details).I think this updates will also benefit the implementation of e-invoice in USA, AU and NZ.
The two updates are very simple. Just add to the invoice webhook payload the following data:
1 -invoice type (in order to avoid API call for bills)
2- nvoice status (in order to avoid API calls for draft and awaiting approval invoices)
Gonzalo
shared this idea
-
Amanda clark
commented
This is a really insightful breakdown of optimizing webhook payloads! It’s impressive how small changes can reduce unnecessary API calls and improve efficiency. For those also dealing with legal processes or needing reliable information on Court Records Search, you might find https://sanbernardinocountycourts.org a helpful reference. Applying similar optimization principles to different systems can save both time and resources. Thanks for sharing these practical tips!
-
Paul
commented
Specifically for Invoices, some items like 'status' would help the code responding to the webhook to decide what to do - otherwise for *every* web hook event we need to access Xero to get the invoice - that's a lot of data when all I need is the status.
There may be a case for some other fields to be included.