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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Qdrant

Qdrant Aliases API

Additional names for existing collections.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 3 operations across 3 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version master.

Requests are made against a single base URL, {protocol}://{hostname}:{port}.

3 operations 3 paths 15 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
master
Server
{protocol}://{hostname}:{port}
Authentication
API Key, HTTP Bearer
Contact
andrey@vasnetsov.com
License
Apache 2.0
Resource Areas
1

Authentication & Security 2

Qdrant Aliases API declares 2 security schemes for authenticating requests. An API key is passed in the header as api-key (api-key). It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated, though some operations may also be called without credentials.

  • api-key — Authorization key, either read-write or read-only

Paths & Operations 3

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

Aliases 3

Additional names for existing collections.

POST
/collections/aliases
Update aliases of the collections
update_aliases 1 param body → default4XX200
GET
/collections/{collection_name}/aliases
List aliases for collection
get_collection_aliases 1 param → default4XX200
GET
/aliases
List collections aliases
get_collections_aliases → default4XX200

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are HardwareUsage (7 properties), ErrorResponse (3 properties), RenameAlias (2 properties), Usage (2 properties). Each schema is shown below with its type and property counts.

ChangeAliasesOperation
object
Operation for performing changes of collection aliases. Alias changes are atomic, meaning that no collection modifications can happen between alias operations.
1 property 1 required
ErrorResponse
object
3 properties
DeleteAlias
object
Delete alias if exists
1 property 1 required
InferenceUsage
object
1 property 1 required
CreateAlias
object
Create alternative name for a collection. Collection will be available under both names for search, retrieve,
2 properties 2 required
CollectionsAliasesResponse
object
1 property 1 required
CreateAliasOperation
object
1 property 1 required
ModelUsage
object
1 property 1 required
HardwareUsage
object
Usage of the hardware resources, spent to process the request
7 properties 7 required
AliasDescription
object
2 properties 2 required
DeleteAliasOperation
object
Delete alias if exists
1 property 1 required
RenameAliasOperation
object
Change alias to a new one
1 property 1 required
RenameAlias
object
Change alias to a new one
2 properties 2 required
Usage
object
Usage of the hardware resources, spent to process the request
2 properties
AliasOperations
Group of all the possible operations related to collection aliases

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qdrant-aliases-api-openapi.yml Raw ↑

Other APIs Qdrant publishes across the network.

Qdrant Beta API
AE Profile APIs.io
Qdrant Collections API
AE Profile APIs.io
Qdrant Distributed API
AE Profile APIs.io
Qdrant Indexes API
AE Profile APIs.io
Qdrant Points API
AE Profile APIs.io
Qdrant Search API
AE Profile APIs.io
Qdrant Service API
AE Profile APIs.io
Qdrant Snapshots API
AE Profile APIs.io
#Aliases
← Back to Q APIs
API Details
ID
qdrant:qdrant-aliases-api
Server
{protocol}://{hostname}:{port}
Docs
https://qdrant.tech/documentation/
Provider
Qdrant
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=qdrant-aliases-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/qdrant-aliases-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Qdrant Aliases 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.