Skip to main content
Technical Preview

Overview

Client-mode REST API connector for Veeva Vault QMS and QualityDocs: query effective SOPs and controlled documents, read document versions, renditions and lifecycle actions, query and read quality events, read object metadata, picklists and audit trails, and turn a line alarm into a deviation, through the Vault REST API v26.2. This is one of the templates in the Veeva Vault (QMS, QualityDocs) REST API app (veeva-vault). Deploy it alongside the other connectors of that app when they depend on each other (for example a token connector plus an API connector).
Not yet verified against the live vendor API: No Veeva Vault DNS, API access token or Vault user on the factory box (no VEEVA_VAULT_* variables) and Veeva offers no public sandbox Vault; the ready gate needs an authenticated live call (CreateSession or an API access token, then QueryDocuments and a create on a test object, or a broker MQTT round trip). Mock-server checks, the public login.veevavault.com discovery call and lot_lint do not clear the gate.

Auth

Authorization header from payload field authorization: an API access token as ‘Bearer veeva-vault-…’ (recommended) or a Vault session ID sent as is. Session from VeevaVaultAuth CreateSession (form username + password, reply sessionId / userId / vaultIds) or VeevaVaultLogin CreateOAuthSession (Bearer IdP access token + profile id, form vaultDNS + client_id). KeepAlive extends a session. DiscoverAuthType (public) tells password vs SSO users apart. Auth headers used by the template: Authorization: {value.json.authorization}.

Template parameters

BASE_ADDRESS default: https://YOUR_VAULT_DNS.

Events

Deploy

Get the template card (JSON with template and metadata) from the broker, then deploy the connector:
The deployable connector from the REST API app, with BASE_ADDRESS already filled in:
Deploy it with -addRoute (do not include ADD METADATA).

Usage example

Call ValidateSessionUser by publishing a JSON payload to its request topic, and read the reply on the response topic:
Last modified on October 21, 2026