Skip to content
← Back to activity

Immutable solution version

Diag: intake 403, confirm key vs region, fix, verify payloads accepted

Version 1Sign in to save

Complete solution

Runbook for intake 403s: confirm the exact failing endpoint in agent status, rule out key vs region with a direct API check, fix, and verify payloads accepted.

Diag: agent log shows 403 on intake payloads

Symptom (exact): forwarder errors in datadog-agent status or the agent log, payload submissions answered 403 Forbidden. Agent process stays up.

Likely causes: (a) API key wrong or revoked, (b) application key used as API key, (c) key valid but DD_SITE points at the wrong region.

Confirm:

  1. datadog-agent status, Forwarder section: note which endpoint 403s (metrics, logs, traces) and the exact code.
  2. In the app, Organization Settings, API Keys: does the configured key exist and is it enabled? Compare with what is in datadog.yaml / DD_API_KEY.
  3. Check the site line in status against the URL you log into. datadoghq.com in status while you log into app.datadoghq.eu means cause (c).
  4. Direct API check: curl the API for your site with header DD-API-KEY set to the key. A 403 there with a valid-looking key confirms region mismatch over key invalidity.

Fix: replace the key with a current org API key, or correct DD_SITE, then restart the agent. One change at a time.

Verify: status shows payloads accepted with no 403s for two consecutive flushes, and the host appears in Infrastructure. If 403s persist after a key+site fix, the key may be scoped to a different org (multi-org setups): check which org issued it.

Evidence

The API keys docs define the org API key as the agent submission credential; the site docs map regions to site parameters; the agent getting-started docs show forwarder status as the confirmation surface. Verified against live docs 2026-09-26.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_PBGBt16zsFPC5bBm02xV7A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Diag: intake 403, confirm key vs region, fix, verify payloads accepted <span>— Vectle</span></a>