Issues with Authorizing & Obtaining Access Token for SMS API Integration in CRM

Sanjaikumar Senthilkumar
Sanjaikumar Senthilkumar
Facilitator 1
in Blackbaud CRM™ APIs

I am working on integrating our own SMS API into the CRM and am encountering issues while authorizing and obtaining an access token using the test application. I have a developer account, but I am facing challenges in getting proper API access.

Current Scenario:

  • I have a developer account and am using the test application for API integration.
  • The authentication process is failing, preventing me from obtaining an access token.
  • The system is suggesting that I contact the organization admin for product and API access.

Challenges Faced:

  1. Authorization Issues: Unable to authenticate and retrieve an access token.
  2. API Access Permissions: Not sure if additional permissions are required from the organization admin.

Finally, How to create the organization admin account

Comments

  • Erik Leaver
    Erik Leaver Blackbaud Employee
    Tenth Anniversary Kudos 5 First Reply Name Dropper

    @Sanjaikumar Senthilkumar See the response I provided to @Surish Payoda here:


  • Sanjaikumar Senthilkumar
    Sanjaikumar Senthilkumar
    Facilitator 1

    @Erik Leaver
    I'm currently working on a project where I’ve implemented user login and authorization successfully. Once a user logs in, the application routes them to a specific page and makes a fetch request like this: fetch('/api/constituents/280')
    Right now, the 280 is hardcoded as the constituentId, but I want to make this dynamic. The goal is to automatically fetch and use the logged-in user’s actual constituentId instead of relying on a hardcoded value.

    What I Need to Know:

    Where or how can I retrieve the correct constituentId after login?

    Should it be returned as part of the login response (e.g., in a token or user object)?

    Is there a standard pattern or best practice to securely pass and use this value in subsequent API calls?

Categories