Skip to main content
POST
Attach a child organization to an enterprise

Authorizations

enterprise-servicekey
string
header
required

When authorizing against our enterprise endpoints, they expect an enterprise service key instead of a regular organization service key. Some endpoints might expect both an enterprise service key and a regular organization service key.

Authorization
string
header
required

(Deprecated) As an alternative to authenticating with a header value, you can also use basic authentication. To use either apiKey or servicekey as basic authentication, simply pass the key as the username with no password. For example:

Body

application/json

Request parameters.

retention
integer

Current retention period selected for the child organization

Example:

7

owner
string

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

Example:

"owner@example.org"

Response

Child organization successfully attached.

account
string

Account number of the organization

Example:

"0000000000"

enterprise
string

Unique Id of the enterprise organization

Example:

"0000000000"

retention
integer

Current retention period selected for the child organization

Example:

7

owner
string

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

Example:

"owner@example.org"

retentionPeriods
integer[]

Available log retention options for the child organization

Current retention period selected for the child organization

plan
string

The name of a plan.

Example:

"enterprise"

servicekey
string

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

Example:

"7b273eb8adc962f2711ad760730debb0"