How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Chroma Collections API

Collection management endpoints for creating, listing, retrieving, updating, and deleting collections within a database.

Chroma Collections API is one of 9 APIs that Chroma publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Collection. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against 2 base URLs: https://api.trychroma.com, http://localhost:8000.

5 operations 2 paths 6 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.trychroma.com
Authentication
HTTP Bearer, API Key, HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 3

Chroma Collections API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). An API key is passed in the header as X-Chroma-Token (tokenAuth). It accepts HTTP basic authentication (basicAuth).

  • bearerAuth — Bearer token authentication for Chroma Cloud. Obtain tokens from the Chroma Cloud dashboard.
  • tokenAuth — Static token authentication via the X-Chroma-Token header.
  • basicAuth — HTTP Basic authentication using RFC 7617 with a user:password base64-encoded Authorization header.

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Collections 5

Collection management endpoints for creating, listing, retrieving, updating, and deleting collections within a database.

GET
/api/v2/tenants/{tenantName}/databases/{databaseName}/collections
List collections
listCollections 4 params → 200
POST
/api/v2/tenants/{tenantName}/databases/{databaseName}/collections
Create a collection
createCollection 2 params body → 200409
GET
/api/v2/tenants/{tenantName}/databases/{databaseName}/collections/{collectionId}
Get a collection
getCollection 3 params → 200404
PUT
/api/v2/tenants/{tenantName}/databases/{databaseName}/collections/{collectionId}
Update a collection
updateCollection 3 params body → 200404
DELETE
/api/v2/tenants/{tenantName}/databases/{databaseName}/collections/{collectionId}
Delete a collection
deleteCollection 3 params → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Collection_2 (5 properties), Collection (5 properties), CreateCollectionRequest_2 (3 properties), CreateCollectionRequest (3 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties 1 required
UpdateCollectionRequest
object
2 properties
CreateCollectionRequest
object
3 properties 1 required
Collection
object
5 properties 2 required
CreateCollectionRequest_2
object
3 properties 1 required
Collection_2
object
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

chroma-collections-api-openapi.yml Raw ↑

Other APIs Chroma publishes across the network.

Chroma Python Client
Chroma JavaScript Client
Chroma Databases API
Chroma Records API
Chroma Search API
Chroma System API
Chroma Tenants API
Chroma Query API
Where this information came from

This is an independent, third-party profile of Chroma Collections API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.