2 results found

1. Allow the number of remaining API calls to be queried

   It would be great to have an endpoint to be able to query the number of remaining callouts for a Xero ORG, or the number used in the last 24h rolling period.

   We have a 5000 call limit per ORG. As an integration partner that deals with many different sizes of businesses (small to large), each business pushes / pulls a different number of invoices, notes, history etc each day.

   We don't want the larger users to hit their rate limits and restrict them from syncing the important information such as invoices.

   If we could query the number of callouts being used or remaining, we can build in-app sync logic to dynamically change the sync timing or data to sync based on the number of callouts remaining.

   Especially now that access to additional endpoints (Quotes etc) have become available, there is more data to transfer but the same amount of API calls and no visibility as to when a customer is approaching their daily limit.

   It would be great to have an endpoint to be able to query the number of remaining callouts for a Xero ORG, or the number used in the last 24h rolling period.

   We have a 5000 call limit per ORG. As an integration partner that deals with many different sizes of businesses (small to large), each business pushes / pulls a different number of invoices, notes, history etc each day.

   We don't want the larger users to hit their rate limits and restrict them from syncing the important information such as invoices.

   If we could query the number of callouts… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminXero Developer Platform (CEO / Founder, Xero Developer Centre) responded

   With our move to OAuth 2.0, we now provide this information in the http headers of each response.

   See the relevant documentation here: https://developer.xero.com/documentation/oauth2/limits

2. Expand Application API History

   The Application API History is very useful. I suggest extending the amount of data held in the Application History and make it searchable.
   https://app.xero.com/Application/History

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   completed  ·  AdminXero Developer Platform (CEO / Founder, Xero Developer Centre) responded

   With OAuth 2.0 we have released a new version of the history page. It can now be filtered by HTTP method, endpoint, org name, response status response time and dates.