Navigation

Create a Configuration for a Third-Party Service Integration

Note

Groups and projects are synonymous terms. Your {GROUP-ID} is the same as your project ID. For existing groups, your group/project ID remains the same. The resource and corresponding endpoints use the term groups.

Important

Each project can only have one configuration per {INTEGRATION-TYPE}.

Base URL: https://cloud.mongodb.com/api/atlas/v1.0

Syntax

POST /api/atlas/v1.0/groups/{GROUP-ID}/integrations/{INTEGRATION-TYPE}

Request Path Parameters

Parameter Required/Optional Description
{GROUP-ID} Required Project identifier.
{INTEGRATION-TYPE} Required

Third-party service identifier. Accepted values are:

  • PAGER_DUTY
  • SLACK
  • DATADOG
  • NEW_RELIC
  • OPS_GENIE
  • VICTOR_OPS
  • FLOWDOCK
  • WEBHOOK

Request Query Parameters

The following query parameters are optional:

Name Type Description Default
pageNum integer Page number (1-based). 1
itemsPerPage integer Number of items to return per page, up to a maximum of 500. 100
pretty boolean Displays response in a prettyprint format. false
envelope boolean Specifies whether or not to wrap the response in an envelope. false

Request Body Parameters

The request body should be a single integration view (i.e. a JSON configuration object) for a single third-party service to add to the project. Always include a type property equal to the third-party service INTEGRATION_TYPE.

Service Configuration Options
PagerDuty

You must provide the following fields when you configure a PagerDuty integration:

Property Description
type PAGER_DUTY
serviceKey Your Service Key.
Slack

Important

Slack integrations now use the OAuth2 verification method and must be initially configured, or updated from a legacy integration, through the Atlas third-party service integrations page.

Legacy tokens will soon no longer be supported.

You must provide the following fields when you reconfigure an existing Slack integration:

Property Description
type SLACK
apiToken Your API Token.
teamName Your team name.

You may also include the following fields:

Property Description
channelName The channel name to reconfigure.
Datadog

You must provide the following fields when you configure a Datadog integration:

Property Description
type DATADOG
apiKey Your API Key.
region Indicates which API URL to use, either US or EU. Datadog will use US by default.
New Relic

You must provide the following fields when you configure a New Relic integration:

Property Description
type NEW_RELIC
licenseKey Your License Key.
accountId Unique identifier of your New Relic account.
writeToken Your Insights Insert Key.
readToken Your Insights Query Key.
Opsgenie

You must provide the following fields when you configure a Opsgenie integration:

Property Description
type OPS_GENIE
apiKey Your API Key.
region Indicates which API URL to use, either US or EU. Opsgenie will use US by default.
VictorOps

You must provide the following fields when you configure a VictorOps integration:

Property Description
type VICTOR_OPS
apiKey Your API Key.

You may also include the following fields:

Property Description
routingKey An optional field for your Routing Key.
Flowdock

You must provide the following fields when you configure a VictorOps integration:

Property Description
type FLOWDOCK
flowName Your Flowdock Flow name.
apiToken Your API Token.
orgName Your Flowdock organization name.
Webhook Settings

You must provide the following fields when you configure webhook settings:

Property Description
type WEBHOOK
url Your webhook URL.

You may also include the following fields:

Property Description
secret An optional field for your webhook secret.

Response Elements

The response includes a results array which lists all third-party integration configurations for the project as objects, and a totalCount of the services integrated with the project. The results array includes the integration view added by the request.

Each third-party integration configuration object includes a type property equal to its own integration type (e.g. "type": "PAGER_DUTY" for the PagerDuty service). Additionally, each third-party service configuration object provides details specific to that service. The following lists the properties returned for each third-party service configuration object:

Service Result
PagerDuty

A returned PagerDuty integration configuration object will contain the following fields:

Property Description
type PAGER_DUTY
serviceKey Your Service Key.
Slack

A returned Slack integration configuration object will contain the following fields:

Property Description
type SLACK
apiToken Your API Token.
teamName Your team name. This field may not be present with a legacy Slack integration.
channelName The configured Slack channel name. An empty string if the value is not set.
Datadog

A returned Datadog integration configuration object will contain the following fields:

Property Description
type DATADOG
apiKey Your API Key.
region Indicates which API URL is used, either US or EU. Datadog will use US by default.
New Relic

A returned New Relic integration configuration object will contain the following fields:

Property Description
type NEW_RELIC
licenseKey Your License Key.
accountId Unique identifier of your New Relic account.
writeToken Your Insights Insert Key.
readToken Your Insights Query Key.
Opsgenie

A returned Opsgenie integration configuration object will contain the following fields:

Property Description
type OPS_GENIE
apiKey Your API Key.
region Indicates which API URL is used, either US or EU. Opsgenie will use US by default.
VictorOps

A returned VictorOps integration configuration object will contain the following fields:

Property Description
type VICTOR_OPS
apiKey Your API Key.

The configuration object may also contain the following fields, depending on your configuration:

Property Description
routingKey An optional field returned if you have a Routing Key configured.
Flowdock

A returned Flowdock integration configuration object will contain the following fields:

Property Description
type FLOWDOCK
flowName Your Flowdock Flow name.
apiToken Your API Token.
orgName Your Flowdock organization name.
Webhook Settings

A returned webhook configuration object will contain the following fields:

Property Description
type WEBHOOK
url Your webhook URL.

The configuration object may also contain the following fields, depending on your configuration:

Property Description
secret An optional field returned if your webhook is configured with a secret.

Example Request

curl -X POST -u "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest "https://cloud.mongodb.com/api/atlas/v1.0/groups/5d791c84ff7a2522cc4f9aa1/integrations/FLOWDOCK" \
-H 'Content-Type: application/json' \
-d '{ "type": "FLOWDOCK", "flowName": "myFlowName", "apiToken": "112233", "orgName": "myOrg" }'

Example Response

{
     "links": [
         {
             "href": "https://cloud.mongodb.com/api/atlas/v1.0/groups/5d791c84ff7a2522cc4f9aa1/integrations/FLOWDOCK?pageNum=1&itemsPerPage=100",
             "rel": "self"
         }
     ],
     "results": [
         {
             "apiKey": "112233",
             "region": "US",
             "type": "DATADOG"
         },
         {
             "apiToken": "112233",
             "channelName": "My Channel",
             "teamName": "My Team",
             "type": "SLACK"
         },
         {
             "apiToken": "112233",
             "flowName": "myFlowName",
             "orgName": "myOrg",
             "type": "FLOWDOCK"
         }
     ],
     "totalCount": 3
 }