Accounting API
Welcome to our official feedback forum for the Xero Developer API.
The Xero Community site is the best place to submit feedback for improving Xero Business
525 results found
-
7 votes
-
4 votes
-
<CurrencyCode> in invoices endpoint is ignoring lower case currency code
When I send "<CurrencyCode>usd</CurrencyCode>" to a CAD base ledger (with USD as a valid currency) the invoice currency becomes CAD. But if I change it to "<CurrencyCode>USD</CurrencyCode>" then it works fine. (data is coming from Stripe, which uses lower case).
Xero should always capitalize the currency code.
1 vote -
deposit
Create Batch Deposits -
https://help.xero.com/au/BatchDepositCreate
Does the API support this specific function? Is there a functional issue as to why this is not supported, or just never requested/not enough votes??
Apologies if it is supported - I could not find it anywhere on developer pages etc.
THANKS9 votes -
Supply <Attachments> elements in standard endpoints when `page` is given
Currently, it seems that you need to make a separate call to get <Attachments>. Being able to get this supplied on the standard invoices/bank transactions/manual journals/credit notes endpoints when
page
is given would help lower the number of API calls without much increasing the amount of data sent.6 votes -
Website URL in API feed
Please include the Website URL in the API feed. Thanks.
6 votes -
1 vote
-
Delete Payments to AR and AP CreditNote via API
In Version 2.74 on Dec 8, 2014, added new feature delete a payment.
However this feature only allow to delete payments to approved AR and AP invoices, but NOT allow to delete payments to AR and AP CreditNote.1 vote -
allow ItemID to be specified when adding line items
It seems to be possible to supply the ItemCode but not the ItemID. I guess the ID is unique for each item? It would be really great in my opinion if the API could be consistent and the ID field was always used to specify a join whenever you are creating or updating anything.
Consider the following use case:
A web app with integrations to xero to do all of the invoicing, and inventory price management. Contacts (users), orders (invoices) and products (items) are stored in the app, but also created in xero. The app then stores the xero id…
17 votes -
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 -
Make Receipt updatable via API
The documentation says:
PUT Receipts
The PUT method is similar to the POST Invoices method, however you can only create new receipts with this method.It would be great if I was able to update receipts with the PUT method.
17 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
114 votes -
Generate reports by using specific identifiers in the "reference field"
As a building business it would be nice to ascertain the costs of a specific build/client to ensure the company is on track with profit/loss per project.
When I started out in Xero, and when all purchases were been entered in as drafts, when a certain reference was entered, such as the client name or job number, a running total was always displayed as to how much was spent on a particular build/client.
Ironically once the purchases were approved and/or paid, upon typing the same specific reference, would no longer provide a tally or what was spent, to be paid…
3 votes -
59 votes
-
Add a report - AgedPayables List - Balance @ Date . Same for AgedReceivables.
To validate back against the balance sheet.
68 votes -
use consistent response structures
The addition of reporting a contact's balances was a great addition, however I feel the response structure should be consistent, regardless of balances. Where any balances are $0, this should be reported as $0, instead of being removed. By removing the key, we are left only being able to test for the absence of data, which creates an assumptive logic.
I understand that removing keys for null values might be part of your api design (ie no email address entered doesn't return an empty <EmailAddress>, but technically, a customer always has a balance so there for the Balances data should…
21 votes -
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.
5 votes -
Provide API to retrieve Customer Invoice Reports
We'd like the ability to retrieve customer reports (as data and in PDF format). We could attempt to re-assemble the reports ourselves but for consistency we'd like to be able to retrieve them directly from Xero.
10 votes -
195 votes
-
Improve the format of responses for Report endpoints
See http://answers.xero.com/developer/question/47411/ for more detail
28 votes
- Don't see your idea?