v1

latestOpenAPI 3.1.02026-07-26189891.1 MB
Enterprise

Attach a child organization to an enterprise

Attaches an existing organization to an enterprise. The retention and owner field are optional, and will be defaulted if not specified. To specify which child organization to attach, one of its service keys must be supplied through our typical service key authorization schema; either as basic authorization or through the servicekey header.

post/v1/enterprise/account

Request body

retentioninteger

Current retention period selected for the child organization

ownerstring

The email of a user to be given owner privileges of an account.

Example request

{
  "retention": 7,
  "owner": "owner@example.org"
}

Response

Child organization successfully attached.

accountstring

Account number of the organization

enterprisestring

Unique Id of the enterprise organization

retentioninteger

Current retention period selected for the child organization

ownerstring

The email of a user to be given owner privileges of an account.

retentionPeriodsRetention[]

Available log retention options for the child organization

planstring

The name of a plan.

servicekeystring

A secret key which can be used to authenticate requests to Mezmo.

Example response

{
  "account": "0000000000",
  "enterprise": "0000000000",
  "retention": 7,
  "owner": "owner@example.org",
  "retentionPeriods": [
    7
  ],
  "plan": "enterprise",
  "servicekey": "7b273eb8adc962f2711ad760730debb0"
}