Datadog (OAuth)

​

🚀 Quickstart

curl "https://api.nango.dev/proxy/v1/events" \
  -H "Authorization: Bearer <NANGO-SECRET-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>"

import { Nango } from '@nangohq/node';

const nango = new Nango({ secretKey: '<NANGO-SECRET-KEY>' });

const res = await nango.get({
    endpoint: '/v1/events',
    providerConfigKey: '<INTEGRATION-ID>',
    connectionId: '<CONNECTION-ID>'
});

console.log(res.data);

​

📚 Datadog (OAuth) integration guides

• How to register your own Datadog OAuth app Register an OAuth client with Datadog and obtain credentials to connect it to Nango
• How to link your Datadog account Find your Datadog site parameter and connect your account through Nango’s UI

​

🧩 Pre-built syncs & actions for Datadog (OAuth)

​

API gotchas

• Datadog’s OAuth authorize and token endpoints, and its API base URL, are all site-specific — pick the site matching where your users’ Datadog accounts live (for example datadoghq.com for US1, datadoghq.eu for EU1). A token issued on one site won’t work against another site’s API.
• Grant only the scopes your app actually needs when creating your OAuth client — Datadog enforces the principle of least privilege, and any request against a scope you didn’t request returns a 401 even with a valid, unexpired token. See Authorization scopes for OAuth clients for the full list.
• To send data on behalf of a connected user (rather than just reading it), you need a Datadog API key. Call the API Key Creation endpoint with the API_KEYS_WRITE scope — the generated key is only ever shown once, so store it securely.