Improved

Configure the Y archiving vault per Workspace

The Y archiving vault identifier (archiving: archive_y) can now be set per Workspace, not only at Organization level. For a Signature Request, the vault is resolved on the Workspace first, then on the Organization. On Direct upload an archived file, an explicit workspace_id targets that Workspace's vault.

  • Workspace-restricted API keys are now accepted on Direct upload and Download archived file. workspace_id is required on upload and limited to the key's scope.
  • Breaking: a request set to archive_y with no resolvable vault is now refused with a 400 (configuration.archive_y_identifier_required) at Initiate or Activate, instead of failing later at archiving time. Integrations that do not require Y-archiving are not affected.