The QQ Catalyst API allows developers to build apps that integrate with QQ Catalyst and securely access Catalyst data via our application services. If you would like to integrate with Catalyst, we have everything you need right here. To get started with Catalyst API integration, please contact our API team via email. We’ll then talk with you about becoming an API partner.
In order to interact with the Catalyst API, you will need to register with QQ Solutions as an API partner. After successfully registering, we will provide you with security tokens and credentials for use during authentication, as documented in the security section of this site. Subsequently, each of your insurance agency customers will need to work with you directly to allow your app to access to their individual Catalyst accounts.
Once you have registered as an API partner, you can download our sample application and view our detailed API documentation. We will also set you with a sandbox Catalyst account (for a nominal annual fee) and help you bring your product to life.
Security of our user's data is at the forefront of our concern. Our users should have the confidence that their data is secure and there will be no unauthorized access. Our API Login process will always require a user to login through QQ Catalyst secure web channels.
QQ Catalyst protects access to our users' data via access tokens provided integrator and via OAuth2 for authentication. The integrating application must be registered with QQ Solutions as a vendor partner in order to receive a security token for access. After you are approved as a partner, our customer will be able to allow or deny access to their individual Catalyst data. If you are not familiar with OAuth2 standards or processes, check out the OAuth 2.0 Standards page to learn more about the technology.
For more information on our Authentication mechanism, review the Authentication section of this document.
QQ Catalyst uses OAuth2 as our authentication mechanism. All API consumer applications are required to authenticate and authorize both the application and the user against QQCatalyst. OAuth 2.0 is the next evolution of the OAuth protocol originally created in 2006. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices. If you are developing with Visual Studio, we highly recommend that you use the tools provided in the DotNetOpenAuth libraries, which can be found here or in NuGet inside Visual Studio.
After you have successfully signed up with QQ Solutions for access to the API as mentioned in the Getting Started section, you can use the callback URL and custom token to call the OAuth Login Server. The two URLs that you will need to access the Login server are:
When your application leverages our active authentication, your users will be prompted for their QQ Catalyst credentials as part of the authentication process. This is the recommended method for 3rd party access to QQ Catalyst when using a visual application. By using OAuth2 standards with an active authentication, no 3rd party developer will need to gather or store a user's login credentials; instead they will redirect QQ Catalyst users to our login page as shown below. When using this method, the url of our login site should always start with "https://login.qqcatalyst.com/" and the page should have the following security log at the bottom right hand corner.
When your application leverages our passive authentication, you will be responsible for gathering and providing all credentials needed by QQ Catalyst for the authentication process. This method is best when creating non-visual or service based applications needing 3rd party access to QQCatalyst. In this scenario, all authentication information must be gathered and stored for use by your application.
Here are some links to additional information that will help you as you integrate with QQ Catalyst.
Would you like to integrate your product with the most advanced agency management software on the market? If so, contact the QQ Solutions API Team to get started.
At QQ Solutions, we are committed to providing a stable, flexible and powerful API. If you have a specific feature request or if you found a bug, please let us know!
Following is a list of the API services. These services are RESTful WCF Services that implement a dynamic response mechanism. By changing the Accepts value in your Request header, our services will provide a response in either JSON or XML format. If you do not specify a preference, these services will respond in JSON