Developers
Analystic's APIs: reports out, clients in, events on change.
Two versioned REST APIs and signed webhooks, authenticated with organization-scoped bearer tokens. The Reporting API runs the same report engine as the app — no separate implementation to drift.
Reporting API
One request, one normalized report.
Ask for a report and a period; get structured JSON with every source's status, per-resource metrics, comparisons, checks and SEO insights.
Request
GET /api/reporting/v1/clients/crm-1057/reports/seo ?period=last28&comparison=previous_periodAuthorization: Bearer YOUR_ANALYSTIC_TOKEN
Response (abridged)
{ "report": "seo", "client": { "name": "Nordvik Studio AB", "external_key": "crm-1057" }, "sources": { "search_console": { "status": "ok" }, … }, "summary": { "search_console": [{ "metrics": { "clicks": { "value": 1193, "comparison": 1291, "change": { "percent": -7.59, "direction": "down" } }, "ctr": { "value": 0.044 } } }] }, "intelligence": { "seo": { "items": [ … ] } }}
Endpoints
What you can build with.
Reporting API
GET a client's (agency) or your site's (company) Overview, SEO, Paid Search, Lead Generation or Ecommerce report for a preset or custom period, with comparisons. Search Console tables page with a cursor.
Automation API
List and look up clients, upsert one by your external_key, or bulk-import up to 500 in one all-or-nothing transaction. Idempotency-Key supported on writes.
Webhooks
client.created, client.updated, client.deactivated, clients.synced, billing.status_changed and webhook.test — signed with HMAC-SHA256 over the timestamp and raw body.
Authentication
Bearer tokens owned by one organization, with explicit scopes: reports:read, clients:read, clients:write, organization:read. Tokens are shown once and can be revoked.
Conventions
Rates are decimals (0.1234), money is { value, currency }, null means unavailable and 0 means a measured zero. Errors are stable JSON with a request ID.
Integrations
n8n workflows, Zapier via Webhooks by Zapier, or your own systems. The OpenAPI 3.1 description imports straight into Postman, Insomnia or a client generator.
Examples
Fictional examples, real shapes.
Create or update a client (Automation API)
curl -X POST https://analystic.dev/api/automation/v1/clients \
-H "Authorization: Bearer YOUR_ANALYSTIC_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: crm-1057-2026-10-05" \
-d '{"external_key":"crm-1057","name":"Nordvik Studio AB","domain":"nordvik.example"}'Verify a webhook signature (Node.js)
// X-Analystic-Signature: v1=HMAC-SHA256(secret, timestamp + "." + rawBody)
const expected = "v1=" + crypto.createHmac("sha256", secret)
.update(`${req.headers["x-analystic-timestamp"]}.${rawBody}`).digest("hex");Reject timestamps older than five minutes and compare in constant time. Deduplicate on the event ID — a manual retry resends the same event.
Limits
Designed for server-to-server use.
Bounded and predictable, so workflows behave the same every run.
Rate limits
Reporting: 30 requests a minute and 2 reports at a time per token. Automation: 120 requests a minute per token.
Bounded responses
Periods up to 366 days, 25 rows per table by default (up to 100), Search Console pages of 25 rows with a cursor.
Strict validation
Unknown or repeated parameters are rejected — a filter is never silently ignored.
The full API reference — every parameter, field and error code — is available to organization admins in Analystic under Automations → API & template docs. The OpenAPI 3.1 description is public: analystic-api-v1.json.
Build on Analystic.
Versioned APIs, scoped tokens and signed events — the same reporting engine as the app.