Starting with 26R3, the DQS API framework is aligning its versioning lifecycle and base URL structure with standard Vault and EDC API patterns. This unifies API integrations across Vault applications, giving developers a more consistent and predictable experience going forward.

DQS is replacing its previous domain-specific versioning (which versioned Forms, Queries, and SFF separately) with the Vault and EDC API standard versioning lifecycle. New DQS API versions will follow the standard pattern for three releases a year: vYY.ReleaseNumber (for example, v26.1, v26.2, v26.3, etc.).

In addition, DQS is migrating to a unified URL structure. From version v26.3 onward, you can use the Vault URL to directly call all DQS API endpoints:

• Legacy URL Pattern: https://[DQS-domain]/edcworkbench/api/{version}/[resource]
• New URL Pattern: https://[Vault-domain]/api/{version}/dqs/[resource]

All new or updated endpoints support only the new Vault URL path, and new customers exclusively use the Vault DNS for all integrations. To ensure backwards compatibility, existing customers can temporarily continue to use the legacy DQS DNS for existing DQS API endpoints or updated endpoints executed with an older API version. Veeva will support this legacy path for a transition period to allow time for migration and provide advance notice before ending support.

Only Limited Release and Pre-Release Vaults will support the new Vault URL path. For more information, including URL examples and changes to responses and errors, see the 26R3 DQS API Release Notes.