Sandbox

The sandbox is a separate Certivu deployment with its own data and its own keys. It behaves exactly like production — same endpoints, same signing pipeline, same verification — with two differences:

• Signing never consumes or enforces billing quota. Sign as much as you need while building.
• API keys use the ctv_test_key_… prefix instead of ctv_key_…, so test and live credentials are never confused.

Base URL

https://api-sandbox.certivu.ai

Point your SDK or HTTP client at this base URL while developing. Switch back to https://api.certivu.ai for production.

import { CertivuClient } from "@certivu/sdk";

const certivu = new CertivuClient({
  apiKey: process.env.CERTIVU_TEST_KEY,
  baseUrl: "https://api-sandbox.certivu.ai",
});

Confirming which environment you’re on

Every response carries an X-Certivu-Environment header (production or sandbox). You can also probe it directly:

curl https://api-sandbox.certivu.ai/version
# { "version": "2.3.0", "environment": "sandbox", "sandbox": true }

Isolation

Sandbox data (orgs, generators, records) is completely separate from production. Create a sandbox account and generators independently — production credentials do not work against the sandbox, and vice versa.

Sandbox tokens verify against the sandbox API only. When you go live, re-sign your production content with production credentials.