Why aren't we getting a token back to our callback URI?

Clayton Loraine
Clayton Loraine
Name Dropper Facilitator 1 First Anniversary
in Blackbaud Raiser's Edge NXT® APIs

Hello! We're working with an integration team to integrate NetSuite with our RE NXT instance. When they connect to the SKY API and successfully authenticate, the SKY API doesn't appear to be sending the token correctly to the callback URI. We know the callback URI is correct and we are getting successfully sent back to it after authentication but the integration platform they are using is throwing an error saying that it did not receive a token in the process.

Any help with this would be appreciated! We're not sure if we need to give the URI permissions to receive the token somehow or if there's a way to see any errors on the SKY API side of things.

Answers

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 Facilitator 3 Raiser's Edge NXT Fall 2025 Product Update Briefing Badge

    Did you include the callback URI in the application redirect URI section?

    image.png
  • Clayton Loraine
    Clayton Loraine
    Name Dropper Facilitator 1 First Anniversary
    https://community.blackbaud.com/discussion/comment/307876#Comment_307876

    Yes we did, when we authenticate with the API it sends us to the callback URI that we have listed in there. We know authentication happens successfully and we know that it's the correct callback URI since if we remove it from the list of redirect URIs in the SKY API console, the SKY API throws an error saying that we cannot access it using that callback URI.

    So we know all that is correct, it's just that when it redirects, it doesn't include the token. I've attached a screenshot of the error our application throws when the SKY API redirects us.

    image.png

Categories