746 results found
-
Align the decimals for invoices & bills (7 digits) with payments (6 digits)
Through Xero API, invoices and bills can be created or updated with up to 7 decimal places while payment transactions can only be created or updated with up to 6 decimal places, it would be great that payments transactions could also be created/updated with 7 decimals
1 vote -
API support for deleting Prepayments and Overpayments
API support to delete/void prepayments and overpayments will add benefit to keep our system in sync with Xero without the need for manual intervention.
1 vote -
Need client code extra field in organization API call
I am reaching out for assistance regarding a client code-related query. Could you please guide us on where to capture this information from the response? If the client code is not provided in the Xero GET Organisation API response, could you also advise on the appropriate steps to request the Xero team to add this property to our response? Your assistance in providing information on the client code is greatly appreciated.
2 votes -
Support compression in API request / response
It would be great to support compression e.g. gzip for API response payloads. Currently including the Accept-Encoding header within requests does not result in any resource size reduction.
13 votes -
To show 2 active tracking categories on the payroll timesheet
Whilst 2 active tracking categories are shown on Sales invoice, Bills and manual Journal entry.
On the payroll timesheet entry only shows 1 of 2 active tracking categories.
Could we please have 2 active tracking categories appear on the payroll timesheet entry ?
Thanks1 vote -
allow contact website to be set/updated via the api
allow contact website to be set/updated via the api
2 votes -
Allow Prepayment Attachments to be Uploaded via the API
It's currently not possible to add Attachments to a Prepayment via the API.
It'd be nice if we could access this at "https://api.xero.com/api.xro/2.0/Prepayments/{Guid}/Attachments/{Filename}" to bring the functionality in line with the GUI.
We currently have access to: Invoices, Receipts, Credit Notes, Repeating Invoices, Bank Transactions, Bank Transfers, Contacts, Accounts, Manual Journals, Purchase Orders, Quotes (https://developer.xero.com/documentation/api/accounting/attachments).
Seems like the standard and infrastructure is already there, it would be nice to have this one soon, thanks!
2 votes -
Ability to create Practice Manager invoices
It's possible to get details of Practice Manager invoices using the Invoices API endpoints:
https://developer.xero.com/documentation/api/practice-manager-3-1/invoices
However, it's not possible to create or update invoices using the API. It seems to be possible to create and update most other objects using the API so why not invoices?
This functionality would be very useful as invoices are a fundamental part of the system.
1 vote -
Enhance API to include Invoice Created By information
Created by is an important audit field and minimally allows the broader organization to know who to go to for questions...E.g. Think PM getting Invoice questions from customers and then needs to speak with whomever created the invoice to review.
Additionally, this impacts many 3rd party integration tools such as Breadwinner that aim to surface Xero data into other systems. The better enabled integration partners are, the more successful Xero will be in growing with customers and entering larger companies.
Enhancement / Use Case:
Enable API to be able to include the name of the person creating an invoice via…2 votes -
2 votes
-
Provide the OpenDate and ClosedDate in the Projects endpoint
The Projects endpoint of the Xero Projects API does not include the OpenDate and ClosedDate as fields.
These are useful for users to report with and should be included.
2 votes -
Trigger e-Invoice via API
We create invoices in Xero using Custom Connector for a number of customers, depending on customer requirements after creating the invoice we either trigger the email of the invoice (as per https://developer.xero.com/documentation/api/accounting/invoices/#emailing-an-invoice) or bring a copy of the invoice PDF back to the customers other system for sending from there.
Now that e-Invoicing has been introduced in NZ our customers want to start sending invoices as eInvoices but this can't be achieved via the API currently.
12 votes -
provide richer data on your Balance Sheet Report (Report by Outlet/ Location)
The API does not return the location of the asset where it is tagged to currently
1 vote -
Udpate Projects API Endpoint to deliver Contact Name as it does in the internal endpoint.
The Internal Endpoint used on the website delivers more fields than the endpoint in the API.
Internal Endpoint: https://go.xero.com/api/projects/projects?status=INPROGRESSAPI Endpoint: https://api.xero.com/projects.xro/2.0/projects?status=INPROGRESS
While the internal Endpoint delivers the contactName, the external endpoint does only provide the contactId. To fetch the Contact name a user needs to get access to the whole accounting module which is nonsense. The contactName should also be delivered where the id is delivered.
1 vote -
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…
11 votes -
Align front-end and api behaviour to list Customers
Following changes to the front-end of Xero there is now a difference between that and the api when selecting a list of Customers.
Original Behaviour - shown on the API:
All contacts start off as neither customer nor supplier. Once an invoice, bill or credit note is raised the isSupplier or isCustomer field is updated accordingly. The contact retains this status.New front-end behaviour:
We look to see if any invoices or bills have been raised and categorise the contact accordingly.We have a client who has an Accounts Receivable Credit Note posted to it so appears as a Customer…
1 vote -
set "Offer auto pay" via the API
When creating a repeating invoice via the API and setting "Approve for Sending" is it possible to send in a flag to also set "Offer Auto Pay" (stripe in our case) or at least have it turned on in the payment settings section?
see this Stack Overflow post for more details
https://stackoverflow.com/questions/76440037/set-auto-pay-for-online-payments-on-repeating-invoices5 votes -
Support payment of non-base-currency bill from non-base-currency account
Currently you can only create a payment for bill if
- the bill or the bank account is the same as the organisation base currency, or
- the bill and the bank account is the same currency.
Please add support for the case where the bill and bank account have different currencies, neither of which is the organisation base currency.
I get the following validation error through the API when attempting this:
"The invoice, payment and organisation base currencies are all different. Xero cannot currently handle a 3-currency transaction."1 vote -
Posting Bank Transaction attachments should produce helpful error for DELETED transactions
Right now it results in an opaque 500 error, which required me to reach to support.
For example:
```
POST https://api.xero.com/api.xro/2.0/BankTransactions/<transaction>/Attachments/kitten.png
Accept: text/xml
Content-Type: image/png
Authorization: Bearer ...
xero-tenant-id: <..>< /kitten.png
```1 vote -
Update Prepayments and Overpayments via API
We can currently create Prepayment Invoices using the Bank Transaction endpoint (all of this also post applies to Overpayment Invoices too). This returns a list of information about the created bank transactions including Prepayment (or Overpayment) IDs.
The Invoice Number is autogenerated by Xero, and we're only able to change it using the UI.
There are are Prepayment and Overpayment endpoints in the API, but these only allow us to GET one (or multiple) invoices, and PUT allocations for an invoice.
It would be great to see either:
- A POST method on the Prepayment and Overpayment endpoints (this would allow…
3 votes
- Don't see your idea?