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
-
Michael Carter
commented
I agree that API access shouldn't be limited only by the current billing setup, especially when users need automation for reporting and workflow management. Expanding eligibility could improve adoption and make integrations more practical for a wider audience. I recently came across https://mahoningcountycourt.org which is a good example of how accessible data resources can benefit users when information is easier to retrieve and manage. Hopefully a more flexible approach can be considered in future updates.
-
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.