VisionConsentRequest vision.consent-request@1

Generated at from openvibe-contracts v0.419.0 and openvibe-sdk v0.161.0.

Version
1.0.0
Owner
vision
Visibility
first-party
Status
active
Compatibility
backward
Schema
https://openvibe.network/contracts/vision/consent-request.v1.json

vision.consent-request@1: POST /api/v1/faces/consents/:feature. The caller signs the current text (`text_version` must match this server's), names themself (`signed_name`), and for cast must confirm they are an adult; library grouping is refused outside the host's allowed regions. A repeat of an active consent changes nothing.

Fields

FieldTypeRequiredDescriptionConstraints
signed_namestringyes
  • minLength 1
  • maxLength 160
text_versionstringyes
  • maxLength 80
modalityenum
  • one of "face", "voice"
featureenumEcho of the :feature path segment.
  • one of "verify", "find", "cast", "library", "voice"
channelstring
  • pattern ^[a-zA-Z0-9][a-zA-Z0-9:_-]{1,119}$
adultboolean
regionstring
  • maxLength 10

Examples

From the contract's own test fixtures: valid ones validate, rejected ones must fail.

Valid: one
{
  "signed_name": "Ana Ruiz",
  "text_version": "face-cast-2026-10-28",
  "feature": "cast",
  "channel": "live:one",
  "adult": true
}
Rejected: one
{
  "signed_name": "",
  "text_version": "face-cast-2026-10-28"
}

Validate

const contracts = require('openvibe-contracts');
contracts.validate('vision.consent-request@1', value);   // { valid, errors: [{ path, message }] }