Files

3.5 KiB

title, short_description, description, weight, partition
title short_description description weight partition
API & SDKs Talk to Qdrant through REST or gRPC and use official client SDKs for Python, JavaScript, Rust, Go, Java, and .NET. Connect to Qdrant with REST or gRPC APIs and official client libraries for Python, JavaScript, Rust, Go, Java, and .NET to build vector search apps. 230 develop

Interfaces

Qdrant supports these "official" clients.

Note: If you are using a language that is not listed here, you can use the REST API directly or generate a client for your language using OpenAPI or protobuf definitions.

Client Libraries

Client Repository Installation Version
python Python pip install qdrant-client[fastembed] Latest Release
typescript JavaScript / Typescript npm install @qdrant/js-client-rest Latest Release
rust Rust cargo add qdrant-client Latest Release
golang Go go get github.com/qdrant/go-client Latest Release
.net .NET dotnet add package Qdrant.Client Latest Release
java Java Available on Maven Central Latest Release

API Reference

All interaction with Qdrant takes place via the REST API. We recommend using REST API if you are using Qdrant for the first time or if you are working on a prototype.

API Documentation
REST API OpenAPI Specification
gRPC API gRPC protobuf definitions

gRPC Interface

The gRPC methods follow the same principles as REST. For each REST endpoint, there is a corresponding gRPC method.

As per the configuration file, the gRPC interface is available on the specified port.

service:
  grpc_port: 6334

Running the service inside of Docker will look like this:

docker run -p 6333:6333 -p 6334:6334 \
    -v $(pwd)/qdrant_storage:/qdrant/storage:z \
    qdrant/qdrant

When to use gRPC: The choice between gRPC and the REST API is a trade-off between convenience and speed. gRPC is a binary protocol and can be more challenging to debug. We recommend using gRPC if you are already familiar with Qdrant and are trying to optimize the performance of your application.