Skip to content

API Keys

PT | EN

Vectora API Keys are used for programmatic authentication and integration with third-party tools that do not support interactive SSO flows.

Overview

Unlike JWT, which is intended for short-lived sessions, API Keys are persistent and allow controlled access to specific Vectora namespaces.

Security

Vectora uses one-way hashing (SHA-256) to store your keys. This means that even if the database is compromised, your original keys cannot be recovered.

How to Use

To authenticate a REST request using an API Key, send the X-API-Key header:

curl -X POST https://api.vectora.app/v1/search \
  -H "X-API-Key: vca_live_xxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"query": "how does auth work?"}'

Key Management

You can manage your keys through the Vectora CLI:

# Create a new key
vectora auth keys create --name "GitHub Actions" --namespace "prod"

# List active keys
vectora auth keys list

# Revoke a key
vectora auth keys revoke <key_id>

External Linking

Security & Management Reference

ConceptResourceLink
API Key Best PracticesGoogle Cloud Docscloud.google.com/docs/authentication/api-keys
SHA-256NIST Standardcsrc.nist.gov/projects/hash-functions
RBACAuth0 Blogauth0.com/blog/role-based-access-control/