Jump to content

Search the Community

Showing results for tags 'authorisation'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Welcome
    • General
    • Feature Requests
    • Content Requests
    • Ideas Exchange
  • Products
    • Sage Business Cloud Accounting
    • Sage X3
  • Services
    • Banking Service
  • SAGE X3 Developers's Topics

Categories

  • What's New?
  • Innovate and Co-create
  • Scale and Grow
  • Supporting You

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Job Title

Found 1 result

  1. Hello! We managed to successfully implement Sage API in our workflow using the official guide https://developer.sage.com/ api / accounting / guides / client_ app_registration /. Everything worked fine (app creation, Postman authorisation and final implementation). However, this was done only for our production environment. Because we also use 2 development environments (DEV and STAGE), we figured it would be best to create 2 more Sage apps and use their client secret and ids to authorise and use on those environments. But, despite doing the same thing as first time, when trying to get authorised via Postman, all requests fail (unauthorised, see attached screenshot). Meaning we can't get access/refresh tokens and cannot use Sage on our testing environment. How can we fix this and use multiple Sage apps in our workflow? This would be a really nice thing to have since using the same app for DEV, STAGE and PRODUCTION causes various outdated refresh/access token situations which we really want to avoid. Any advice is welcome! Thanks!
×
×
  • Create New...