---
title: "Get collection info"
method: GET
path: "/collections/{collection_name}"
tags: ["Collections"]
---

# Get collection info

`GET /collections/{collection_name}`

Get detailed information about a specific collection, including vector configuration, index type and parameters, point count, and collection status.

## Path parameters

- `collection_name` string, required

## Response `200`

Collection information

- object
  - `usage` object
    - `hardware` object, nullable — Hardware resource counters for the operation, including CPU, payload I/O, payload index I/O, and vector I/O metrics.
  - `time` number, double — Time spent to process this request, in seconds.
  - `status` string — Operation status.
  - `result` object
    - `status` string — The health status of the collection. Possible values are `Green`, `Yellow`, and `Red`.
    - `optimizer_status` object — Status of the collection optimizer.
      - `ok` boolean — Whether the optimizer is functioning normally.
      - `error` string, nullable — Error message if the optimizer has encountered a problem, or null if healthy.
    - `warnings` string[] — Any warnings about the collection state.
    - `indexed_vectors_count` integer, nullable — Number of vectors that have been indexed, or null if indexing has not started.
    - `points_count` integer — Total number of points stored in the collection.
    - `segments_count` integer — Number of storage segments in the collection.
    - `config` object — The collection configuration.
      - `params` object — Core collection parameters.
        - `vectors` object, nullable — Named vector configurations, or null if using default unnamed vectors.
        - `shard_number` integer — Number of shards for the collection.
        - `replication_factor` integer, nullable — Number of replicas for each shard, or null if not configured.
        - `write_consistency_factor` integer, nullable — Minimum number of replicas that must confirm a write, or null if not configured.
        - `on_disk_payload` boolean — Whether payload data is stored on disk rather than in memory.
      - `hnsw_config` object — HNSW index configuration.
        - `m` integer, nullable — Number of bidirectional links per element in the HNSW graph, or null for default.
        - `ef_construct` integer, nullable — Size of the dynamic candidate list during index construction, or null for default.
        - `full_scan_threshold` integer, nullable — Minimum collection size before HNSW indexing is used instead of full scan, or null for default.
        - `max_indexing_threads` integer, nullable — Maximum number of threads used for indexing, or null for default.
        - `on_disk` boolean, nullable — Whether the HNSW index is stored on disk, or null for default.
        - `payload_m` integer, nullable — Number of bidirectional links for payload index, or null for default.
      - `optimizer_config` object — Optimizer configuration for indexing and vacuum behavior.
      - `wal_config` object — Write-ahead log configuration.
    - `payload_schema` object — Schema of indexed payload fields.
    - `name_ext` string — The collection name.
    - `health_status_ext` string — Extended health status string.
    - `vectors_count` integer — Total number of vectors in the collection.
    - `index_type_ext` string — The index type used by the collection.

---

[API](https://skmtc.net/actiancorp/apis/actian-vectorai-db-collections-api.md) · [All operations](https://skmtc.net/actiancorp/apis/actian-vectorai-db-collections-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/actiancorp/actian-vectorai-db-collections-api/versions/af01467a9a12/schema)