Ansvisor Docs

Trigger a tracking run

POST /api/tracking/start
Content-Type: application/json
Authorization: Bearer <SUPABASE_JWT>

{
  "brandId": "uuid",
  "platforms": ["chatgpt", "gemini", "perplexity"],
  "models": ["gemini-2.5-flash"]
}

Enqueues a tracking job. Returns:

{
  "success": true,
  "jobId": "job-uuid"
}

Poll job status

GET /api/tracking/job/{jobId}
Authorization: Bearer <SUPABASE_JWT>

Returns:

{
  "status": "active",
  "progress": { "phase": "querying-platforms", "completed": 12, "total": 30 },
  "result": null,
  "failedReason": null
}

status values: waiting, active, completed, failed, cancelled.

Internal cron endpoint

The web app’s cron route (/api/cron/daily-tracking) calls the server’s internal endpoint with a shared secret:

POST /cron/daily-tracking
Authorization: Bearer <CRON_SECRET>

This loops over every brand in the org, picks brands due for refresh based on brand_platforms.check_frequency, and enqueues tracking jobs for them.

Vercel Cron triggers /api/cron/daily-tracking on a schedule defined in web/vercel.json. To run the same flow manually for testing, hit the server endpoint directly with the cron secret.

Latest results

For UI rendering, prefer the optimized RPC:

POST /rest/v1/rpc/get_latest_prompt_results
Content-Type: application/json
Authorization: Bearer <SUPABASE_JWT>

{
  "p_brand_id": "uuid",
  "p_platform": "chatgpt"  // optional
}

Returns the most recent prompt_results row per (prompt_id, platform) — much cheaper than SELECT … ORDER BY created_at DESC LIMIT 1 per prompt in app code.

Continue: Webhooks

Outbound webhooks for content briefs and lifecycle events.

API Reference

Tracking

Trigger a tracking run

Poll job status

Internal cron endpoint

Latest results

Continue: Webhooks

​Trigger a tracking run

​Poll job status

​Internal cron endpoint

​Latest results

Continue: Webhooks

Trigger a tracking run

Poll job status

Internal cron endpoint

Latest results