Workspace scoping

Every API key maps to exactly one workspace. Reads and writes never cross workspaces.

Your API key maps to exactly one workspace. The mapping is enforced for every read and every write.

What this means in practice

Lead lookups (/feedback/events, /leads/export, /leads/push) only see leads in your workspace. An unknown lead ID returns 404 lead_not_found, never data from another workspace.
Radar resources you create are visible to your workspace only.
Workspace metadata (tier, credit balance, allowed endpoints) is returned by /account/key-info and /account/credit-usage.

Why this matters for clients

You do not need to pass workspace IDs anywhere in the request: the key is the workspace. If you maintain multiple workspaces (for example one per customer in a reseller setup), use one key per workspace and route requests accordingly on your side.