Ben Smith

Hi Ronen, Unfortunately at present we don't have an alternative, if the request fails the only alternative is to re-authenticate. I'll certainly feed this back to our engineering team, as I can fully appreciate the frustration. Do you have further details on whats happening when you get these failures? Ben

Hi Josh, Thanks for reporting this - we'll investigate and get back to you as soon as possible. Ben

Hi Tom, Currently there isn't a REST API available for Sage 50cloud Accounts provided by Sage, but we do have partners and other third parties that provide a middleware connector, installed where the Sage 50 data is stored, and provide an API for clients to consume. Whilst I cannot recommend one over another, if you google "API for Sage 50" there are at least two on the first page. Hope that helps! Ben

Hi Alain, I've sent you a DM about this. Ben

Hi Thivagar, I'm looking into this at the moment, I'll get back to you as soon as possible. Ben

Glad you're up and running Jon - also appreciate you coming back to update with the solution! Ben

Hi Alex, Thanks for pointing this out - I've replicated the exact same behaviour tonight. I'll discuss with our engineering team, and clearly it's not only inconsistent with the other dates, but contrary to whats shown in the openapi spec as you say. I suspect a bug, and will treat as such - I'll update you once I have more. Ben

Hi Jeeva, Really sorry for the delay in getting back to you - if you can ask the same question over on our Sage City community for the US we have a forum specifically for Sage 100: https://www.sagecity.com/us/sage100_erp/ Ben

Hi Everyone, We'd like to invite you all to join Sage on-screen at #SageDevStream Oct 28 to learn about our: ⚡ #Accounting API 🎱 @gosuperscript partnership 📡 Local market updates Registration is free so please come innovate ➡️https://bit.ly/39wjpTo

Hi Daniel, Sorry for the delay. I've had a meeting this morning to figure this all out. Essentially the change from a string ID to a GUID has come about with recent changes made as part of the EU VAT reform updates we made. A new endpoint has been added called tax determinations which essentially returns a list of legislatively valid tax rates when queried along with params describing the usage etc. Due to the vastly increased number of rate combinations required and the way they are generated a GUID was used. It isn't a one off and won't be something we'll be in a position to change. I am however sorry that this hasn't been communicated prior to the change going into production. What we are recommending going forward is that you don't use the ID property to show information to the customer (allowing for selection etc.), and rather than concatenating name + id, just the displayed_as property instead, as that will remain a string description, and as you may have seen is in many instances in fact a better description than the ID & name were previously. I hope you are ok to make this change, and apologies again that we didn't get this information out prior to that release. Ben

Thanks for this suggestion, to ensure its fed back to the right team can you advise which Sage product this is for please? Ben

Hi John, Apologies for the delay in you getting a response. Unfortunately, although there have been many discussions in the past about APIs etc. for Sage 50cloud Accounts, at present you can integrate via the .NET SDK, and have read only access using ODBC queries. The only API connectivity at present is via our partner solutions that utilise a form of middle-ware connector. Ben

Hi Jeeva, Can you confirm which product and region this is you are working with please? Ben

Hi Roberto, Can you confirm is this Sage 200 UK or Spain? Ben

Hi Melvyn, can you advise which Sage product you are looking to have this integrate with please? Ben

Thanks a lot Daniel, that makes perfect sense. I'm discussing it with the engineering team at present and will update you as soon as I have more.

Hi Daniel, Could you give me details on what specifically about the use of the GUID is breaking your integration please? Thanks

Hi Daniel, Thank you for bringing this to my attention - I'll investigate and get back to you ASAP. Thanks, Ben

Hi, If you are referring to the Sage 300 SDK here, please contact our Sage City community for assistance with Sage 300. Thanks!

Hi Sethupathi, Thanks for providing those details. So this is an intermittent issue is that correct? Have you checked your own application logs? Can you also advise what language/framework you are using for this app please? Thanks, Ben

Hi Tamuno, At this time the initial authentication requires a user to input credentials to successfully log in, then authorise an application to access the business. Once this has been done, it's then possible to utilise the refresh token to effectively keep the connection alive. Ben

Hi Eugenia, 1. So the terminology used in that document refers to payments and receipts as payments out and payments in. Whenever you are using a csv import you must ensure that the value of payments out (so actual payments) are set to a -ve value. 2. You can import the following types of data: Chart of Accounts Customer and Supplier contacts Customer or Supplier opening balances Products or services Batches of Sales or Purchase quick entries Transactions via Opayo When creating credits via the quick entry batch import you can just leave all figures as positives as you state the Type in the first column (Cr Note / Invoice). 3. Sage Business Cloud Accounting has the concepts of Invoices or credits, so no Sales debit notes, only invoices. Ben

Hi Fabio, Can you confirm which Sage product you are referring to please? Thanks Ben

Hi, That makes sense then, and is something we will have to consider going forward for sure, and thanks for clarifying. We have a guide on pagination here which details the parameters provided. I would agree that using $next to reach the last page is the best option, and one I've suggested in the past. I'd be keen to see the tweak you have made, and will contact you separately about that. Ben

Hi Tadej, I'll contact you via DM to get some further details. Ben