Work on a new endpoint to send invoices via the API has now begun. We expect to be shipping early in the new year.
Thanks for your feedback and patience everyone.
Our invoicing team are doing a lot of work improving the invoicing feature set. This includes the ability to send invoices via email. Once this feature has been delivered we will make it available through the API. No timeline yet but keen to get this one shipped by the end of the year.
We have recently added support for email templates in Xero ( see http://help.xero.com/#EmailTemplates ). The next stage of work is to let users set a sender address which our team is working on now. Once that is in place we'll look to add support for triggering the sending of invoices via the API. After that we'll consider adding support for other documents.
@Mark: Sorry if I wasn't clear, but we cannot provide functionality that is not in the Xero application already, hence my point on the sender address not being a generic one until that is available within the application.
It is possible to download a PDF version of an invoice right now via the API and email it yourself: see the comment on PDF in our documentation: http://blog.xero.com/developer/api/invoices/
Thanks for the feedback on this so far.
I am doing some work to better understand how you would like this to work.
As you may be aware, emailing an invoice from within Xero sets the "from" address as the current user (person sending the invoice). If sent via the API, this would have to be the person that created or authenticated the API connection.
Secondly, Xero does not have any default message or message templates, so this would need to be set each time. This message body cannot include HTML etc - plaintext only.
Thirdly, the "to" address: at the moment this is automatically populated with the contact email of the invoice contact, but there is also the option to specify other email addresses also. We would not be comfortable allowing any email address to be specified programmatically via the API - would only being able to send to the invoice contact be sufficient.
I would appreciate your thoughts on this and also, any insights into how you would see yourself using this functionality would really improve our understanding of your needs - we have previously assumed that it would be just as easy for you to generate an email yourself after retrieving the invoice details via the API, so I would love to understand your needs better.
65 votesunder review · 4 comments · Xero Accounting API » Developer Tools · Flag idea as inappropriate… · Admin →
We have recently created a dedicated Developer Experience team to upgrade many of the services around the API. This type of functionality is part of a wider Sandbox EPIC that the team will look at later in the year.
We will post updates as and when we have them.
Hi Edward, a good suggestion but it's unlikely that we'll be adding this feature to Xero in the near future.
There's not a huge demand for it in Xero's feature request forum https://community.xero.com/business/discussion/2045046/
For this depth of inventory functionality we will probably always recommend an organisation use an add-on.
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.
We will not be providing a further update until we begin active development, and won't provide an ETA other than to say it will not be something we will be working on in the next 3-4 months.
We opened the beta for the contacts endpoint. You can find the documentation here: https://developer.xero.com/documentation/webhooks/
Invoices webhooks work is underway, we will post an update as soon as we release it to production. Thanks
@Chris - why do you need to retrieve each invoice individually? You should be able to do a GET Invoices call to retrieve multiple invoices at once unless you need the line item detail. In addition, you can use the modified-since parameter to only retrieve the changes: http://developer.xero.com/documentation/getting-started/http-requests-and-responses/#title2
All that aside, 18,000 API queries a month is still well inside the average monthly limit of 30,000 (1,000 per day).
That does not mean we should not keep working to make the API more efficient via web hooks etc, just some pointers to keep you going for now. ^RQ
Today’s release supports PUT/POST BankTransfers in addition to the GET BankTransfer work previously done.
We consider this in beta until we can complete some of the more advanced use cases, but for most, this should what they are after: http://developer.xero.com/documentation/api/v2-release-notes/#2.42
@Mark - this hasn't been left out, we just have not built it yet. We are working on a bunch of other functionality right now, but our goal is to expose as much of the Xero application via the API as we can. Appreciate everyone's feedback and votes - remember a little info on your own specific use cases is always helpful to guide us when we do get into development.
44 votes0 comments · Integration with other products » Point Of Sale · Flag idea as inappropriate… · Admin →
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
This is something we are looking at. As a first step, we may only open this up to certified Add-on partners. It would be great to get your feedback and use cases below.