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.
Documentation Index
Fetch the complete documentation index at: https://mezmo-9a59581a-mintlify-926f893d.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
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.
(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:
curl https://api.logdna.com/v1/config/view -u INSERT_API_KEY:Body
Request parameters.
Response
Child organization successfully attached.
Account number of the organization
"0000000000"
Unique Id of the enterprise organization
"0000000000"
Current retention period selected for the child organization
7
The email of a user to be given owner privileges of an account.
"owner@example.org"
Available log retention options for the child organization
Current retention period selected for the child organization
The name of a plan.
"enterprise"
A secret key which can be used to authenticate requests to Mezmo.
"7b273eb8adc962f2711ad760730debb0"