Skip to main content

​
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 current API version is v1. All endpoints are prefixed with /v1 to ensure compatibility as the API evolves. For more information about API versioning, see the Introduction.

​
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
​
December 2025
v1.4.0

​
Added

  • New endpoint: Get Referrals Report - Retrieve referral traffic data from daily aggregated reports
  • New endpoint: Get Bots Report - Retrieve bot traffic analytics with metrics for citations, indexing, training, and visit counts

​
Changed

​
Removed

  • Legacy examples page
​
December 2025
v1.3.0

​
Added

  • New endpoint: Get Personas - Retrieve all personas associated with your organization
  • New endpoint: 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.
​
November 2025
v1.2.0

​
Added

​
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