177 results found
-
Import invoices in foreign currency not just base currency
At present any invoice either imported or brought in via API can only be in the base currency. This means for any foreign currency invoice the user has to click into every single invoice and change the currency manually and then save. This is to say the lease a tad tedious, especially given it is a multi-currency system.
1 voteThis is well overdue to be closed!
API support for multi currency invoices was completed loooooong ago.
-
Include Financial Year End in the GET Organisation response
Including a companies year end date would have value for people using the reports API
1 voteCleaning up some old requests, just confirming that FinancialYearEndDay and FinancialYearEndMonth are exposed in the GET Organisation API call.
-
Modify already authorised Invoices via the API so they can be quickly reconciled
Our clients don't pay invoices if they are unhappy with one of the LineItems. As we like to be able to reconcile payments quickly all invoices are authorised as soon as they are in Xero. Which means they then can not be modified via the API without running around xero doing all sorts.
1 voteIn our latest update we added support for updating approved invoice via the API (as long as no payments have been made on the invoice)
-
allow bank statement data to be accessed via API
this would allow integration with other processing systems that match via the EFT reference used
1 voteSorry – didn’t see this earlier. We have a BankStatement endpoint http://developer.xero.com/api/reports/#BankStatement
-
void authorized invoices
Be able to void authorized invoices via API
1 voteYou can now use POST Invoices to void invoices, you just need to include the InvoiceNumber and set the Status element to VOIDED. Note you cannot void invoices that have any payments applied against them.
-
Allow journals to be sent to Xero
For my business i cannot book all invoices straight to sales - i must book to prepayment then release prepayments to revenues. I want to be able to send via API the journals to release to sales, based on customer usage.
1 voteSorry – closed the earlier request for this when it was released . You can now enter DRAFT manual journals – see http://blog.xero.com/developer/api/manual-journals/
-
1 vote
-
document api response from POST,PUT and DELETE not only GET.
i.e. on successful Contacts POST returned xml will be: <write>returned xml here</write>
while on failure, depending on the cause, the following errors can be returned:<error> possible error here</error>
And so on for all the methods in Contacts, Invoices etc.
Currently only the GET responses are documented.1 voteThis old issue has been fully addressed, but please feel free to let us know if there are any more documentation issues you spot.
-
1 vote
-
invoice(s) PUT addresses/phones elements should not be mandatory
Xero doesn't require addresses & phone(s) fields when creating a contact, why are they neccessary via the API ? For external systems using Xero as the data source of Customers where they are read only in the external system the schema should be changed so those fields are non-mandatory
1 voteInvoices and all our endpoints will be be more flexible in our next API update – lots of elements will be optional – a developer preview release will be available during the week of 7-11 Sept 09
-
Additional GET /invoices Request Parameters
It would be really handy if the GET /invoices request also accepted the optional parameters contactID and contactNumber to retrieve invoices created for a specific contact. This extends the provious contact id request submitted by phaines.
1 vote -
Compress responses (Gzip)
Responses from the API should be compressed (e.g. gzipped) as XML is very verbose and responds well to being compressed.
This should be a simple setting change within IIS.
I haven't tried my application with the production system so it might already be enabled there, but this would also help in the test system.
As the server will only respond with compressed content if the client request says it supports it, this feature shouldn't break anyone's existing code.
1 voteThis is now the default response
-
Integrate with JavelinCRM
Javelin CRM is a create CRM tool www.javelincrm.co.uk
1 voteSee http://blog.xero.com/2009/04/javelin-crm-integrates-with-xero/ for more info.
-
add journals via the API
Add manual journals via the API - same functionality as the app
1 vote -
be able to filter getAccounts depending on type of request
Would be nice to only show those accounts that are valid for a particular purpose.e.g entering an Accounts Receivable invoice , entering an Accounts Payable invoice rather than listing all accounts. Filtering on a specific type maybe useful as well. e.g. Assets, Liabilities
1 voteThe API V2 GET Accounts endpoint allows the use of where clauses for this type of function.
-
Bulk fetching of invoice payments within a date range
Rather than having to query the API to get payment information for each invoice consider allowing a date range to be specified and return all invoices that have had payments applied
1 voteWe’ve introduced a new API method that allows you to get payments since a timestamp. See our API reference for more details http://blog.xero.com/developer/api/invoices-get/
-
GET Organisation: expose 'line of business' field
expose the 'line of business' field that is set in the organisation settings in Xero, to show the industry that organisation is in.
0 votesThe line of business field is now returned on the GET Organisation API call: http://developer.xero.com/documentation/api/organisation/
- Don't see your idea?