Jump to content

Aaron Trevena

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by Aaron Trevena

  1. 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?

  2. 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?  

  3. 43 minutes ago, Ben Smith said:

    You can essentially have a connection to the UKI 200 API unattended using the refresh token to maintain it. During the initial setup, manual login must be provided as part of the oauth process, but after that, the access token can be refreshed indefinitely and without the need for manual intervention. 

    Is this what you need to confirm?

    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

  4. 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:

    > The restriction of not being able to pass the business credentials is not one of Python but one of the Sage Business Cloud Accounting oAuth implementation.

    >You can not complete the auth flow without the manual intervention of the user entering their Sage business credentials to authorise.

    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

  5. On 9/20/2022 at 11:21 AM, Steel, Mark said:

    > The restriction of not being able to pass the business credentials is not one of Python but one of the Sage Business Cloud Accounting oAuth implementation.

    >You can not complete the auth flow without the manual intervention of the user entering their Sage business credentials to authorise.

    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

×
×
  • Create New...