Add organisation
Adds an organisation to the installation, with its first admin and its organisation wallet. The first admin becomes the super admin of the organisation and gets access by an invitation e-mail or a one-time password (access). A new organisation has only the feature Issuer & Verifier on; configuredFeatures sets the features that differ.
The call has three steps: the organisation and its first admin, then the deployment of its wallet, then the access of the first admin. A failure of the wallet deployment or of the access does not undo the organisation: the answer is still 201, with walletDeployment.status failed, or without oneTimePassword. Then deploy the wallet with Deploy organisation wallet, send the invitation again, or set a one-time password. An answer with a one-time password has Cache-Control: no-store.
Authorizations
AuthorizationstringheaderrequiredAn access token:
Bearer <access-token>.
Body
organisationobjectrequiredfirstAdmin objectrequiredaccessenum<string>requiredHow the first admin gets access.
invitation: an invitation e-mail; this needs the e-mail service of the installation.oneTimePassword: a one-time password in the answer, which you give to the admin.Available options:
invitation,oneTimePasswordExample:
"oneTimePassword"configuredFeatures objectThe features that differ from those of a new organisation. A missing member keeps the value of a new organisation. A removed feature of an earlier release (for example
webhooksorprivacyDashboard) gets400.
Response
The organisation is made.
organisationobjectAn organisation of the installation as a platform admin sees it: its profile and its state. It has no data of the organisation, such as its credentials, records or keys.
firstAdmin objectAn admin account as a platform admin sees it.
oneTime Password objectA one-time password. The value is in this answer only: give it to the admin in a safe way. The answer has
Cache-Control: no-store.walletDeployment objectThe result of the deployment of the organisation wallet.