Skip to main content

​
Get Your API Key

Get a Free API Key

Click “Get API Key” to instantly receive a test key. No signup required.
 All API requests to Rotavision require authentication using an API key.

​
Self-Service Registration

  1. Visit api.rotavision.com/docs
  2. Click “Get API Key” in the top navigation
  3. Enter your email, name, and company
  4. Receive your rv_test_* key instantly via email
Test keys include 100 requests/day in the sandbox environment. For production access, contact our team.

​
Key Types

TypePrefixUsage
Liverv_live_Production environments
Testrv_test_Development and testing
Never expose your live API keys in client-side code, public repositories, or logs. Use environment variables or a secrets manager.

​
Authentication Methods

Include your API key in the Authorization header: 
curl https://api.rotavision.com/v1/vishwas/analyze \
  -H "Authorization: Bearer rv_live_abc123..." \
  -H "Content-Type: application/json" \
  -d '{"model_id": "my-model"}'

​
Using SDKs

Our SDKs handle authentication automatically: 
from rotavision import Rotavision

# Option 1: Pass directly
client = Rotavision(api_key="rv_live_...")

# Option 2: Environment variable (recommended)
# Set ROTAVISION_API_KEY in your environment
client = Rotavision()

​
API Key Scopes

When creating an API key, you can restrict its permissions to specific products:
ScopeDescription
vishwas:readRead fairness analyses and reports
vishwas:writeCreate new fairness analyses
guardian:readRead monitoring data and alerts
guardian:writeConfigure monitors and log inferences
dastavez:readRead extraction results
dastavez:writeSubmit documents for extraction
sankalp:proxyMake LLM proxy requests
orchestrate:readRead workflow executions
orchestrate:writeCreate and run workflows
gati:readRead fleet and route data
gati:writeSubmit optimization requests

​
Example: Read-Only Key

{
  "name": "Analytics Dashboard",
  "scopes": [
    "vishwas:read",
    "guardian:read",
    "gati:read"
  ]
}

​
Organization & Project Keys

For larger teams, Rotavision supports hierarchical key management: 
Organization (Acme Corp)
├── Project: Production
│   ├── Key: Backend Service (all scopes)
│   └── Key: Analytics (read-only)
├── Project: Staging
│   └── Key: CI/CD Pipeline
└── Project: Development
    └── Key: Local Testing
Project-scoped keys inherit organization-level rate limits but can have additional restrictions applied.

​
IP Allowlisting

For enhanced security, you can restrict API keys to specific IP addresses or CIDR ranges: 
{
  "name": "Production Backend",
  "allowed_ips": [
    "203.0.113.0/24",
    "198.51.100.42"
  ]
}

​
Key Rotation

We recommend rotating API keys periodically. The dashboard supports:
  1. Create new key with the same scopes
  2. Update your application with the new key
  3. Verify functionality in production
  4. Revoke the old key
Use a secrets manager (AWS Secrets Manager, HashiCorp Vault, etc.) to automate key rotation without application deployments.

​
Security Best Practices

Never hardcode API keys in your source code. Use environment variables or a secrets manager.
export ROTAVISION_API_KEY=rv_live_...
Only grant the permissions your application actually needs. A monitoring dashboard doesn’t need write access.
Use rv_test_ keys in development and CI/CD. Never use live keys in non-production environments.
Review API key usage in your dashboard. Investigate unexpected patterns or unauthorized access attempts.
For production keys, restrict access to known IP addresses of your servers.

​
Rate Limits by Key Type

Key TypeRequests/minRequests/dayAccess
Test (Self-Service)10100Get instantly
Live (Starter)60050,000Contact sales
Live (Growth)3,000500,000Contact sales
Live (Enterprise)CustomCustomContact sales
See Rate Limits for detailed information.