177 results found
-
68 votes
-
Inventory items: additional fields
There are a number of fields supported by inventory items within Xero, not yet exposed via the API:
- Name
- PurchaseDescription
- Quantity on hand
- Whether or not it should be 'tracked'
(+ a bunch of others)This request is to track reading and creating / updating these fields via the API
65 votesHi everyone,
Good news! Tracked inventory is now fully supported via the API.
Check out our community post and developer.xero.com for more details.
https://community.xero.com/developer/discussion/12341649/
Thanks for your patience.
Adam
-
Support for Batch Payments
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.
64 votesHi everyone,
Batch payment functionality is now available via the accounting API.
Check out the docs here https://developer.xero.com/documentation/api/batch-payments
Cheers,
Adam -
64 votes
-
Allow attachments of PDF on payable invoices
Store supplier invoices with the invoice transaction in xero. Doubles as a storage system and makes retrieval much easier. Worth paying the upper price plan for
61 votesWe have released the ability to attach files to AP invoices today: http://blog.xero.com/developer/v2-release-notes/
There have been some comments about adding attachments to other documents in Xero. For now, only receipts and AP invoices are supported as in the main application, but any changes to this in the main application, we will work to reflect in the API.
Any questions about using the attachment functionality, feel free to ask a question in our forum: https://community.xero.com/developer/
Thanks
Ronan
-
General Journal Improvements
1) include transaction source and id to be able to link back to the source document of the journal eg AP/AR invoice etc 2) allow endpoint to be filtered by accounting date to be able to get just a certain period.
58 votesWe are pleased to confirm that the Journals endpoint now returns the SourceType and SourceID. This allows you to link journals back to their source transaction.
http://developer.xero.com/documentation/api/v2-release-notes/#2.83
Unfortunately it is not possible to filter the journals endpoint by accounting date. We’ll look to address this with an improved journals reporting endpoint in future.
-
PUT/POST tracking categories and options
Be able to create tracking options via the API. Also when creating invoices via the API allow the creation of tracking options within Xero's existing tracking groups if they don't exist.
58 votesThe ability to delete tracking categories and tracking category options was released today: http://developer.xero.com/documentation/api/v2-release-notes/#2.98
This means the API now supports the full range of tracking category functionality.
If you have any questions about using this feature, please feel free to ask in our community: https://community.xero.com/developer/
-
A fully featured JSON API, with no XML requirements whatsoever.
Title says it all, pure JSON, nothing else. All the same features as the XML one, but at a different endpoint.
57 votesHi everyone,
I’m pleased to announce that we now fully support JSON for the accounting API.
https://devblog.xero.com/json-for-the-accounting-api-974a3b8adfb4
You can now use application/json as your content type and send through your PUTs and POSTs with JSON.
Cheers,
Adam -
Fixed assets API
Provide an API for the fixed assets module.
54 votesWe’re pleased to announce that the Assets API has now been released: https://devblog.xero.com/assets-api-making-your-fixed-assets-restful-98f9eb42e2c5
Please give it a try and let us know if you have any feedback. This is only the beginning for the Assets API so please add new user voice requests if there are any specific features you’re still after,
The docs can be found here: https://developer.xero.com/documentation/assets-api/overview/
Cheers,
Adam -
be able to get approved invoices in PDF format via the API
Be able to query Xero with an invoice number and get a PDF returned of the approved invoice
52 votesYou can now retrieve any invoices and credit notes in PDF format (all statuses) – see http://blog.xero.com/developer/api-overview/http-get/
-
Credit Notes: apply as invoice payment & refund
At the moment, you can create a credit note via the API but you cannot:
- Apply the credit note as a payment to an invoice
- Apply a payment to the credit note (thus refunding the customer)50 votesXero API v2.28 has introduced support for credit note refunds via the Payments endpoint.
See http://developer.xero.com/documentation/api/v2-release-notes/ for examples
Applying credit notes to invoices was completed in a previous release.
-
Create & update credit card type accounts
At the moment it is not possible to create or update an account in the chart of accounts that is of 'credit card' type - this request is to track progress on this feature.
48 votesWe have released an update that allows credit card accounts to be created and updated via the API, as well as bank accounts.
Learn more here: https://developer.xero.com/documentation/api/accounting/accounts
-
Single Sign on provider
Allow users to sign into 3rd party applications using Xero as a single sign on provider (probably through OpenID).
43 votesYou can now use Xero as an SSO provider using OAuth 2.0 and OpenId Connect.
Check out the docs here: https://developer.xero.com/documentation/oauth2/sign-in
-
Add read-only access to accounting numbers for use in other systems
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!
43 votesIt is now possible to request read-only access for your app using scopes in OAuth 2.0 https://developer.xero.com/documentation/oauth2/scopes
-
40 votes
It is now possible to add notes to many of our accounting resources including contacts.
https://developer.xero.com/documentation/api/history-and-notes#PUT
-
Allow adding Contacts to Contact Groups
When you GET a Contact via the API you are returned the ContactGroups that they belong to. But if you try and update their ContactGroups with a PUT or POST the API will just ignore the ContactGroups XML element.
It would be really useful for automating the organisation of Contacts, if you allowed us to update the ContactGroups for a Contact in a similar way that you can add LineItems to an Invoice.
38 votesWe are glad to announce the release of the ContactGroups endpoint which allows this functionality: https://community.xero.com/developer/discussion/6512619/
-
allow fine grained permissions
I'd like to be able to generate multiple API keys for myself, but be able to control the permissions for each of these keys.
For example:
I do some subcontracting to a company and do timesheets for them each month. I then invoice them each month with those timesheet numbers as each line item on the invoice. I'm currently modifying their timesheeting system (which I wrote anyway) so that it'll generate the invoice for me in Xero, it would be nice to be able to PUT an invoice but not allow anyone else in the company to do any GETs…33 votesYou can now set more fine grained permissions for your app using scopes in OAuth 2.0
-
Idempotent requests
At the moment, its rather difficult to recover from a network interruption that happens when you send the request to Xero API, and you loose the connection before you receive the response from Xero. There is a fair number of reasons why this could happen at any time.
In such a situation you really have no way of knowing if your request was even sent fully, or if it was received by Xero, nor what was Xero's response.This is not specific to Xero, as all APIs out there have this same problem, as its simply how the web works.
…
32 votesFind out more in our Idempotent Requests guide: https://developer.xero.com/documentation/guides/how-to-guides/idempotency
-
31 votes
You can now enter DRAFT manual journals – see http://blog.xero.com/developer/api/manual-journals/
-
Payment Terms: expose organisation and contact default due dates
Expose the organisation and contact default due dates on GET Organisation and GET Contact respectively. Xero now supports setting default due dates on an organisation wide or per contact basis.
29 votesYou can now retrieve the default payment terms for an organisation and also for a specific contact. See http://developer.xero.com/documentation/api/organisation/ and http://developer.xero.com/documentation/api/contacts/
Support for updating these via the API will come in a later release – please vote on this other request – http://xero.uservoice.com/forums/5528-xero-api/suggestions/4376082-set-payment-terms-via-the-api
- Don't see your idea?