577 results found
-
Expose internal unique identifiers in the API when retrieving reports
Because we currently extract accounts through reports, we don't get the internal unique identifier and have to match on number and name. If the user re-names or re-numbers an account in Xero (and this is likely to happen to other entities) we lose the connection to the account stored in our system and the user potentially loses data.
12 votes -
add custom fields to contacts
Ability to create or edit additional 'custom' fields to use for notes, additional phone numbers, job descriptions, etc.
112 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.
-
Validate only option for POST and PUT
Currently when you POST or PUT, Xero will either accept or reject each of the entries. Provide an option to POST or PUT data (Invoices) and have the results returned WITHOUT actually updating any data. That would allow an All or Nothing approach to batch data submission.
3 votes -
allow sales unit prices to be to 3 decimal places - to avoid rounding errors
when a supplier generated sales invoice is received it would be nice to be able to agree to their grant total
1 vote -
PDF's attached to purchase invoices have a URL link so that they can be used by 3rd party apps
PDF Invoices that are attached in Xero have a URL that 3rd party apps can link to
e.g a purchase invoice has an attachment which is thescanned copy of the invoice, we would like a url so we can link the pdf to a web app
1 vote -
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).
66 votes -
Partial payment feature for invoices coming through API
Enable the ability to split payments on a bank rec coming through the API so we can reconcile merchant payments from two separate machines on 1 day. 1 invoice, 2 payments currently unable to split.
2 votes -
Allow rules to apply to invoices coming through the API (especially Vend)- So you can automatically add account codes, analysis codes etc.
Rules to apply to invoices recived through the API - analyisis codes
1 vote -
Improve the format of responses for Report endpoints
See http://answers.xero.com/developer/question/47411/ for more detail
12 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
48 votes -
Add a report - AgedPayables List - Balance @ Date . Same for AgedReceivables.
To validate back against the balance sheet.
27 votes -
31 votes
-
10 votes
-
Allow the full UTF8 character set in Contact Names
Names containing accented characters, eg: Nuñez, are rejected when uploading a new Contact.
12 votes -
1 vote
-
provide transactional support
Allow for batch create/update/delete operations to multiple API endpoints within a single transaction.
5 votes
Public API PM
responded
-
78 votes
-
Send <Payments> together with <Invoice>
We invoice just upon payment, so it would be nice to be able to send <Payments> together with <Invoice>, when creating it, so we don't need to do two separate calls for it.
15 votes -
API to set exchange rates
Create and API entry point to set default exchange rates, just like we do on the Settings page.
Rational: here in Poland, we're obliged to use the Polish Central Bank exchange rates on accounting. Having an API for it makes it possible for us the call it once everyday to set the rate for the next day. Without this we're not able to use Xero officially for bookkeeping. (we have to setup the rates for this whole calendar year!)
14 votes -
Multiple transaction handling with commit and rollback
I would like to have the ability to use the API to enter multiple transactions with the ability to commit or rollback, as appropriate - like you do with a database.
2 votes
- Don't see your idea?