O
Oliver

API Changelog

This page documents all notable changes to the Oliver Chat API. We're committed to maintaining backward compatibility while continually improving our API.

v1.0.0 (Current) - March 11, 2025

Initial Public Release

The first stable release of the Oliver Chat API, featuring comprehensive AI chatbot capabilities with specialized features for financial services.

Features:

  • Core chat API with streaming capabilities
  • RAG (Retrieval Augmented Generation) with permission-based containers
  • Microsoft SSO integration
  • Financial compliance checks (FINRA, SEC)
  • Internet-enabled search via Bing Search API
  • Web browsing capabilities for AI
  • Citation system for sources
  • Image generation
  • User and permission management
  • Supervisor access controls

v0.9.0 (Beta) - February 15, 2025

Beta Release

Final beta release with all major features implemented.

Changes:

  • Added financial compliance checks
  • Enhanced RAG capabilities with better precision
  • Improved streaming performance
  • Enhanced web browsing capabilities with better content extraction
  • Added citation system
  • Performance optimizations across all endpoints

Bug Fixes:

  • Fixed token refreshing in authentication flow
  • Addressed issues with long-running search queries
  • Fixed RAG container permission checks
  • Improved error handling for failed image generation

v0.8.0 (Alpha) - January 10, 2025

Alpha Release

Initial alpha release for selected partners.

Features:

  • Basic chat functionality
  • Preliminary RAG implementation
  • Initial authentication system
  • Basic compliance checking
  • Limited search capabilities

Note: This alpha version has been deprecated and is no longer supported.

API Versioning Policy

We follow semantic versioning (SemVer) for our API:

  • MAJOR version for incompatible API changes (e.g., v1.0.0 to v2.0.0)
  • MINOR version for added functionality in a backward-compatible manner (e.g., v1.0.0 to v1.1.0)
  • PATCH version for backward-compatible bug fixes (e.g., v1.0.0 to v1.0.1)

When we introduce breaking changes, we:

  • Provide at least 6 months notice before deprecating any API version
  • Support at least two major versions simultaneously during transition periods
  • Document migration paths between major versions

Stay Updated

To stay informed about API updates:

Getting Started Guide Back to Overview