Be able to import bank statement lines into a bank account in Xero. This would be useful for custom bank accounts or banks that do not have a direct feed into Xero1,426 votes
Looking to put a roadmap together for this financial year. Initially this will enable traditional bank feeds via the API but will be extended to statement upload in future.
Provide an API for the recently released quotes feature in Xero (http://help.xero.com/QuotesMain)1,108 votes
At the moment there are still no plans to add quotes functionality to the API. We appreciate there is strong demand but our focus this year will be on other aspects of the platform that benefit all apps including OAuth2.0, SSO and some huge marketplace improvements.
I know it must seem like we don’t pay attention to UserVoice but we really do value the feedback. In the past year we’ve shipped two of the top three requests (Webhooks and emailing invoices) but unfortunately we just can’t get to everything.
To stay up to date with what we’re actively planning to work on, check out our public roadmap here https://trello.com/b/cHoNWLSe/xero-platform-roadmap-for-developers
Be able to create and manage repeating invoices (http://help.xero.com/#Accounts_RepeatingInvoice) via the API.748 votes
- Update September 2016 -
You can retrieve repeating invoices via the API but we have no current plans to add create or update functionality.
We know this would be a useful feature but the team is currently focused on other big features like webhooks.
We’ll re-evaluate the status of this in the new year.
The current budget summary API report (http://blog.xero.com/developer/api/reports/#BudgetSummary) returns the overall budget summary report. Within Xero, you can create additional budgets which can be filtered by tracking category. This request is to:
- Provide a Budgets API endpoint
- Allow the budget summary report be filtered by budget645 votes
Provide an API to retrieve the transactions of an account. (e.g. something like this Profit & Loss report-> click on the YTD value of an account)
More discussion in the thread <https://community.xero.com/developer/discussion/326819/>401 votes
No updates to add on this at the moment
Currently, we have no idea which user connected via OAuth. In other platforms (QB for once), you get details (especially email) of the user, and can design behavior based on it. In Xero, we get all the data on the users (with the new email address field), but we don't which user connected. If this will be exposed, it will give the developers more tools to create a more specific experience for the users229 votes
Our new OAuth2.0 authorisation will include an OpenID Connect identity layer that will allow apps to retrieve the connecting user’s details.
It’s a big project and still probably a few months away from general release but we’ll update this post with more details as we have them.
Any chance Xero will support oAuth2.0 ?
oAuth1.0 and it's payload signing doesn't work very well in various environments including node.js
With rest of the world moving to oAuth 2.0 - I hope XERO does too199 votes
The team has started working on this. We’ll keep you updated on the progress.
1.void payments via API
2.unallocated/void credit note via API
API should let us void payments and credit notes, at least for the invoices copied from our system184 votes
Back in December 2014 we added functionality to delete payments so this is well overdue for an update.
Unallocating credit notes, prepayments etc is definitely something we’d like to do but not on the roadmap right now
When merging contacts the system seems to treat them as a delete so we can’t differentiate them from a full delete. Ideally they should show a status of merged and the ID of the contact they were merged with that way we could perform the same action in the CRM of merging the contacts history rather than deleting them.177 votes
Ability to create or edit additional 'custom' fields to use for notes, additional phone numbers, job descriptions, etc.168 votes
While there is no immediate plan to provide custom fields on contacts, we are certainly looking at our contact data model in the next 6-12 months so keep the suggestions coming.
Please not that an account number field was added to Xero and the API last year which may be useful to some: http://developer.xero.com/documentation/api/v2-release-notes/#2.73
Add support for batch payments to the API.
- When retrieving payments via the Payments endpoint, include the batch payment ID so you can know which payments were made as part of a batch payment.
- Allow the creation of a batch payments. A single payment that can be assigned to multiple invoices and display as a lump sum in the bank account.168 votes
Work has now started on a new endpoint for batch payments.
We’ll be delivering support for payments (bills) first with batch receipts (sales) to follow.
We’ll keep this post up to date with all the release details.
This functionality is missing from API and available only via front end. We have almost finished implementation of Store Credits via Credit Notes and Overpayments, but luck of this functionality makes entire sync process very cumbersome.140 votes
Be able to update the EU Country field via the API. This is required and seems very strange to be left out of the API.135 votes
This would allow us to build tools to do bulk budget exports for multiple periods from our current system. (I think that budgets import might be coming through the user interface anyway, in which case this isn't really needed).124 votes
This will be something we are considering now that the main application allows budget imports (recently added).
Anyone interested should add their vote – also be good to let us know your intended use in a comment so we can factor this into development.
Once an invoice is approved, it should have the facility to "revert it back to draft"
It is because of the reason that mostly, my client ask me to approve the invoice and then says that it's not yet approved and then i don't have the facility, ultimately it is showing in our accounts that an overdue invoice is available, which is actually not yet approved.
Xero should facilitate us in such a way.
It should be different crietaia to add contacts. It should allow contacts with same name , may be have different personal details. validation should not be on name.107 votes
We’re currently investigating the feasibility of making this change. There are quite a few complications (for the API as well as our other apps) because you won’t be able to use contact name as an identifier anymore but we’ll planning on making the transition as smooth as possible.
E-mailing updates to receivable accounts about their payments via the API would be very useful. Via the web interface, this is possible by sending a statement. API request is to be able to retrieve a statement report and email it via the API102 votes
I have an internal system that handles all the other metrics for our business, but the financial data is missing.
We could either hand-enter the necessary data or build some sort of import functionality, but it would be best to query Xero directly so I can use that data in my internal system.
Thanks for listening!91 votes
You currently need to be a standard user in Xero to grant rights to a 3rd party application. Adding permission options for apps is on our radar
- Don't see your idea?