Introduction

Release Notes

📢 Deprecations:

FeatureSunset DateReplacement
Old Dynamic Tags ExperienceJune 20, 2025New Dynamic Tags Experience
Add Assets POST /datasets/:dataset_id/assetsJuly 7, 2025Ingestion via Public URL or S3 Bucket POST /api/v1/ingestion/assets
POST /api/v1/ingestion/buckets
Update Metadata PUT /datasets/:dataset_id/assets-metadataJuly 7, 2025Add/Update Metadata POST /api/v1/ingestion/metadata
Encoder: multimodal (Create/Search Dataset)July 7, 2025Use multimodal-tx-large2 or multimodal-tx-large3
Legacy API Domain (app.coactive.ai)December 31, 2025Newly published APIs will be on api.coactive.ai and will gradually replace all existing endpoints on our legacy domain

June 16, 2025

  • New Dynamic Tags Experience (Beta): We have a new dynamic tags experience within the Coactive UI that we are excited to share with our users. If you would like to try this out, reach out to Coactive support.
  • Old Dynamic Tags Tables will no longer be accessible (Deprecation Notice): We are deprecating the old Dynamic Tags tables category_*. You will no longer be able to access these tables after June 20th, please recreate your tags on the New Dynamic Tags experience.
  • Ingestion Observability (Beta): Track the status of ingested assets directly in the dataset view or via API, including error reporting, processing, and ready to search states. For full details, see the Ingestion Observability Guide.
  • SQL UI Row Limit: The SQL tab in the platform now displays a maximum of 10,000 rows in the UI. If your result set exceeds this limit, you can still:
    • Use SELECT COUNT(*) to retrieve the full row count
    • Download the full result set as a CSV(s)
    Note: Users will see the total number of results, but will only be able to browse the first 10,000 rows within the UI.

June 2, 2025

  • Connections API (Beta): Introduced endpoints to securely connect external cloud storage to Coactive for automated ingestion workflows. The API currently supports S3 buckets and allows programmatic creation, testing, updating, and deletion of connections. Future support for additional cloud storage providers is planned.

    For more details, see the Connections API reference and the Cloud Storage Access guide.

  • Bucket-Based Ingestion: Added a new endpoint (POST /api/v1/ingestion/buckets) that scans a specified path within a connected S3 bucket and ingests all discovered assets. Ideal for bulk ingestion workflows that do not require individually listing files.

May 23, 2025

  • System Credentials API (Beta): Added support for long-lived, programmatic credentials not tied to specific users. These credentials can be scoped to datasets or system-wide roles and are ideal for backend integrations.

    See the System Credentials reference for more information.

  • User Management API (Beta): Introduced endpoints to invite, list, update, and remove users, as well as manage assignable roles. Role scoping supports system- and dataset-level access control.

    Learn more in the User Management reference and User Roles & RBAC guide.

March 13, 2025

  • Ingestion API (v1): Released a modern ingestion pipeline that supports asset uploads via public URLs, S3 buckets, and batch asset lists. A separate endpoint also allows metadata to be applied post-upload. These new APIs replace earlier dataset-scoped routes and improve ingestion scalability, performance, and compatibility with newer ML workflows.

  • As part of this release, we’ve begun deprecating the legacy multimodal encoder previously used in dataset creation and search. Customers should migrate to multimodal-tx-large2 or multimodal-tx-large3, which offer improved performance and semantic accuracy.

    See the Ingestion API reference and Update Metadata documentation.

    For compatibility information, see the Accepted Media Formats guide.

Febuary 20, 2025

  • Coactive is transitioning to a unified and versioned API domain structure:
    • New API domain: https://api.coactive.ai
    • Legacy API domain: https://app.coactive.ai
  • All new APIs — including ingestion, user management, connections, and system credentials — are hosted on the new domain and should be used for all future integrations. The legacy domain for existing APIs will remain available until December 31, 2025, but it will not receive further updates or new features.
    • Action recommended:
      • When reading our API docs, please verify the domain used.
      • Existing Legacy APIs will gradually be placed by newer APIs, please check this page frequently for our newly published APIs