API Not working

@Parth patel
Good morning,
I'm sorry to hear about this experience. I'd like to identify if the problem is with the documentation (did we give you bad, or not enough, information) or a bug. I have a few questions to get started.

• The first part of the example call is https://secure2.convio.net/. Some sites use https://secure3.convio.net. Please open your organization's website or a donation form and check the URL to see if your org uses secure2 or secure3. (assuming you create your website and/or forms in Luminate Online)
• The second part of the call is /organization/site/. This must be replaced by the same information as you see in the URL for your website or donation forms. (assuming you create your website and/or forms in Luminate Online).
  For example, if your donation form URL is https://secure3.convio.net/goodnews/gns/donations then your api calls must start with https://secure3.convio.net/goodnews/gns/
• The third part of the call identifies which servlet to use. The available options are located near the top of each API documentation page.
  There are three parts to this- CR or SR indicates if this is a Client or Server Servlet. Then we identify which category of method this is (Constituent=Cons, TeamRaiser=TR, etc.,). The end of the Servlet is always API. The only option for getSingleSignOnToken is SRConsAPI.
  

So far our example call would be https://secure3.convio.net/goodnews/gns/SRConsAPI

• Next we need to identify the method we are calling. In this case getSingleSignOnToken. We add the method onto the call with ?method=methodname
  https://secure3.convio.net/goodnews/gns/SRConsAPI/?method=getSingleSignOnToken.
• Next we need to connect this call with our organization's resources with the correct API key. These additional parameters are added with ampersands &.
  (If you need help setting up or checking your API key, see Setup - LO API (blackbaud.com.) Please do not share your API key with anyone.
  For our example:
  https://secure3.convio.net/goodnews/gns/SRConsAPI/?method=getSingleSignOnToken & api_key=123456789
• Then we need to add our credentials which are our login name and password.
  https://secure3.convio.net/goodnews/gns/SRConsAPI/?method=getSingleSignOnToken & apikey=123456789 & loginname=johndoe & login_password=A1!password
• After this comes the required v parameter. The v stands for version and the only option is 1.0.
  https://secure3.convio.net/goodnews/gns/SRConsAPI/?method=getSingleSignOnToken & api_key=123456789 & v=1.0
• Then you must identify which constituent is being logged in. You can either use the constituent id or member id
  https://secure3.convio.net/goodnews/gns/SRConsAPI/?method=getSingleSignOnToken & apikey=123456789 & v=1.0 & cons_id=123
  OR
  https://secure3.convio.net/goodnews/gns/SRConsAPI/?method=getSingleSignOnToken & apikey=123456789 & v=1.0 & member_id=45678
• After this there are a number of optional parameters, but none of that should be necessary.

If none of those call parameters are the issue, then I'd ask if the third-party server that is trying to log the user into the Luminate System is not including any session cookies or session id. That is prevented for security reasons.

Finally, I'd verifty that getSingleSignOnToken is the correct method for what you need to accomplish. This method is only for authenticating constituents from third-party resources. If you just need to login a constituent, try the authenticateUser - LO API (blackbaud.com) method or the login - LO API (blackbaud.com) method.

And….if none of that helps, I'd suggest reaching out toSupport - Blackbaudand creating a ticket so we can fully research the issue.

I hope that helps.
Liz