# API destination partners in Amazon EventBridge
Use the information provided by the following AWS Partners to configure an API destination and connection for their service or application.
## Cisco Cloud Observability
**API destination invocation endpoint URL:**
`https://tenantName.observe.appdynamics.com/rest/awsevents/aws-eventbridge-integration/endpoint`
**Supported authorization types:**
OAuth client credentials
OAuth tokens are refreshed when a 401 or 407 response is returned
**Additional authorization parameters required:**
Cisco AppDynamics Client ID and Client Secret
OAuth endpoint:
`https://tenantName.observe.appdynamics.com/auth/tenantId/default/oauth2/token`
The following OAuth key/value pair parameters:
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destination-partners.html)
**Cisco AppDynamics documentation:**
[AWS events ingestion](https://docs.appdynamics.com/display/CLOUD/AWS+Events+Ingestion)
**Commonly used API operations:**
Not applicable
**Additional information:**
Choosing **Cisco AppDynamics** from the **Partner destinations** drop-down menu prefills the necessary OAuth information, including the header and body key/value pairs required for API calls.
For additional information, see [AWS events ingestion](https://docs.appdynamics.com/display/CLOUD/AWS+Events+Ingestion) in the *Cisco AppDynamics* documentation.
## Confluent
**API destination invocation endpoint URL:**
Typically the following format:
`https://random-id.region.aws.confluent.cloud:443/kafka/v3/clusters/cluster-id/topics/topic-name/records`
For more information, see [Find the REST endpoint address and cluster ID](https://docs.confluent.io/cloud/current/kafka-rest/krest-qs.html#step-1-find-the-rest-endpoint-address-and-cluster-id) in the Confluent documentation.
**Supported authorization types:**
Basic
**Additional authorization parameters required:**
Not applicable
**Confluent documentation:**
[Produce Records](https://docs.confluent.io/cloud/current/api.html#tag/Records-(v3)/operation/produceRecord)
[Confluent REST Proxy for Apache Kafka](https://docs.confluent.io/platform/current/kafka-rest/api.html#records-v3)
**Commonly used API operations:**
`POST`
**Additional information:**
To transform the event data into a message that the endpoint can process, create a target [input transformer](eb-transform-target-input.md).
+ To generate a record without specifying a Kafka partitioning key, use the following template for your input transformer. No input path is required.
```
{
"value":{
"type":"JSON",
"data":aws.events.event.json
},
}
```
+ To generate a record using an event data field as the Kafka partitioning key, follow the input path and template example below. This example defines the input path for the `orderId` field, and then specifies that field as the partition key.
First, define the input path for the event data field:
```
{
"orderId":"$.detail.orderId"
}
```
Then, use the input transformer template to specify the data field as the partition key:
```
{
"value":{
"type":"JSON",
"data":aws.events.event.json
},
"key":{
"data":"",
"type":"STRING"
}
}
```
## Coralogix
**API destination invocation endpoint URL**
For a full list of endpoints, see [Coralogix API Reference](https://coralogix.com/docs/log-query-simply-retrieve-data/).
**Supported authorization types**
API Key
**Additional authorization parameters required**
Header `"x-amz-event-bridge-access-key"`, the value is the Coralogix API Key
**Coralogix documentation**
[Amazon EventBridge authentication](https://coralogix.com/docs/amazon-eventbridge/)
**Commonly used API operations**
US: https://ingress.coralogix.us/aws/event-bridge
Singapore: https://ingress.coralogixsg.com/aws/event-bridge
Ireland: https://ingress.coralogix.com/aws/event-bridge
Stockholm: https://ingress.eu2.coralogix.com/aws/event-bridge
India: https://ingress.coralogix.in/aws/event-bridge
**Additional information**
The events are stored as log entries with `applicationName=[AWS Account]` and `subsystemName=[event.source]`.
## Datadog
**API destination invocation endpoint URL**
For a full list of endpoints, see [Datadog API Reference](https://docs.datadoghq.com/api/latest/).
**Supported authorization types**
API Key
**Additional authorization parameters required**
None
**Datadog documentation**
[Authentication](https://docs.datadoghq.com/api/latest/authentication/)
**Commonly used API operations**
POST https://api.datadoghq.com/api/v1/events
POST https://http-intake.logs.datadoghq.com/v1/input
**Additional information**
Endpoint URLs differ depending on the location of your Datadog organization. For the correct URL for your organization, see [documentation](https://docs.datadoghq.com/api/latest/).
## Dynatrace
**API destination invocation endpoint URL:**
+ Logs: https://*environment-id*.live.dynatrace.com/api/v2/logs/ingest
+ Davis events: https://*environment-id*.live.dynatrace.com/platform/ingest/v1/events
+ SDLC events: https://*environment-id*.live.dynatrace.com/platform/ingest/v1/events.sdlc
+ Security events: https://*environment-id*.live.dynatrace.com/platform/ingest/v1/events.security
**Supported authorization types:**
API Key
**Additional authorization parameters required:**
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destination-partners.html)
**Dynatrace documentation:**
+ [Log ingestion](https://docs.dynatrace.com/docs/observe-and-explore/logs/lma-log-ingestion)
+ [How to ingest data (events)](https://docs.dynatrace.com/docs/platform/openpipeline/getting-started/how-to-ingestion)
+ [Ingest Amazon ECR vulnerability findings and scan events](https://docs.dynatrace.com/docs/platform-modules/application-security/security-events-ingest/ingest-aws-ecr-data)
**Commonly used API operations:**
POST
**Additional information:**
Each endpoint type has its token scope, which is required for successful authentication. For more information, see [Ingestion APIs](https://docs.dynatrace.com/docs/platform/openpipeline/reference/api-ingestion-reference) in the Dynatrace documentation.
## Freshworks
**API destination invocation endpoint URL**
For a list of endpoints, see [https://developers.freshworks.com/documentation/](https://developers.freshworks.com/documentation/)
**Supported authorization types**
Basic, API Key
**Additional authorization parameters required**
Not applicable
**Freshworks documentation**
[Authentication](https://developers.freshdesk.com/api/#authentication)
**Commonly used API operations**
https://developers.freshdesk.com/api/\$1create\$1ticket
https://developers.freshdesk.com/api/\$1update\$1ticket
https://developer.freshsales.io/api/\$1create\$1lead
https://developer.freshsales.io/api/\$1update\$1lead
**Additional information**
None
## MongoDB
**API destination invocation endpoint URL**
https://data.mongodb-api.com/app/*App ID*/endpoint/
**Supported authorization types**
API Key
Email/Password
Custom JWT Authentication
**Additional authorization parameters required**
None
**MongoDB documentation**
[Atlas Data API](https://www.mongodb.com/docs/atlas/app-services/data-api/)
[Endpoints](https://www.mongodb.com/docs/atlas/app-services/data-api/generated-endpoints/#endpoints)
[Custom HTTPS Endpoints](https://www.mongodb.com/docs/atlas/app-services/data-api/custom-endpoints/)
[Authentication](https://www.mongodb.com/docs/atlas/app-services/data-api/generated-endpoints/#authentication)
**Commonly used API operations**
None
**Additional information**
None
## Momento
**API destination invocation endpoint URL:**
https://api.cache.*region*.prod.a.momentohq.com/cache/*cacheName*
https://api.cache.*region*.prod.a.momentohq.com/topics/*cacheName*/*topicName*
**Supported authorization types:**
API Key
**Additional authorization parameters required:**
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destination-partners.html)
**Momento documentation:**
[Momento \$1 Amazon EventBridge](https://docs.momentohq.com/cache/integrations/amazon-eventbridge)
[Using the Momento Topics API](https://docs.momentohq.com/topics/develop/api-reference)
[API reference for Momento Cache](https://docs.momentohq.com/cache/develop/api-reference)
**Commonly used API operations:**
For caches: `PUT`, `DELETE`
For topics: `POST`
**Additional information:**
When updating or deleting a cache, include the following query string parameters in the configuration of your rule target:
+ The key you want to update in your Momento cache
+ The Time-To-Live (TTL) for the cache item
For example, if your input event included a `details` field with those values:
`key: $.details.key ttl_seconds: $.details.ttl_seconds`
## New Relic
**API destination invocation endpoint URL**
For more information, see [Our EU and US region data centers](https://docs.newrelic.com/docs/using-new-relic/welcome-new-relic/get-started/our-eu-us-region-data-centers/).
**Events**
**US–** https://insights-collector.newrelic.com/v1/accounts/*YOUR\$1NEW\$1RELIC\$1ACCOUNT\$1ID*/events
**EU–** https://insights-collector.eu01.nr-data.net/v1/accounts/*YOUR\$1NEW\$1RELIC\$1ACCOUNT\$1ID*/events
**Metrics**
**US–** https://metric-api.newrelic.com/metric/v1
**EU–** https://metric-api.eu.newrelic.com/metric/v1
**Logs**
**US–** https://log-api.newrelic.com/log/v1
**EU–** https://log-api.eu.newrelic.com/log/v1
**Traces**
**US–** https://trace-api.newrelic.com/trace/v1
**EU–** https://trace-api.eu.newrelic.com/trace/v1
**Supported authorization types**
API Key
**New Relic documentation**
[Metric API](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/ingest-apis/report-metrics-metric-api/)
[Event API](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/ingest-apis/introduction-event-api/)
[Log API](https://docs.newrelic.com/docs/logs/log-management/log-api/introduction-log-api/)
[Trace API](https://docs.newrelic.com/docs/understand-dependencies/distributed-tracing/trace-api/introduction-trace-api/)
**Commonly used API operations**
[Metric API](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/ingest-apis/report-metrics-metric-api/)
[Event API](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/ingest-apis/introduction-event-api/)
[Log API](https://docs.newrelic.com/docs/logs/log-management/log-api/introduction-log-api/)
[Trace API](https://docs.newrelic.com/docs/understand-dependencies/distributed-tracing/trace-api/introduction-trace-api/)
**Additional information**
[Metric API limits](https://docs.newrelic.com/docs/telemetry-data-platform/get-data/apis/metric-api-limits-restricted-attributes/)
[Event API limits](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/ingest-apis/introduction-event-api/#limits)
[Log API limits](https://docs.newrelic.com/docs/logs/log-management/log-api/introduction-log-api/#limits)
[Trace API limits](https://docs.newrelic.com/docs/understand-dependencies/distributed-tracing/trace-api/trace-api-general-requirements-limits/)
## Operata
**API destination invocation endpoint URL:**
https://api.operata.io/v2/aws/events/contact-record
**Supported authorization types:**
Basic
**Additional authorization parameters required:**
None
**Operata documentation:**
[How do I create, view, change and revoke API Tokens?](https://help.operata.com/en/articles/5542797-how-do-i-create-view-change-and-revoke-api-tokens)
[Operata AWS Integration using Amazon EventBridge Scheduler Pipes](https://docs.operata.com/docs/aws-integration)
**Commonly used API operations:**
`POST https://api.operata.io/v2/aws/events/contact-record`
**Additional information:**
The `username` is the Operata Group ID and the password is your API token.
## Salesforce
**API destination invocation endpoint URL**
**Sobject–** https:// *myDomainName*.my.salesforce.com/services/data/*versionNumber*/sobjects /*SobjectEndpoint*/\$1
**Custom platform events–** https://*myDomainName*.my.salesforce.com/services/data /*versionNumber*/sobjects/*customPlatformEndpoint*/\$1
For a full list of endpoints, see [Salesforce API Reference](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_list.htm)
**Supported authorization types**
OAuth client credentials
OAUTH tokens are refreshed when a 401 or 407 response is returned.
**Additional authorization parameters required**
[Salesforce Connected App](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_oauth_and_connected_apps.htm) Client Id and Client Secret.
One of the following authorization endpoints:
+ **Production–** https://*MyDomainName*.my.salesforce.com./services/oauth2/token
+ **Sandbox without enhanced domains–** https://*MyDomainName*--* SandboxName*.my. salesforce.com/services /oauth2/token
+ **Sandbox with enhanced domains–** https://*MyDomainName*--* SandboxName*.sandbox.my.salesforce.com/services/oauth2/token
The following key/value pair:
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/eventbridge/latest/userguide/eb-api-destination-partners.html)
**Salesforce documentation**
[REST API Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_what_is_rest_api.htm)
**Commonly used API operations**
[Working with Object Metadata](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/using_resources_working_with_object_metadata.htm)
[Working with Records](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/using_resources_working_with_records.htm)
**Additional information**
For a tutorial explaining how to use the EventBridge console to create a connection to Salesforce, an API Destination, and a rule to route information to Salesforce, see [Tutorial: Send events to Salesforce from Amazon EventBridge](eb-tutorial-salesforce.md).
## Slack
**API destination invocation endpoint URL**
For a list of endpoints and other resources, see [Using the Slack Web API](https://api.slack.com/web)
**Supported authorization types**
OAuth 2.0
OAUTH tokens are refreshed when a 401 or 407 response is returned.
When you create a Slack application and install it to your workspace, an OAuth bearer token will be created on your behalf to be used for authenticating calls by your API destination connection.
**Additional authorization parameters required**
Not applicable
**Slack documentation**
[Basic app setup](https://api.slack.com/authentication/basics)
[Installing with OAuth](https://api.slack.com/authentication/oauth-v2)
[Retrieving messages](https://api.slack.com/messaging/retrieving)
[Sending messages](https://api.slack.com/messaging/sending)
[Sending messages using Incoming Webhooks](https://api.slack.com/messaging/webhooks)
**Commonly used API operations**
https://slack.com/api/chat.postMessage
**Additional information**
When configuring your EventBridge rule there are two configurations to highlight:
+ Include a header parameter that defines the content type as “application/json;charset=utf-8”.
+ Use an input transformer to map the input event to the expected output for the Slack API, namely ensure that the payload sent to the Slack API has “channel” and “text” key/value pairs.
## Shopify
**API destination invocation endpoint URL**
For a list of endpoints and other resouces and methods, see [Endpoints and requests](https://shopify.dev/api/admin-rest#endpoints)
**Supported authorization types**
OAuth, API Key
OAUTH tokens are refreshed when a 401 or 407 response is returned.
**Additional authorization parameters required**
Not applicable
**Shopify documentation**
[Authentication and authorization overview](https://shopify.dev/apps/auth)
**Commonly used API operations**
POST - /admin/api/2022-01/products.json
GET - admin/api/2022-01/products/\$1product\$1id\$1.json
PUT - admin/api/2022-01/products/\$1product\$1id\$1.json
DELETE - admin/api/2022-01/products/\$1product\$1id\$1.json
**Additional information**
[Create an app](https://shopify.dev/apps/getting-started/create)
[Amazon EventBridge webhook delivery](https://shopify.dev/apps/webhooks/configuration/eventbridge)
[Access tokens for custom apps in the Shopify admin](https://shopify.dev/apps/auth/admin-app-access-tokens)
[Product](https://shopify.dev/api/admin-rest/2021-10/resources/product#top)
[Shopify Admin API](https://shopify.dev/api/admin)
## Splunk
**API destination invocation endpoint URL**
https://*SPLUNK\$1HEC\$1ENDPOINT*:*optional\$1port*/services/collector/raw
**Supported authorization types**
Basic, API Key
**Additional authorization parameters required**
None
**Splunk documentation**
For both authorization types, you need an HEC token ID. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://help.splunk.com/en/data-management/collect-http-event-data/use-hec-in-splunk-cloud-platform/set-up-and-use-http-event-collector-in-splunk-web).
**Commonly used API operations**
POST https://*SPLUNK\$1HEC\$1ENDPOINT*:*optional\$1port*/services/collector/raw
**Additional information**
API Key – When configuring the endpoint for EventBridge, the API key name is “Authorization” and value is the Splunk HEC token ID.
Basic (Username/Password) – When configuring the endpoint for EventBridge, the username is “Splunk” and the password is the Splunk HEC token ID.
## Sumo Logic
**API destination invocation endpoint URL**
HTTP Log and Metric Source endpoint URLs will be different for every user. For more information, see [ HTTP Logs and Metrics Source](https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/HTTP-Source).
**Supported authorization types**
Sumo Logic doesn’t require authentication on their HTTP Sources because there’s a unique key baked into the URL. For this reason, you should make sure to treat that URL as a secret.
When you configure the EventBridge API destination, an authorization type is required. To meet this requirement, select API Key and give it a key name of “dummy-key” and a key value of “dummy-value”.
**Additional authorization parameters required**
Not applicable
**Sumo Logic documentation**
Sumo Logic has already built hosted sources to collect logs and metrics from many AWS services and you can use the information on their website to work with those sources. For more information, see [Amazon Web Services](https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/Amazon-Web-Services).
If you’re generating custom events from an application and want to send them to Sumo Logic as either logs or metrics, then use EventBridge API Destinations and Sumo Logic HTTP Log and Metric Source endpoints.
+ To sign up and create a free Sumo Logic instance, see [Start your free trial today](https://www.sumologic.com/sign-up/).
+ For more information about using Sumo Logic, see [ HTTP Logs and Metrics Source](https://help.sumologic.com/03Send-Data/Sources/02Sources-for-Hosted-Collectors/HTTP-Source).
**Commonly used API operations**
POST https://endpoint4.collection.us2.sumologic.com/receiver/v1/http/*UNIQUE\$1ID\$1PER\$1COLLECTOR*
**Additional information**
None
## TriggerMesh
**API destination invocation endpoint URL**
Use the information in the [Event Source for HTTP](https://docs.triggermesh.io/concepts/sources) topic to formulate the endpoint URL. An endpoint URL includes the event source name and user namespace in the following format:
https://*source-name*.*user-namespace*.cloud.triggermesh.io
Include the Basic authorization parameters in the request to the endpoint.
**Supported authorization types**
Basic
**Additional authorization parameters required**
None
**TriggerMesh documentation**
[Event Source for HTTP](https://docs.triggermesh.io/concepts/sources)
**Commonly used API operations**
Not applicable
**Additional information**
None
## Zendesk
**API destination invocation endpoint URL**
https://developer.zendesk.com/rest\$1api/docs/support/tickets
**Supported authorization types**
Basic, API Key
**Additional authorization parameters required**
None
**Zendesk documentation**
[Security and Authentication](https://developer.zendesk.com/rest_api/docs/support/introduction#security-and-authentication)
**Commonly used API operations**
POST https://*your\$1Zendesk\$1subdomain*/api/v2/tickets
**Additional information**
API requests EventBridge makes count against your Zendesk API limits. For information about Zendesk limits for your plan, see [Usage limits](https://developer.zendesk.com/rest_api/docs/support/usage_limits).
To better safeguard your account and data, we recommend using an API key rather than basic sign-in credentials authentication.