52 results found
-
Make the BrandingTheme for a contact customizable
Currently the field 'BrandingTheme' is only returned on a GET request. We would like to have this field customizable, so we can change the theme used based on info in our CRM
12 votes -
Fix the Contact creation API to fail when PUT-ing a duplicate contact that has been archived
Currently (Jan 2016, API 2.0) using the API to PUT a new contact fails when its email is in use by an existing contact - as would be expected.
However, if the contact that has the duplicate is archived, the PUT will SUCCEED, returning a new contact ID and everything. However, the new contact will not actually be added. This can be done repeatedly, each time "generating" a new contact ID.
Given this, there is no way to ensure that a given contact has been added via the API before attempting to, for example, create a new Invoice via the…
1 vote -
reminder
Optimise the collection process by having an automatic 'reminder' date (day/week) or a manual action to remind you to follow up outstanding account for payment. A calendar format to set action / follow update. Perhaps integrate with MS Outlook to include email attachments for follow up action.
1 vote -
Change back the layout of Contacts!!!
At such a busy time of year, getting use to a new layout sucks!
1 vote -
add custom fields to contacts
Ability to create or edit additional 'custom' fields to use for notes, additional phone numbers, job descriptions, etc.
114 votesCurrently, we’ve no plans to work on this feature but please continue to add your votes and comments.
We’re continually adjusting our priorities as different features are completed and your feedback is really important.
-
Website URL in API feed
Please include the Website URL in the API feed. Thanks.
7 votes -
Show payments in the Contacts suppliers
I would love to see the payments made against a supplier in the contacts.
ie: date of payment and amount. Then be able to drill down and see what invoices were paid. As it is you can see invoices and that they have been paid but not dates of payment or amount paid unless you drill down into invoice and then drill into payment.1 voteAs 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 make your suggestion in the Xero Community forum: https://community.xero.com/business/
-
Add coordinate elements (longitude, latitude) for street and delivery address types
This will enable mobile e-commerce apps
1 voteAs 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 make your suggestion in the Xero Community forum: https://community.xero.com/business/
-
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 -
Allow the full UTF8 character set in Contact Names
Names containing accented characters, eg: Nuñez, are rejected when uploading a new Contact.
13 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 -
make Xero contacts available over LDAP
Xero could export contacts via LDAP for integration with VOIP caller ID, email addressbooks and access control systems.
2 votesWhile I think it is a cool idea, it is not our model to provide specific technology interfaces like LDAP – it should be quite straightforward to connect to our API, return contacts in XML, and then make them available over LDAP with your own code.
- Don't see your idea?