51 results found

1. General Journal Improvements

   1) include transaction source and id to be able to link back to the source document of the journal eg AP/AR invoice etc 2) allow endpoint to be filtered by accounting date to be able to get just a certain period.

   58 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   11 comments  ·  Journals  ·  Delete…  ·  Admin →
   completed  ·  AdminXero Developer Platform (CEO / Founder, Xero Developer Centre) responded

   We are pleased to confirm that the Journals endpoint now returns the SourceType and SourceID. This allows you to link journals back to their source transaction.

   http://developer.xero.com/documentation/api/v2-release-notes/#2.83

   Unfortunately it is not possible to filter the journals endpoint by accounting date. We’ll look to address this with an improved journals reporting endpoint in future.

2. open standards data & document formats

   At the moment I can import & export financial data via an Open Standards CSV format (& well-documented API's), which is great for interoperability with other systems :)

   Unfortunately this is not carried through universally, such as Custom Invoice Branding, which is reliant on ms docx formats.
   This excludes a significant potion of my own customer-base (many SME's/SMB's reducing overheads) that are increasing not making use of manu ms-based technologies (i.e. office), and are increasingly moving toward more "cloud-based" solutions, such as Google Docs (sample docs are an absolute mess in GDocs) & Open/LibreOffice.

   Please add support for common, Open Standards formats, such as ODF & PDF, and less of a reliance on closed/vertical application stacks.

   At the moment I can import & export financial data via an Open Standards CSV format (& well-documented API's), which is great for interoperability with other systems :)

   Unfortunately this is not carried through universally, such as Custom Invoice Branding, which is reliant on ms docx formats.
   This excludes a significant potion of my own customer-base (many SME's/SMB's reducing overheads) that are increasing not making use of manu ms-based technologies (i.e. office), and are increasingly moving toward more "cloud-based" solutions, such as Google Docs (sample docs are an absolute mess in GDocs) & Open/LibreOffice.

   Please add support for… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  General Requests  ·  Delete…  ·  Admin →
   declined  ·  AdminXero Developer Platform (CEO / Founder, Xero Developer Centre) responded

   As 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/

3. document api response from POST,PUT and DELETE not only GET.

   i.e. on successful Contacts POST returned xml will be: <write>returned xml here</write>
   while on failure, depending on the cause, the following errors can be returned:<error> possible error here</error>
   And so on for all the methods in Contacts, Invoices etc.
   Currently only the GET responses are documented.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   completed  ·  AdminXero Developer Platform (CEO / Founder, Xero Developer Centre) responded

   This old issue has been fully addressed, but please feel free to let us know if there are any more documentation issues you spot.

4. Print Invoices & Packing Slips via API

   Currently, it is impossible to print Invoices and Packing Slips via API but this can be done via Web Interface.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Invoices  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Idempotent requests

   At the moment, its rather difficult to recover from a network interruption that happens when you send the request to Xero API, and you loose the connection before you receive the response from Xero. There is a fair number of reasons why this could happen at any time.
   In such a situation you really have no way of knowing if your request was even sent fully, or if it was received by Xero, nor what was Xero's response.

   This is not specific to Xero, as all APIs out there have this same problem, as its simply how the web works.

   Best solution to this I've seem so far are Idempotent Requests.

   With each request to Xero API you would include some kind of a unique identifier which only needs to be unique to you, not all of Xero users. For example if you need to send some invoices to Xero and you have each of them already saved in your database, you could send your primary key as your unique identifier as this is something that will not change on your end.

   Xero then reads your request and makes a note of what was requested and saves your unique key along with request params.

   If network goes down at this point, Xero will still know what you requested and prepare a response for you, but will not be able to deliver the response since the network connection is closed now.

   To retry, you just send the same request, with same unique identifier and Xero knows you already requested that, and just returns the cached response, that is was unable to deliver last time.

   In another scenario, if your network goes down even before Xero received your request, next time you send the request, it will be a new one for Xero, and it will be processed as usual.

   So in both cases, when network goes down before and after your request was received by Xero, its safe to retry your request once network connection is restored.

   Stripe is a nice example of an API that supports idempotent requests, which makes working with it much easier and worry free.

   https://stripe.com/docs/api?lang=curl#idempotent_requests

   If you were to try to achieve something like this now, it will not only be impossible to do in all cases, but it would also take a lot more of your time, be much more prone to bugs as you would need a separate system for each document type in Xero, plus it would eat into your rate limit as you would need to query the API first, before you can try sending your request again.

   At the moment, its rather difficult to recover from a network interruption that happens when you send the request to Xero API, and you loose the connection before you receive the response from Xero. There is a fair number of reasons why this could happen at any time.
   In such a situation you really have no way of knowing if your request was even sent fully, or if it was received by Xero, nor what was Xero's response.

   This is not specific to Xero, as all APIs out there have this same problem, as its simply how the web works.

   … more

   32 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  General Requests  ·  Delete…  ·  Admin →
   completed  ·  Public API PM responded

   Find out more in our Idempotent Requests guide: https://developer.xero.com/documentation/guides/how-to-guides/idempotency

6. Purchase Order (where) filter

   It is essential for our product to be able to filter Purchase Order by Contact, just like the Invoice end-point;
   Furthermore, having a symmetrical capabilities in "major" end points is a believe important to have - http://developer.xero.com/documentation/getting-started/http-requests-and-responses/#title3.

   23 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   10 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Create more granular accounting scopes (eg: Sales - Invoice only)

   Right now there is a very wide range of APIs wrapped up in the "accounting.transactions" scope, with no way to provide more granular access within these APIs (https://developer.xero.com/documentation/guides/oauth2/scopes#organisation-scopes).

   This means that it's not possible to grant access to something quite narrow without also granting access to other things that are often not needed. For example, you cannot grant permission to creating/manipulating Sales Invoices without also giving access to all Bank Transactions at the same time.

   This problem is perhaps accentuated for Custom Connections, which are designed to be used for "in house" integrations, as ALL developers with access to maintain such a sales invoice integration would effectively have access to their colleague's salaries and company bank balances and nothing can be done to mitigate against this.

   It feels like either there should be an extra layer of scopes such as "accounting.transactions.invoice" or "accounting.transactions.sales" available.

   I would also think this is quite easy to implement!

   Right now there is a very wide range of APIs wrapped up in the "accounting.transactions" scope, with no way to provide more granular access within these APIs (https://developer.xero.com/documentation/guides/oauth2/scopes#organisation-scopes).

   This means that it's not possible to grant access to something quite narrow without also granting access to other things that are often not needed. For example, you cannot grant permission to creating/manipulating Sales Invoices without also giving access to all Bank Transactions at the same time.

   This problem is perhaps accentuated for Custom Connections, which are designed to be used for "in house" integrations, as ALL developers… more

   57 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  11 comments  ·  Authentication  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Files API endpoint

   Develop a Files API that will let you perform actions like querying the files inbox, create folders in the inbox, upload new files to the inbox, associate files in the inbox with documents (like invoices, SM, RM's etc).

   13 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   5 comments  ·  Delete…  ·  Admin →
   completed  ·  AdminXero Developer Platform (CEO / Founder, Xero Developer Centre) responded

   We are pleased to announce we have launched the Files API today: https://www.xero.com/blog/2015/02/developer-opportunities-xero-files-api/

9. File Upload from Cloud Volumes

   Allow uploading of documents (my use case is Invoices) from cloud storage. Currently you can provide the document content, but it renders as a blank document in the viewer.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Support for Inventory Adjustments

    Add support for the inventory adjustments in the API.

    Currently you can effectively perform inventory adjustments via the API using invoices. See the tracked inventory guide for more info: http://developer.xero.com/documentation/api-guides/tracked-inventory-in-xero/

    This request is to expose the specific inventory functionality in Xero via the API.

    14 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Items / Inventory  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Multi-currency Bank Transfers

    Currently, if I try and send a Bank Transfer through the APIs between 2 accounts with different currencies, I get an error response with the message:

    "Multi currency Bank Transfers are not currently supported"

    There is a field for the "CurrencyRate" in the documentation for GET, however, setting this for a PUT call, results in the same error message.

    It's possible to do this through the UI as a user, it should also be possible to do this through the APIs.

    12 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Banking  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Email (send) purchase orders via API

    This is available in Web Interface, but API does not have any documentation on it.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Remove validation to allow 0 value spend money transactions on bank account to move money between accounts

    Currently it's possible to add a 0 value transaction on a bank account using the web interface by clicking "New Transaction" selecting "spend money" then adding a positive sum to one account and a negative sum to another account.

    When attempting this with the API you get a validation error "The Total for this document must be greater than zero".

    This is a simple request to remove the additional validation on the API to allow this transaction to be added (like you can in the web interface).

    Something similar can be achieved with a manual journal, however these don't support multiple currencies which means this method can't be used.

    Currently it's possible to add a 0 value transaction on a bank account using the web interface by clicking "New Transaction" selecting "spend money" then adding a positive sum to one account and a negative sum to another account.

    When attempting this with the API you get a validation error "The Total for this document must be greater than zero".

    This is a simple request to remove the additional validation on the API to allow this transaction to be added (like you can in the web interface).

    Something similar can be achieved with a manual journal, however these don't support… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Banking  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. 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.

    11 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    3 comments  ·  Invoices  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Make Receipt updatable via API

    The documentation says:

    PUT Receipts
    The PUT method is similar to the POST Invoices method, however you can only create new receipts with this method.

    It would be great if I was able to update receipts with the PUT method.

    6 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Receipts & Expenses  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Public API PM responded

    
    

16. fix the api documentation

    how are we supposed to develop to the api interface if the docs are wrong or out of date

    http://blog.xero.com/developer/api/get-apixro10invoice/

    the xsd is invalid (according to my parser line 56 and 57 are back to front

    the sample response can not be validated against the supplied xsd, ContactStatus, and InvoiceStatus are not in the xsd

    i hate to moan, but it is really frustrating, and i am wasting a lot of time through trial and error to figure things out.

    perhaps you could specify the values for ContactStatus and InvoiceStatus and what they mean

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Delete…  ·  Admin →
    completed  ·  AdminXero Developer Platform (CEO / Founder, Xero Developer Centre) responded

    Hi,

    Thanks for pointing out the error in our XSD – we’ll get this sorted. Please let us know if you find anything else. The quickest way to get help with these sort of issues is to email network@xero.com else it might be a few days before we get to them here.

    For sure we can provide more documentation for Contact Status and Invoice Status values. We’ll add some detailed notes on our API reference page shortly. The main statuses for contacts are ACTIVE & DELETED. All invoices entered via the API have an initial status of DRAFT

    I’ve updated our documentation on Invoice and Contact Status values in more detail than the summary above.

    See http://blog.xero.com/developer/api/

17. Customisation of packing slip

    There needs to be a simple way of customising the inbuilt packing slip (and accessing it) rather than having to go in and change the view.

    Or can you please amend it to at least include a signatory section for the recipient to sign as Proof of Collection and change the name to Delivery Note.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Invoices  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. new Bin Location field for Tracked Items will assist Warehousing and Inventory Management

    it would be useful to have a field which can be used to specify the warehouse location of the item needed for pick and packing

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Items / Inventory  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. include the optionID in the "Get budgets" operation

    According to the developer reference here https://developer.xero.com/documentation/api/accounting/budgets
    The get budgets operation should include both the tracking category option name and ID.

    Currently, only the name comes through which means we are forced to name match unless we validate the names via a seperate API call before trusting that budgets are for specific options.

    This method we are forced to use does not account for name collisions.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. bank transaction column names

    Change name & add an extra column in the bank transactions screen.
    Currently says Description - should be Payee
    Reference - Document ID/Invoice number)
    New Column - Description/Memo

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Banking  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating