Skip to main content

Authentication

All API requests require authentication using your API key in the X-API-Key header.

Getting Your API Key

  1. Sign up at sociavault.com
  2. Navigate to your Dashboard
  3. Copy your API key (starts with sk_live_)

Using Your API Key

Include your API key in every request using the X-API-Key header:
curl --request GET \
  --url 'https://api.sociavault.com/v1/scrape/tiktok/profile?handle=stoolpresidente' \
  --header 'X-API-Key: sk_live_your_api_key_here'
Keep your API key secure! Never expose it in client-side code, public repositories, or share it publicly.

API Performance

The SociaVault API is built to scale automatically with your needs.

Auto-Scaling

Our infrastructure automatically scales to handle your request volume

High Availability

99.9% uptime with redundant systems and automatic failover

Global CDN

Fast response times from anywhere in the world

No Rate Limits

Send as many requests as you need - we scale with you
Enterprise-grade infrastructure ensures your requests are handled quickly and reliably, no matter the volume.

Credit System

Each API endpoint consumes credits based on data complexity:
ComplexityCredit CostExamples
Simple1 creditProfile lookups, basic info
Moderate5-10 creditsPosts, videos, comments
Complex20+ creditsDemographics, analytics
Check individual endpoint documentation for specific credit costs.

Checking Your Balance

Monitor your credit balance in real-time via the Dashboard.
Each API response includes your remaining credits in the response headers for easy tracking.

Error Responses

The API uses standard HTTP status codes and returns detailed error messages:
Status CodeDescription
200Success
400Bad Request - Invalid parameters
401Unauthorized - Invalid or missing API key
403Forbidden - Insufficient credits
500Internal Server Error

Error Response Format

{
  "error": "Unauthorized",
  "message": "Invalid API key provided",
  "statusCode": 401
}

Best Practices

  • Store API keys in environment variables
  • Never commit API keys to version control
  • Use different keys for development and production
  • Rotate keys regularly for security
  • Cache frequently accessed data
  • Use pagination for large datasets
  • Only request the data you need
  • Monitor your usage in the dashboard
  • Always check response status codes
  • Implement proper error handling
  • Log errors for debugging
  • Retry failed requests with exponential backoff
  • Implement caching strategies
  • Use batch requests when possible
  • Monitor response times in your logs
  • Contact support for optimization advice

Need Help?