We have several use cases in my organization where API integration from top to bottom is the most desirable approach. In these instances the consumers use the APIs to distribute surveys AND gather the response data using the export APIs. As such, the actual Qualtrics contacts and all the associated IDs are mostly meaningless overhead to these consumers. To simplify this process, I've been doing proof of concept around leveraging Actions to distribute surveys and API event subscriptions to gather completed survey response data close to real-time rather than having to run CRON jobs to export responses every so often. I LOVE this idea because our API consumers no longer have to concern themselves with managing mailing list IDs, contact IDs, library IDs, message IDs, subject IDs etc. and they don't have to write complicated CRON jobs for ETL. Instead they can simply provision a URI from the JSON action event, define their own JSON payload, map the fields as required and kick off a task to
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
