Update organisation features
Turns features of an organisation on or off. Send only the features that you change; a missing member keeps its value. A removed feature of an earlier release (gettingStarted, dataAgreements, managedData, privacyDashboard, account, actionLogs, webhooks, files or sandbox) gets 400 with a text that names it. When a feature is off, the API refuses its operations for the organisation with 403 and errorKey feature_disabled. A change is written in the Activity Logs of the platform operator organisation.
Authorizations
AuthorizationstringheaderrequiredAn access token:
Bearer <access-token>.
Path parameters
organisationId stringrequiredThe ID of the organisation, from List organisations of the installation.
At most 256 characters.
Example:
"6731f0c2a1b2c3d4e5f60789"
Body
issuerVerifier booleanIssuer & Verifier.
Example:
truewalletUnit booleanWallet Unit (Holder).
Example:
trueconsentManagement booleanConsent Management.
Example:
truedataDisclosure Agreements booleanData Marketplace.
Example:
falseapiKey Scopes Ui booleanThe feature preview of the scope picker of the new API key scopes.
Example:
false
Response
The features of the organisation after the change.
configuredFeatures objectThe features of an organisation. The four product features decide which parts of the platform the organisation can use: when one is off, the API refuses its operations for the organisation with
403anderrorKeyfeature_disabled. Getting Started, Account, Webhooks and Activity Logs have no feature and are always on. See Organisation features.