HTTP API
The HTTP API drives EdgeComet programmatically. Cache operations are designed for CMS publish hooks, deploy pipelines, and CI integrations: when your content changes, tell EdgeComet, and bots see the new version on their next visit. The Data Explorer endpoints read your bot traffic and Search Console data as JSON or CSV.
Base URL: https://cloud.edgecomet.com
Endpoints
| Endpoint | Purpose |
|---|---|
POST /api/websites/{website}/cache/recache | Queue URLs for re-rendering; existing cache stays live until the render completes |
POST /api/websites/{website}/cache/invalidate | Drop cached entries; the next bot request triggers a fresh render |
GET /api/websites/{website}/data-explorer | List the queryable explorers with their columns, filters, and periods |
POST /api/websites/{website}/data-explorer/{explorerKey}/query | Read a page of rows as JSON |
POST /api/websites/{website}/data-explorer/{explorerKey}/export | Start a CSV export and get a download link |
GET /api/websites/{website}/data-explorer/export/{exportId}/status | Check an export and mint a fresh download link |
The {website} path parameter is the numeric website ID, visible in the dashboard URL.
See also: Data Explorer columns and filters, errors and rate limits, integration recipes.
Authentication
All requests require a bearer token:
Authorization: Bearer eck_xxxxxxxxxxxxxxxxTokens are minted in the dashboard under Settings - API Tokens and use the eck_ prefix. A token carries the website access and role of the user who minted it. Cache endpoints need the manager role or above; Data Explorer endpoints are reads and accept any role, including readonly. Both require the platform module on the website. Tokens do not expire by default; an optional expiry can be set at creation time.
Keep tokens out of source control - configure them as environment variables or secrets in the calling system.