Skip to main content
Track all changes, improvements, and updates to the Promptwatch API v2.

​
October 27, 2026

Pinned point on monitors
  • POST /api/v2/monitors accepts latitude, longitude, locationAccuracy (20, 50, 100, 500, 1000 or 5000 meters, default 50) and locationName to pin the monitor to a point. ChatGPT, Google AI Overviews and Google AI Mode use the point; other models keep using the country, state and city. Pinning needs the Local GEO/SEO Targeting feature (Business, Agency Scale and Enterprise plans), otherwise the request returns 403 MONITOR_GEO_COORDINATES_NOT_ALLOWED. Sending only one of latitude and longitude returns 400 MONITOR_INVALID_COORDINATES.
  • Monitor responses include the four fields, null when no point is pinned. The MCP monitor tools take and return the same fields.
  • The point is fixed after creation like the rest of the location: a different value on PUT /api/v2/monitors/{id} returns 400 MONITOR_LOCATION_LOCKED.
Brand book
  • GET /api/v2/brand-book returns the project’s brand book: name, website, aliases, language, country, descriptions, industry, key features, and analysis instructions.
  • PATCH /api/v2/brand-book updates any of those fields. Leave a field out to keep its current value. industry: null means Other. An empty analysisInstructions clears it. Renaming the brand also changes the project slug, which the response includes.
  • languageCode, countryCode, and industry accept the same values as the brand book page.
  • A project key can call both routes. An organization key must send X-Project-Id.

​
October 22, 2026

Site audit actions
  • Unified actions gain the SITE_AUDIT type. data carries check, runId, affectedUrls, newUrls, fixedUrls and urlsChecked. Drill into the URLs with GET /api/v2/site-audit/issues?runId={data.runId}&issues={data.check}.
  • GET /api/v2/actions filtered by type=SITE_AUDIT also returns existing WEBSITE_HEALTH and WEBSITE_PERFORMANCE actions. New actions are no longer created with those two types.

​
October 19, 2026

Monitor language and location are fixed after creation
  • PUT /api/v2/monitors/{id} no longer changes languageCode, countryCode, stateCode, or cityCode. A different value returns 400 MONITOR_LOCATION_LOCKED. Repeating the stored value still succeeds, so an update that resends the monitor keeps working. Create a new monitor to track a different language or location.

​
October 13, 2026

Site audit insights
  • GET /api/v2/site-audit/runs/latest returns the newest finished run (COMPLETED or PARTIAL). An in-flight run does not hide it.
  • GET /api/v2/site-audit/issues lists affected URLs, errors first. Filter with issues, severity or search.
  • GET /api/v2/site-audit/links?kind=orphans|brokenLinks|coverageGaps|navOnly lists link findings. truncated means the stored list hit its cap. The broken-link cursor is opaque.
  • GET /api/v2/site-audit/content?kind=thin|duplicates|stale|changed|duplicateTitles lists content findings. staleDays applies to kind=stale.
  • GET /api/v2/site-audit/profile returns the link profile, content profile and slowest pages together.
  • GET /api/v2/site-audit/url-history?url= returns one URL’s checks across runs, newest first.
  • runId is optional on issues, failing URLs, links, content and profile. Omit it to read the latest finished run. Every response echoes runId.
  • Run list and run detail now include issue totals by severity. Run detail also includes per-check summaries, response-time averages and recheckPending.
  • GET /api/v2/site-health is deprecated. Use GET /api/v2/site-audit/issues for the current checks. crawlHealthScore on sitemap progress is crawl coverage, not the site audit health score.

​
October 5, 2026

Date range limit
  • REST v2 and MCP date windows can now span 92 inclusive UTC days (previously 90), so a request can cover three full calendar months. Ranges longer than 92 days still return 400 DATE_RANGE_TOO_LARGE.

​
September 18, 2026

Search Insights (Google Search Console and Bing Webmaster)
  • GET /api/v2/search-insights/google/pages — Google clicks, impressions, and position per pathname (period=7d|30d). Paginated (page, size, default 50, max 100); response is { data, total, page, size, totalPages }.
  • GET /api/v2/search-insights/google/trend — daily Google clicks and impressions (startDate/endDate, default last 30 days, max 90)
  • GET /api/v2/search-insights/bing/pages — Bing clicks, impressions, and position per pathname (period=7d|30d). Same pagination as Google pages.
  • GET /api/v2/search-insights/bing/trend — daily Bing clicks and impressions (startDate/endDate, default last 30 days, max 90)
Requires the matching integration to be connected in the dashboard. Google uses the requested calendar window; Bing uses complete Sat–Fri weeks, so the two will not always cover the same days. An unconnected engine returns zeros or empty rows.

​
September 16, 2026

Organization usage
  • GET /api/v2/usage returns organization usage and effective limits (plan, custom overrides, and add-ons), plus a per-project breakdown of countable features including project caps (active prompts, prompt responses, analytics events, crawler logs, content generations, crawled pages, knowledge base items). Requires an organization-level API key; X-Project-Id is not required. Project-level keys receive 403 USAGE_ORG_FORBIDDEN.

​
September 15, 2026

Project events for time-series annotations
  • GET /api/v2/events returns project events grouped by UTC day (date + items) in a startDate/endDate window. Item types are action, prompts_created, and prompts_deleted. Join on date with visibility or sentiment time series. Optional filters: llmMonitorId, promptId. page/size paginate completed actions (default 200, max 200); response includes total, page, size, totalPages.
Site audit endpoints
  • GET /api/v2/site-audit/runs, GET /api/v2/site-audit/runs/{id} and GET /api/v2/site-audit/failing-urls: audit runs with their health score and coverage counts, per-check issue counts with new/fixed deltas against the previous run, and the URLs a run could not fetch. All three are keyset-paginated: pass the returned nextCursor back as cursor. They return 402 SITE_AUDIT_PLAN_REQUIRED when site audits are not part of your plan.

​
August 26, 2026

Featured image is a separate field
  • GET /api/v2/content and GET /api/v2/content/{id} now include featuredImageUrl. The generated featured image is no longer embedded in content markdown. Compose the image yourself if you previously parsed it out of the body.

​
July 29, 2026

competitorMentions deprecated on responses
  • GET /api/v2/responses and GET /api/v2/responses/{id}: competitorMentions is deprecated. It is still present and required, and is now derived from the same brand mentions that back brandMentions. Read brandMentions and keep the entries whose relation is DIRECT_COMPETITOR. brandMentions additionally carries each brand’s domain, visibility score, position and sentiment. competitorMentions will be removed in a future version.

​
April 21, 2026

Crawler activity trend default
  • GET /api/v2/analytics/crawlers/trend: if the crawlers query parameter is omitted, the server now queries all known AI crawler types (the full allowed set) instead of returning an empty time series. Pass crawlers when you need to limit results to a subset.

​
January 19, 2026

Documentation Launch
  • Initial public API documentation release
  • Comprehensive endpoint documentation
  • Interactive API reference
  • Getting started guides
  • Rate limits and quota information
Last updated: September 18, 2026