Authentication | Genlytic Docs

The Genlytic API uses long-lived API keys for authentication. Keys start with gly_live_ and are created in Settings → API.

All API requests require a valid API key. Unauthenticated requests return 401 Unauthorized.

Creating an API key

Go to Settings → API in your Genlytic dashboard
Click + Create API Key
Give it a name (e.g. "Power BI connector")
Select the scopes your integration needs
Copy the key immediately — it is shown only once

Request format

Include the key as a Bearer token on every request:

Authorization: Bearer gly_live_xxxxxxxxxxxxxxxx

Example request

curl https://api.genlytic.app/v1/visibility \
  -H "Authorization: Bearer gly_live_xxxxxxxxxxxxxxxx"

Scopes

Each API key is issued with explicit scopes. Request only the scopes your integration needs.

Scope	Access
`visibility:read`	Read visibility scores and snapshots
`prompts:read`	List prompts and read scan results
`prompts:write`	Create and update prompts
`scans:write`	Trigger manual scans (counts against daily limit)
`optimize:read`	Read actions and briefs
`optimize:write`	Update action status (applied / dismissed)
`agent:read`	Read agent missions, memory, and pending approvals

There is no agent:write scope. Agent actions — including approving tasks — require a Genlytic dashboard session and cannot be performed via the external API.

Plan requirements

API access requires Growth plan or above. Requests from Starter or Pro workspaces return 403 Forbidden.

Error responses

Status	Meaning
`401`	Missing or invalid API key
`403`	Key lacks the required scope, or plan too low
`429`	Rate limit exceeded — see Rate Limits

Next steps

Rate Limits — requests per hour by plan
Endpoints Overview — full API reference
Webhooks — receive events instead of polling