26 results found
-
Improve Error Handling in Batch Requests – Identify Which Records Succeeded or Failed
When creating multiple records in a single API request (e.g., contacts or invoices), if some records succeed and others fail, the response only includes information about the failed records.
There is no indication of which records were successfully processed, making it difficult to reconcile results and handle retries programmatically.
It would be highly beneficial if the API could return a structured response that includes both:
A list of successful records (with IDs)
A list of failed records (with error messages)
This enhancement would significantly improve error handling and make batch operations more reliable and developer-friendly.
1 vote -
An Enterprise Xero Platform for Larger Clients
An Enterprise Xero Platform for larger clients to transfer to instead of having to go to another Accounting Platform. So you can transfer them to this 'level' of Xero and the transactions etc flow with it.
1 vote -
Bugfix for C# SDK - Journal endpoint is missing page
A simple fix maybe - you do not seem to have implemented Page() on the JOURNAL endpoint in C#. The other endpoints all have it - and offset is a little mysterious.
1 vote -
to have an "activity" button or tab, that shows in descending order all the activity you have done on Xero for the day (like a history tab),
Make it 'clickable' so you can go back to transactions that may need editing, or to remember how you handled a credit note etc. This would be great for people not that familiar with Xero.
1 voteThis is a great idea for the Xero product and you should definitely raise your idea here https://community.xero.com/business/topic/23/
Declining this particular post because this forum is specific to Xero’s developer API
-
Add User element to Invoices API to allow Suppliers to approve system generated invoices
I'd like to generate draft invoices for my subcontractors via xero, and let them review and submit the invoice.
1 voteUnclear what this request is for.
-
Timeline Put Api BAD Request message should be more descriptive
Put TimeLines API gives BAD Request message does not have sufficient information
https://api.xero.com/payroll.xro/2.0/timesheets/{TimesheetID}/lines/{TimesheetLineID}
{
"date": "2017-03-06T00:00:00",
"earningsRateID": "1e5304e6-40c8-4dd8-9bfb-87b70de7a705",
"numberOfUnits": 17
}these values were inserted in correct format based on the data I have but still getting the 400 BadRequest Error!
If anyone knows a work around it please help!
0 votes
- Don't see your idea?