Hi Everyone,
I am not experienced with code or the API, so my apologies if I am not explaining this clearly.
Our office has 7 different API v2 calls that need to be moved to V3.
* addRecipient
* getDistributions
* updateRecipient
* sendSurveyToPanel
* createPanel
* sendReminder
To the best of my knowledge all of our API's are done through posting to the php URL: https:\\survey.qualtrics.com/WRAPI/ControlPanel/api.php with commands passed and parameters in the URI.
The V3 migration guide says you can no longer do this. So here are my questions:
* Does this mean we can no longer use PHP as part of our API's?
* Does this mean we have to rebuild our API calls from scratch?
* If we have to build it from scratch, what is the best coding language to use?
* What would be the most efficient way of moving these calls to API V3?
Thanks in advance for your help!
Userlevel 7
+27
> @uhrxx005 said:
> To the best of my knowledge all of our API's are done through posting to the php URL: https:\\survey.qualtrics.com/WRAPI/ControlPanel/api.php with commands passed and parameters in the URI.
>
> The V3 migration guide says you can no longer do this. So here are my questions:
> * Does this mean we can no longer use PHP as part of our API's?
The v3 API endpoints are different from v2. The fact that v2 used PHP is irrelevant.
> * Does this mean we have to rebuild our API calls from scratch?
Yes.
> * If we have to build it from scratch, what is the best coding language to use?
The one that you are most familiar with. PHP or Python are both good choices. If you were using curl with PHP it will be very similar, but you will need a few tweaks.
> * What would be the most efficient way of moving these calls to API V3?
If you are using a script to do the api calls, I would make a copy of the script then modify the copy for v3.
> To the best of my knowledge all of our API's are done through posting to the php URL: https:\\survey.qualtrics.com/WRAPI/ControlPanel/api.php with commands passed and parameters in the URI.
>
> The V3 migration guide says you can no longer do this. So here are my questions:
> * Does this mean we can no longer use PHP as part of our API's?
The v3 API endpoints are different from v2. The fact that v2 used PHP is irrelevant.
> * Does this mean we have to rebuild our API calls from scratch?
Yes.
> * If we have to build it from scratch, what is the best coding language to use?
The one that you are most familiar with. PHP or Python are both good choices. If you were using curl with PHP it will be very similar, but you will need a few tweaks.
> * What would be the most efficient way of moving these calls to API V3?
If you are using a script to do the api calls, I would make a copy of the script then modify the copy for v3.
+4
From what I understand, we need to change our "UpdateRecipient" call from v2 to v3 by the end of the month. We use the webservice in the flow so it's not like I'm using script. Do I just change the webservice address and then update the version from 2.5 to 3? The new address (removing PHP) is shown as: https://yourdatacenterid.qualtrics.com/API/v3/.....
Leave a Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.