> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryprofound.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Changelog
> Track API changes, version history, and release notes
## Overview
This changelog tracks all changes, updates, and improvements to the Profound REST API. We document new features, bug fixes, breaking changes, deprecations, and security updates to help you stay informed and plan your integrations accordingly.
The latest API version is `v2` for Agent Analytics report endpoints (`/v2/reports/*`). V1 endpoints remain active, including V1 report endpoints. For more information about API versioning, see the [Introduction](/rest-api/introduction#api-versioning).
## Change Categories
Changes are organized into the following categories:
* **Added** - New endpoints, features, or capabilities
* **Changed** - Modifications to existing endpoints or behavior
* **Deprecated** - Features that will be removed in a future version
* **Removed** - Features that have been removed
* **Fixed** - Bug fixes and corrections
* **Security** - Security improvements and vulnerability patches
* **Breaking** - Changes that require action to maintain compatibility
### Added
* New **beta** `/v2/reports` endpoints — a unified `{ info, data }` request/response shape, accepting names **or** UUIDs in filters, with cursor pagination and a `/stream` (SSE) variant:
* `POST /v2/reports/visibility` - Asset visibility, share of voice, and average position
* `POST /v2/reports/citations` - Domain and page citation counts, share, and rank
* `POST /v2/reports/sentiment` - Per-brand positive/negative sentiment with optional comparison periods
* `POST /v2/reports/query-fanouts` - Search queries an AI generates behind the scenes when answering a prompt
* New **beta** endpoint: `POST /v2/prompts/answers` - Raw per-execution rows (mentions, citations, search queries), with a `/stream` (SSE) variant
### Deprecated
* The V1 report endpoints (`POST /v1/reports/visibility`, `/citations`, `/sentiment`, `/sentiment-v2`, `/query-fanouts`) are being phased out in favor of the V2 equivalents above. They remain active; a sunset date will be announced before removal.
### Added
* New endpoint: [List Agents](/api-reference/agents/list-agents) - List agents available to your organization
* New endpoint: [Get an Agent](/api-reference/agents/get-an-agent) - Retrieve an agent and its schema details
* New endpoint: [Run an Agent](/api-reference/agents/run-an-agent) - Start a new run for an agent
* New endpoint: [Get an Agent Run](/api-reference/agents/get-an-agent-run) - Retrieve the status and result details for an agent run
### Deprecated
* Deprecated raw Agent Analytics endpoints:
* `POST /v1/logs/raw` - Get Logs
* `POST /v1/logs/raw/bots` - Get Bots
* Deprecation started on `2026-04-10`
* API keys created on or after `2026-04-10` can no longer access these endpoints
* Existing API keys created before `2026-04-10` can continue using these endpoints until the sunset date of `2026-06-10`
* Migrate to the V2 aggregated report endpoints instead:
* `POST /v2/reports/bots` for bot traffic reporting
* `POST /v2/reports/referrals` for referral traffic reporting
* For examples using the replacement endpoints, see [Agent Analytics V2](/rest-api/examples/agent-analytics)
### Added
* New `/v2/reports` endpoints with **hourly granularity**, bucketed by UTC hour — see [Agent Analytics V2](/rest-api/examples/agent-analytics)
* `POST /v2/reports/bots` - Bot traffic data at hourly resolution
* `POST /v2/reports/referrals` - Referral traffic data at hourly resolution, including UTM and referrer distinction
* Because V2 uses UTC hour buckets rather than EST day buckets, users in any timezone can now align queries to their own local calendar days
### Added
* New endpoint: Get [Referrals Report](/api-reference/reports/get-referrals-report-v1) - Retrieve referral traffic data from daily aggregated reports
* New endpoint: Get [Bots Report](/api-reference/reports/get-bots-report-v1) - Retrieve bot traffic analytics with metrics for citations, indexing, training, and visit counts
### Changed
* Reorganized example documentation structure under new [Example Requests](/rest-api/examples/example) tab
### Removed
* Legacy examples page
### Added
* New endpoint: [Get Personas](/api-reference/organization/get-personas) - Retrieve all personas associated with your organization
* New endpoint: [Get Category Personas](/api-reference/organization/get-category-personas) - Retrieve all personas associated to the given category
* `persona` dimension to citations, visibility and sentiment reports
* `persona` to the prompt answers
* `model_id` to the prompt answers
* `sentiment_themes` to the prompt answers, deprecating `themes`. `sentiment_themes` returns the theme and its sentiment
### Changed
* Require a non-empty list value when using the `in` or `not_in` filter operator
* `created_at` field is not allowed to be disabled
### Fixed
* Avoid exporting duplicate prompts in the prompt answers.
### Added
* New endpoint: [Get Category Assets](/api-reference/organization/get-category-assets) - Retrieve assets associated with a specific category
* New endpoint: [Get Assets](/api-reference/organization/get-assets) - Retrieve all assets associated with your organization
* `asset_id` dimension in [Query Visibility](/api-reference/reports/query-visibility) and [Query Sentiment](/api-reference/reports/query-sentiment)
### Changed
* Require `hostname`, `path`, `root_domain` and `url` to be included as dimensions when used as filters
### Fixed
* `contains` filter not being applied correctly
* Typo in sentiment metric field name
* **Before:** `ocurrences`
* **After:** `occurrences`
* Filters containing UUID's not being applied correctly
* Incorrect handling of mixed timezone and non-timezone values in `start_date` and `end_date` filters