On the Pro and Agency plans you create a key in the dashboard under Account → API & MCP. The key is shown only once; keep it like a password. Access is read-only: no endpoint changes anything on your site or in Glimana.
Authentication and limits
- Header:
Authorization: Bearer glm_… - Requests per minute: Pro 60, Agency 300. Over the limit:
429withRetry-After. - Errors are JSON:
401 invalid_api_key,403 plan_required,404 site_not_found. - Text language: English by default;
?lang=trfor Turkish.
REST
| Endpoint | Returns |
|---|---|
GET /api/v1/sites | Sites, health score, last crawl |
GET /api/v1/sites/{site}/summary | Last 28 days of Search Console (clicks, impressions, CTR, position, change), open issues by severity, measured impact |
GET /api/v1/sites/{site}/tasks?limit=20 | Open tasks in priority order, with why and how |
GET /api/v1/sites/{site}/issues?limit=50 | Open audit issues, example URLs, how to fix |
GET /api/v1/sites/{site}/impacts?limit=30 | 28-day impact results (control group, significance) |
GET /api/v1/sites/{site}/queries?days=28&limit=50 | Search Console queries |
GET /api/v1/sites/{site}/ai-access | AI bot access: robots.txt and live request result per bot |
{site}: the id from the list, or the domain (example.com).
curl -H "Authorization: Bearer glm_…" https://glimana.com/api/v1/sites/example.com/tasks?limit=5
MCP
A Model Context Protocol server (Streamable HTTP, JSON). Add it to clients such as Claude, ChatGPT or Cursor as a custom connector / MCP server:
https://glimana.com/api/mcp Authorization: Bearer glm_… https://glimana.com/api/mcp/glm_… (for clients that cannot send headers; do not share this URL)
Tools: list_sites, get_site_summary, get_priority_tasks, get_open_issues, get_impact_results, get_top_queries, get_ai_bot_access.
Example prompt: "What should I fix on example.com this week?"