Developer Features in 18R2

We are pleased to bring you the following additions and enhancements to Developer Portal features in 18R2. REST API features added in 18R2 only affect API v18.2, unless otherwise noted.

Removal of Weaker TLS Ciphers

Beginning in 18R1.3 (June 1, 2018), we will remove support for 1024 bit Diffie-Hellman ciphers and TLS v1.0 and will only support Elliptic Curve and TLS v1.2. To ensure your integrations continue working with Vault API, you must ensure that the technology you use to build and run integrations support strong ciphers.

18R1.2

Release Date: April 27, 2018

We are pleased to bring you the following additions and enhancements to Developer Portal features in 18R1.2. REST API features added in 18R2 only affect API v18.2, unless otherwise noted. You can learn more about the 18R1.2 Release in Vault Help.

REST API v18.2

Multi-Site Document Distribution

As of API v18.2, users in Clinical Vaults can now use the existing Document & Binder User Actions endpoints to initiate multi-site document distribution workflows. These workflows distribute important documents, such as protocol amendments, revised informed consent form templates, and safety information documents, to many study sites at once. Learn more about multi-site document distribution in Vault Help.

Accept Vault Session IDs as Bearer tokens

This feature allows API client applications and integrations to send Vault Session IDs inside an Authorization HTTP Request Header with a Bearer keyword, as if it was a real Bearer OAuth token.

For example: Authorization: Bearer {Vault Session ID}

Learn more about Authentication in the REST API v18.2 Reference.

Configurable Copy Fields

In this release, users can configure which fields to copy when executing the Make a Copy action on a document. Document fields have a new noCopy attribute when retrieving document field metadata, where true means this field is not copied. You cannot set the noCopy value through the API, and must do so through the UI.