القائمة
Troubleshoot Datadog API authentication issues (401/403 errors), understand API keys vs app keys, and configure correct regions. Use when hitting auth errors or setting up Datadog API access.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create, inspect, and update Datadog monitors via API - get monitor details by ID or URL, create or update metric/query alerts with thresholds and Slack notifications. Use when setting up alerting, tuning monitors, investigating monitor triggers, or checking monitor group states.
Search and manage Datadog Error Tracking issues via API - find grouped errors by service, resolve/ignore issues. Use when investigating production errors or managing error tracking issue states.
Work with Datadog Incidents API - fetch incidents with enrichment, update incident fields, understand incident data structures. Use when working with incidents or the dd-cli get-incident/update-incident commands.
Create log-based count metrics via API - works with all storage tiers including flex. Use when you need to monitor log patterns but logs are in flex tier (where log monitors don't work).
Search Datadog logs via API - query syntax, storage tiers (indexes, flex, online-archives), pagination. Use when searching logs or using the dd-cli search-logs command.
List and inspect Datadog SLOs via API - view SLI values, error budgets, thresholds, and history. Use when checking SLO compliance, reviewing error budgets, or finding SLOs by tag.
| name | datadog-auth |
| description | Troubleshoot Datadog API authentication issues (401/403 errors), understand API keys vs app keys, and configure correct regions. Use when hitting auth errors or setting up Datadog API access. |
DD-API-KEY — org-scoped API key (32 hex chars)DD-APPLICATION-KEY — application key VALUE (secret; 40 hex chars)us3.datadoghq.com) so the base is https://api.<DD_SITE>.| Item | Example | Use in requests |
|---|---|---|
| API key (value) | aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa (32 hex) | Header DD-API-KEY |
| Application key (value, secret) | bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb (40 hex) | Header DD-APPLICATION-KEY |
| API key ID | xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (UUID) | Not for auth |
| Application key ID | yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy (UUID) | Not for auth |
| Region | API Base |
|---|---|
| US1 | https://api.datadoghq.com |
| US3 | https://api.us3.datadoghq.com |
| US5 | https://api.us5.datadoghq.com |
| EU1 | https://api.datadoghq.eu |
| AP1 | https://api.ap1.datadoghq.com |
| AP2 | https://api.ap2.datadoghq.com |
# Test API key only (no app key needed)
curl -sS -H "DD-API-KEY: $DD_API_KEY" https://api.$DD_SITE/api/v1/validate
# Or use the CLI
dd-cli validate
| HTTP | Symptom | Likely cause | Fix |
|---|---|---|---|
| 401 | Unauthorized | Wrong app key value, wrong site/org, using key ID instead of value | Use the secret value, verify region |
| 403 | scoped app keys not supported | Using a scoped app key | Use an unscoped app key |
| 403 | Generic | Missing permission on owner's role | Adjust role permissions |
dd-cli validatefor site in us3.datadoghq.com datadoghq.com datadoghq.eu; do
code=$(curl -s -o /dev/null -w "%{http_code}" -H "DD-API-KEY: $DD_API_KEY" "https://api.$site/api/v1/validate")
echo "$site -> $code"
done
export DD_APP_KEY="$(printf %s "$DD_APP_KEY" | tr -d '\r\n')"
If you see "This API does not support scoped app keys," use an unscoped app key.