720 results found
-
Fix broken linq count() processing on anything that is pagged like journals. Count is defined as the nuber of records, and cannot be pagged.
Fix linq count() to match stanadard, not massed up version..
Count cannot be paged, this is very basic..3 votes -
3 votes
-
Create a customer credit limit field and be able to access as a y/n from the API so & I could automatically flag.
I want to be able to freeze or restrict customers accounts in relation to orders or services if they exceed their credit limit on overdue balances.
This is a very clear business need and I hope it could be integrated into your system as I believe it would add significant value to Xero
3 votesAs this forum is for developer API functionality requests and yours relates to something that would need to happen in the main application, I’m afraid we have to decline this suggestion, but don’t take it personally – we would still love to see you add your vote in the Xero Community forum:
-
Fix the Expense Claim dates
The C# wrapper is looking for CreatedDateUTC, UpdatedDateUTC & Date but the API returns just UpdatedDateUTC and even this appears to be wrong in my testing (I get 2008-09-25T11:04:21.707).
I'd like to see ReportingDate and PaymentDueDate.
3 votes -
Include ContactNumber in the response for GET CreditNotes
GET CreditNotes has the InvoiceNumber field but not the ContactNumber field. It would be quite nice to have both.
3 votes -
Populate reference field on payable invoices
Would like the ability to set the reference field on payable invoices. This is available on sales invoices but not on payables
3 votesIf you set the InvoiceNumber when creating payable invoices via the API it will populate the Reference field in the Xero UI.
-
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.
3 votes -
Contacts' creation date exposed in API
Would enable the measurement of new business. e.g. number of new customers since the start of the year and their $ value.
3 votes -
Specify which account to import FreshBooks entries into
The API sync with FreshBooks currently dumps my FreshBooks transactions into my checking account ledger irrespective of where those funds were actually deposited. This is a serious limitation that needs to be fixed promptly. Most businesses--even small ones--have more than one account. For interest maximization, all deposits at our firm, for example, go into a money market. As cash is needed in checking to cover outgoing money, it's transferred.
3 votes -
3 votes
Thanks for the suggestion!
Unfortunately we have no current plans to provide a “Surrender to MYOB” API function! -
email to invoice gateway
not sure if it is possible, but what about an email to invoice gateway.
have an email address invoices@xero.com
i can email any invoices i get to that address and it automatically populates a draft invoice in xero, based on the from address of the senderobviously you would need to have a bit of security, like a cryptic email address to send the invoices too, and it would be difficult to parse all invoices formats, but not impossible.
even if it pulled out the generic details of each invoice, eg invoice no, from, date, total, it would save a…
3 votes -
Fix LineItem ID payload returning single ID instead of two
We have identified an issue where the API response for certain line items is returning only a single LineItemID in scenarios where two distinct IDs are expected (specifically regarding the mapping between a transaction line and its associated tracking category).
This request is to ensure the payload correctly returns both IDs to allow for accurate reconciliation and data mapping in third-party integrations.2 votes -
Add TrackingOptionID to the Journals API Response
Requesting the inclusion of the TrackingOptionID directly within the LineItem object for the Journals (Manual Journals) endpoint. Currently, developers have to perform additional lookups or cross-reference tracking names to get the specific ID associated with a journal line.
Adding the ID directly to the response will streamline integration workflows, reduce API call overhead, and provide a more robust way to map tracking data across different parts of the Xero ecosystem.2 votes -
Tracking categories for Products and services
I have clients with multiple site locations so we have tracking categories set up to report on each sites profit. Each site sells different products and services and at different prices. Currently when raising a sales invoice with multiple line items, the clients have to manually choose which tracking category they would like the sales line to be tagged with.
It would be really useful if we could create products & services that can be allocated with a tracking category so for example 'Site A - Labour' service item created and when selected on a sales invoice then the auto-fill…
2 votes -
Expose Journal Count
Other paged endpoints show the total number of records available but journals doesn't (possibly because it's using "offset" instead of "page")
2 votes -
Endpoint to Update Bill Payment
We would need an endpoint to update the Bill Payment object created. Our use case is to update reference number for the existing bill payment.
2 votes -
Add customer sales defaults and Financial details on contacts api
Add ability to view and update customer finical details
- Credit limits.
- Credit Terms (Invoice due date).
- Outstanding balances (possibly read only).
- Discount.This will allow among other for 3rd part vetting process of customer onboarding to be seamlessly integrated.
2 votes -
in the project API expose the time start in time entries
Either expose the time start in project time entries or expose project reports.
This is extremely important when trying to calculate overtime and also to review timings when doing payroll.
I actually cannot believe it is not already exposed.
2 votes -
Include QuoteID/InvoiceID in either Invoices or Quotes endpoint to allow analysing
Our customers need to be analyse Quotes and Invoices and link both with each other. Unfortunately, while you can create a sales invoice from a quote, there is no linking identifier between the two.
It would be good to include the InvoiceID in the Quotes to know which invoice was create from the quote. If a quote can be invoiced multiple times, it would be good for this to be an Invoices collection.
It would also be good to include the QuoteID in the Invoices endpoint to know this invoice originated from a quote and which.
2 votes -
We need to be able to fetch bulk, paginated History and Notes
We need to be able to fetch bulk, paginated History and Notes via the API. Now it only has the ability to fetch records for single invoice. It will be great if we are performing one time ETL and we are getting the time out 429 status in error and rate limiting issue.
2 votes
- Don't see your idea?