![]() ![]() The root URL is the foundation for any API request. The current Qualtrics API system uses a root URL to perform requests: /API/ Through these means, the Qualtrics API allows you to interact with parts of the Qualtrics system and integrate these areas with your CRM. These requests can be made by either GET, POST, PUT, or DELETE requests, which return JSON responses. You can request information to be sent to Qualtrics, updated, removed, or returned to your system. Communicating with the Qualtrics system can be thought of as a sequence of requests. The Qualtrics v3 API is a REST API that allows you to communicate or query our system using a simple URL syntax. Please note that we always recommend that our clients use the latest version of the API. Here are links to the documentation for the latest version of the API for each of our products: Once you’ve purchased the Qualtrics API feature, you’ll be able to use the API for any products that are a part of your license. Some of these products include the Survey Platform, Site Intercept, and XM Directory (Target Audience). Qualtrics has a variety of different products that allow you to gather actionable data in real time. ![]() If you’d like to know more about our custom coding services, please contact your Qualtrics Account Executive. You can always try asking our community of dedicated users instead. Our support team does not offer assistance or consultation on custom coding. Take note of the Client ID and Client Secret that are generated.Attention: API extensions may require programming knowledge to implement.Under Authorized redirect URIs enter Prismatic's OAuth 2.0 callback URL:.Under Application type select Web application.Click +CREATE CREDENTIALS and select OAuth client ID.Once your "Consent Screen" is configured open the Credentials page from the sidebar again.That'll allow your customers to authorize your integration to access their Google Drive. When you are ready for verification (they verify your privacy policy statement, etc), click PUBLISH APP on the OAuth consent screen. Your app will only work for those testing users until it is "verified" by Google. Enter some test users for your testing purposes.On the next page, ignore scopes - this component knows what scopes it needs to run and will request the right scopes for you.Fill out the OAuth consent screen with an app name (your company or product's name), support email, app logo, domain, etc.Your app will be externally available to your customers, so choose a User Type of External.An OAuth 2.0 app includes a "Consent Screen" (the page that asks "Do you want to allow (Your Company) to access Google Drive on your behalf?"). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |