Skip to main content

Sandbox Mode

Vidiking provides a sandbox environment for testing your integration without spending credits.

Sandbox vs Production

FeatureSandboxProduction
CostFreeFunds deducted
WatermarkYes (Vidiking logo)No
Output expiry24 hours7 days
ResolutionUp to 720pUp to 4K
Rate limit10 requests/min100 requests/min
AI modelsLimited selectionAll models
WebhooksSupportedSupported

How to Switch

The environment is determined by the x-sandbox header. By default, all requests go to production.

curl

# Sandbox request
curl -X POST https://api.vidiking.com/v1/render \
-H "Authorization: Bearer $VIDIKING_API_KEY" \
-H "x-sandbox: true" \
-H "Content-Type: application/json" \
-d '{ ... }'

# Production request (default)
curl -X POST https://api.vidiking.com/v1/render \
-H "Authorization: Bearer $VIDIKING_API_KEY" \
-H "Content-Type: application/json" \
-d '{ ... }'

Node.js

import Vidiai from '@vidiking/sdk';

// Sandbox client
const sandbox = new Vidiai({
apiKey: process.env.VIDIKING_API_KEY,
sandbox: true,
});

// Production client (default)
const production = new Vidiai({
apiKey: process.env.VIDIKING_API_KEY,
});

Python

from vidiai import Vidiai

# Sandbox client
sandbox = Vidiking(api_key="your_key", sandbox=True)

# Production client (default)
production = Vidiking(api_key="your_key")

Sandbox Limitations

  • Output files include a semi-transparent Vidiking watermark in the bottom-right corner.
  • Files are automatically deleted after 24 hours.
  • Maximum resolution is capped at 720p regardless of the resolution parameter.
  • Some AI models (Runway Gen-4 HQ, ElevenLabs HD) are unavailable in sandbox mode.
  • Rate limits are lower to prevent abuse.

When to Use Sandbox

  • During initial development and testing
  • In CI/CD pipelines for integration tests
  • For demos and proof-of-concept work
  • When debugging timeline JSON structure

Once your integration is working correctly in sandbox, remove the x-sandbox: true header (or set sandbox: false in the SDK) to switch to production.