12 results found
-
be able to retrieve account transactions via the api.
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/
1,243 votesCurrently, we’ve no plans to work on this feature but please continue to add your votes and comments.
We’re continually adjusting our priorities as different features are completed and your feedback is really important.
-
Customer Credit Limits available via API
Xero has finally released a "Credit Limit" facility for Customer accounts. Please can you make this available through the API?.
323 votesThanks heaps for taking the time to suggest this! We’ve shared your idea with the relevant team at Xero. While we might not be able to action every idea, your feedback plays a big part in shaping where we focus and how we can improve your developer experience.
-
add custom fields to contacts
Ability to create or edit additional 'custom' fields to use for notes, additional phone numbers, job descriptions, etc.
232 votesCurrently, we’ve no plans to work on this feature but please continue to add your votes and comments.
We’re continually adjusting our priorities as different features are completed and your feedback is really important.
-
195 votes
-
Create more granular accounting scopes (eg: Sales - Invoice only)
Right now there is a very wide range of APIs wrapped up in the "accounting.transactions" scope, with no way to provide more granular access within these APIs (https://developer.xero.com/documentation/guides/oauth2/scopes#organisation-scopes).
This means that it's not possible to grant access to something quite narrow without also granting access to other things that are often not needed. For example, you cannot grant permission to creating/manipulating Sales Invoices without also giving access to all Bank Transactions at the same time.
This problem is perhaps accentuated for Custom Connections, which are designed to be used for "in house" integrations, as ALL developers with access…
165 votesFollowing up on this - we've shared the idea with the relevant team, and while we recognise that more granualr scopes could be beneficial for a number of reasons this has wide reaching impacts and unfortunately it's not something we're planning to move forward with right now. We truly appreciate your input, so we'll keep this idea open so others can still vote or add their thoughts, and if priorities shift down the track we may revisit the idea. Thanks again!
-
Enter budgets via the API. Both historical and current.
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).
156 votes -
EU Country field
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.
138 votes -
Approved Invoices:: Should have the facility to "Revert it back to draft"
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.
Thanks
Hassan133 votes -
Be able to retrieve & e-mail statements to receivable accounts via the API
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 API
117 votes -
64 votes
-
Increase rate limit (or allow details to be included in invoices, etc)
This is especially important for an initial sync of a new customer with our product as we need every invoice in the database (including the PDFs, which we are happy to trickle into the system over time).
40 votes -
Contact search should be case insensitive via API
While creating the sales invoice via API, usually we check if the contact is already created or not, to search the contact the name/keyword must be used in the same case that is available on Xero, if its different then it will not search.
1 voteHi Swapnil,
Thanks for the post.
We currently have a work around for the issue you are currently facing which may be of use.
It is possible to include ToLower() in the where clause when quering the endpoint. ie. ?Name.ToLower()=="{name}’
See the following commultiy thread for more information: https://stackoverflow.com/questions/60265042/can-xero-contacts-be-filtered-by-name-case-insensitive
- Don't see your idea?