> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudgeni.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Authentication

> Authenticate programmatic Cloudgeni API calls with the organization-scoped API key header the backend actually expects.

# Authentication

For programmatic API usage, use the `X-CLOUDGENI-API-KEY` header.

That is the header name the codebase and local project instructions expect. Do not substitute
`Authorization` or `x-api-key` unless you have a different auth surface in front of the API.

## Example

```bash theme={null}
curl --fail --silent --show-error \
  -H "X-CLOUDGENI-API-KEY: $CLOUDGENI_API_KEY" \
  "$CLOUDGENI_API_URL/api/v1/organizations/$CLOUDGENI_ORG_ID"
```

## Notes

* Keep API keys organization-scoped and secret-managed
* Use separate keys for CI and local automation when possible
* Prefer short automation flows over broad permanently shared credentials

## CLI Alternative

If you prefer not to work with raw HTTP, use the [CLI](/cli/overview). It exposes the same general
organization and scan surfaces with JSON output support.