Configure OdataLink to poll for changes: Difference between revisions
Created page with "= Overview = Polling allows OdataLink to quickly check for changes. If no changes were made since the data was last retrieved, OdataLink will source the data from the archive..." |
No edit summary |
||
| Line 34: | Line 34: | ||
The formal recommendation is to use '''NEVER force a full refresh regardless of how old the archive data is.''' unless you experience issues with polling for changes. | The formal recommendation is to use '''NEVER force a full refresh regardless of how old the archive data is.''' unless you experience issues with polling for changes. | ||
= Which endpoints currently support polling = | |||
Polling for changes was primarily built to increase performance and reduce the costs Xero decided to charge for their API in December 2025. As such, we prioritised the following endpoints: | |||
* [[Xero Accounting Endpoint: Contacts]] | |||
* [[Xero Accounting Endpoint: ContactsExpanded]] | |||
* [[Xero Accounting Endpoint: ContactsExpandedTable]] | |||
* [[Xero Accounting Endpoint: Invoices]] | |||
* [[Xero Accounting Endpoint: InvoicesExpanded]] | |||
* [[Xero Accounting Endpoint: InvoicesExpandedTable]] | |||
The plan is to have all endpoints support polling in some form or another but prioritising the ones used most. | |||