581 results found
-
Exposing organization's timezone in ISO 8601 format
Currently Xero API exposes the timezone via Organisation endpoint as text eg. <Timezone>NEWZEALANDSTANDARDTIME</Timezone>
11 votes -
integrate batch payment export into a banks payment system
I believe it is possible to export a batch payment file for subsequent import into your internet banking solution. It would create efficiencies to build outward direct bank feeds to set up payments on Bills. Then make it available via the API to set due/ payment dates and create payment batches.
11 votes -
Expose the Online quotes URL via the Xero API
Be able to retrieve the online quotes URL via the Xero API as you already can for invoices (http://help.xero.com/#OnlineInvoices)
10 votes -
Return linked Tenant ID in the auth response
When a user has access to multiple Xero accounts it would be great to know the Tenant ID of the account they linked in the auth response.
10 votes -
be able to enter customers address when you create a quote/invoice.
I'd like to be to able to enter the customers address when I create a quote or invoice. Currently I can only do this once the quote/invoice is created by editing the customers details.
10 votes -
Expose reversal information in Journal endpoint
Problem: if a Journal is reversed, Journal.SourceId may point to an invoice whose LineItems do not correspond to JournalLines.
Proposed Solution: If a Journal is a reversal, expose the number of reversed journal via API, e.g.
<Journal>
<IsReversalOf>originalJournalNumber</IsReversalOf>
...
</Journal>When it is useful: in the simplest scenario, when Invoice's LineItem is edited, the original Journal corresponding to the Invoice is reverted and new one is created. We end up with three Journals: Journal1 and Journal2 cancel each other, Journal3 reflects (the new version of) the invoice. Unfortunately, all three Journals have SourceID pointing to the (now modified) invoice. Consequently,…
10 votes -
Increase the limit of API calls
It would be great if the limit of API calls is increased. That way we can make more requests to Xero and not have the connection destabilise. This affects our customer experience as our customers ask us always
10 votes -
Be able to add new user to Xero via API
To be able to add new user via API and connecting it with Employee, Customer, and Supplier
10 votes -
10 votes
-
be an aggregator for bank transactions in New Zealand
This is a challenge for SaaS financial apps in New Zealand, both for small business and personal finance. Since Xero already integrates with banks, it would be great to be able to procure transactions through you via a standardised API :-)
10 votes -
Create a transition plan for Reports via the API
Xero will be retiring the old reports on July 31. By retiring the old reports, you also retire the only place where subscribers can affect the layout of the Profit and Loss report retrieved via the API. However, to date, you offer no replacement and no transition plan to your subscribers or developers.
We use the Reports endpoint to retrieve data needed for our internal reporting. If not for the API, we'd be pulling and formatting seven reports to compile our monthly reporting. Today, if we add a new account or need to change the layout for the P&L retrieved…
9 votes -
Invoice/Webhook - When posting Invoices, be able to set a flag to stop the Webhook from sending the same data back
With Webhooks enabled, it is pointless to have the webhook send the same data back to us when we are posting the data to Xero.
9 votes -
contact notes
Access to the Notes field in the Contacts endpoint would be nice.
9 votes -
Apply same invoice due date logic like in the UI
When creating invoices via Xero UI, contact and organization default due date rules are applied, which is great!
But when creating invoices via API, due date field is left blank unless it's explicitly set in the API request. All this nice logic of applying contact and organization due date, in that order, is skipped for API created invoices, resulting in a rather inconsistent UX for end users.And to "use" that feature of Xero, each API application would need to reimplement same logic that Xero UI already has.
I think keeping parity between UI and API would be very good…
9 votes -
add line item ids to manual journal lines on GET and POST successful responses
this will make it possible to keep local data linked to manual journal lines up to date and in sync with changes made in xero
9 votes -
TaxNumber type field
Contact entity has a field to store Tax number type (EIN, SSN, ITIN and ATIN). This field is accessible via UI or in exported csv file, but not accessible via API, while "Tax Number" itself can be read using API.
9 votes -
Provide CreatedDateUTC
Provide CreatedDateUTC element so invoices, manual journals etc can be filtered using the new element in similar way like UpdatedDateUTC
9 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…
9 votes -
API report Sales by Item
Provide API to get report Sales By Item. because it will help to analyse sales by Item (Product). Now we can generate the report but I don't see API to get report data as other financial report.
9 votes -
Support the US "auto tax" feature in the API
In US Xero we would like invoices to go into Xero with the "Auto Tax" element switched on - by default they go in as "Manual Tax".
We have looked at the Invoice endpoint on the Accounting API and can't see a way to do this, but did notice a Type for Auto Tax, but this is only available for GET (not POST).
We need to make use of this feature with POST, even if it's only the high level "Auto tax" setting of Manual/Auto (we are happy for the From and To to be populated based on existing data).
…
8 votes
- Don't see your idea?