Create an API Key
On this page
Base URL: https://{OPSMANAGER-HOST}:{PORT}/api/public/v1.0
Resource
POST /orgs/{ORG-ID}/apiKeys
Request Path Parameters
Name | Type | Description |
---|---|---|
| string | Unique identifier for the organization whose API keys you want to retrieve. Use the /orgs endpoint to retrieve all organizations to which the authenticated user has access. |
Request Query Parameters
The following query parameters are optional:
Name | Type | Description | Default | ||||||
---|---|---|---|---|---|---|---|---|---|
pageNum | integer | Page number (1-index based). |
| ||||||
itemsPerPage | integer | Number of items to return per page, up to a maximum of 500. |
| ||||||
pretty | boolean | Indicates whether the response body should be in a prettyprint format. |
| ||||||
envelope | boolean | Indicates whether or not to wrap the response in an envelope. Some API clients cannot access the HTTP response headers or
status code. To remediate this, set For endpoints that return one result, response body includes:
For endpoints that return a list of results, the | None |
Request Body Parameters
All body parameters are required.
Name | Type | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| string | Description of the API key. Must be between 1 and 250 characters in length. | ||||||||||
| string array | List of roles that the API key should have. There must be at least one role listed, and all roles must be valid for an Organization. Organization roles include:
|
Response
Name | Type | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| string | Unique identifier for the API key | ||||||||||
| string | Description of the API key | ||||||||||
| string | Private key for the API key. This key appears unredacted only at the time of creation. | ||||||||||
| string | Public key for the API key | ||||||||||
| object array | Roles that the API key has | ||||||||||
| string | The | ||||||||||
| string | The name of the role. The
|
Example Request
Note
The user who makes the request can be formatted either as {PUBLIC-KEY}:{PRIVATE-KEY}
.
curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest \ --header "Accept: application/json" \ --header "Content-Type: application/json" \ --request POST "https://<ops-manager-host>/api/public/v1.0/orgs/{ORG-ID}/apiKeys?pretty=true" \ --data '{ "desc" : "New API key for test purposes", "roles": ["ORG_MEMBER"] }'
Example Response
Response Header
401 Unauthorized Content-Type: application/json;charset=ISO-8859-1 Date: {dateInUnixFormat} WWW-Authenticate: Digest realm="MMS Public API", domain="", nonce="{nonce}", algorithm=MD5, op="auth", stale=false Content-Length: {requestLengthInBytes} Connection: keep-alive
200 OK Vary: Accept-Encoding Content-Type: application/json Strict-Transport-Security: max-age=300 Date: {dateInUnixFormat} Connection: keep-alive Content-Length: {requestLengthInBytes} X-MongoDB-Service-Version: gitHash={gitHash}; versionString={ApplicationVersion}
Response Body
Note
The privateKey
appears unredacted in the response body. This
example is redacted for security purposes.
{ "desc" : "New API key for test purposes", "id" : "{API-KEY-ID}", "links" : [ { "href" : "https://<ops-manager-host>/api/public/v1.0/orgs/{ORG-ID}/apiKeys/{API-KEY-ID}", "rel" : "self" } ], "privateKey" : "********-****-****-db2c132ca78d", "publicKey" : "{PUBLIC-KEY}", "roles" : [ { "orgId" : "{ORG-ID}", "roleName" : "ORG_MEMBER" } ] }