Deprecating the v2 Routes and updating to the v3 Routes
What does it mean?
To improve compatibility and maintainability, we updated all of our API endpoints to use ID fields with a standardized type. We made changes to make specific fields use more efficient and appropriate value types. Because this change could cause clients not to interpret or send the correct types correctly, we have kept a previous version of these API endpoints available with the “v2” suffix. Now that enough time has passed, and all clients have been updated, we will deprecate these v2 routes and only allow the use of the new v3 routes.
For API endpoint calls to work, they must be updated to use the /v3/ suffix. In addition, all ID fields need to use a standardized integer field. Other changes are outlined in the API documentation that is currently available.
Please reference Taqtile API’s at api.taqtile.com. The URL’s in the environment will need to specify all 4 variables and reference v3
- Example: {{SUBDOMAIN}}.{{BASE_URL}}:{{PORT}}/graphql/{{VERSION}}
- Example with the variables specified: test.taqmanifest.com/graphql/v3
What does this mean for Manifest users? Please reference the Q&A below. If you continue to have questions, please reach out to manifestsupport@taqtile.com.
Q&A
QUESTION #1:
What will happen to Manifest Users on OLDER VERSIONS of MANIFEST (pre-version 4.0)
The user will see errors in the client applications. It’s important to update to the latest and greatest version of Manifest.
QUESTION #2:
I am using an API Script that is still using v2 Routes. How do I update it to use v3 Routes, and what will happen if I do not update it accordingly in my API Script? Try changing ‘/v2’ in your request to ‘/v3’. If that doesn’t help, please see the postman to fix your request or find similar ones. If you continue to have issues, please contact manifestsupport@taqtile.com for assistance.
QUESTION #3
I am currently using Manifest for Docker. I am on an older Version. Should I be concerned with running into these issues?
Manifest for Docker will not be affected by this change since it is in a closed environment. So customers (for example, those who are still using v2.8) won’t have issues once the converter is removed because they are in a Docker environment.
Additionally, one should also use a compatible version of the client. For example, it is not possible to use the 2.8 API server and 4.0 Manifest for iPad. If you find yourself updated on the clients but still using an older version of the API, please reach out to manifestsupport@taqtile.com, and we will provide you with a sideloaded build to ensure compatibility.
