Aaron Trevena

answering my own question based on feedback from the sagesoft developer team - there is no support currently or planned for being able to create invoices in sage 200 through the rest API, the only option is to create sales orders and manually create invoices from those following the process in Print invoices from sales orders (sage.co.uk)

While attempting to use the Postman collection for the Sage 200 REST API, I'm finding that the sop_orders sage endpoint is always returning 403 while other endpoints for customers, sales transactions, etc are all returning 200 status and json payloads with expected data. Is there some sort of access control in the sage 200 setup restricting the API as I can’t find any documentation on that – or is it that the SOP module needs to be enabled or setup for these endpoints to be available?

I'm trying to find an explanation or documentation of how to create invoices in sage 200 using the REST API - the invoices endpoint doesn't seem to create anything that can be used as an invoice, and https://www.sagecity.com/gb/sage-200/f/general-discussion/143666/api-endpoint-for-draft-invoices---with-line-items suggests creating a sales_order and using an undocumented process to go from there to an actual invoice. So how, exactly, can a useful invoice, that our finance team can send to customers, be created through the REST api?

Thanks Ben, It's a bit disappointing that the OAuth "confidential client" standard for machine to machine isn't supported, but we'll add this workaround. Is there any update on providing confidential client model authentication to the API? I've seen requests for that for the last couple of years with no ETA on it being provided. Thanks again, Aaron

Hi all, Whats the recommended approach for integrating with sage 200 without human intervention (aws lamda functions, cron jobs, message queue workers, e-commerce) ? On 9/20/2022 at 11:21 AM, Steel, Mark said: This would appear to rule out using the Sage 200 API for any e-commerce integration which would need to be fully automated and unattended - what API is provided for that - and does Sage provide a confidential client OAUTH authentication option as per the RFC? There's no mention of this possibility anywhere in the API documentation or in here, all I could find was that it's unsupported - are users who need automation and e-commerce supposed to move away from sage and use something else? Thanks, Aaron

This would appear to rule out using the Sage 200 API for any e-commerce integration which would need to be fully automated and unattended - what API is provided for that - and does Sage provide a confidential client OAUTH authentication option as per the RFC? Thanks, Aaron