Sandbox base URL
Sandbox API keys
Sandbox keys are provisioned separately from production keys and only work against the sandbox environment. Contact support@truenroll.com to request a sandbox key.Never use a production API key against the sandbox, or a sandbox key against production.
Keys are environment-specific and will be rejected by the wrong environment.
What’s the same
- Full pipeline: classification, extraction, forensics, translation
- Webhook delivery to your registered endpoint
- All API routes, request/response shapes, and error codes
- Feature provisioning: your sandbox organization is configured with the same features as your production organization
What’s different
- Data is isolated: cases created in sandbox are not visible in production, and vice versa
- Sandbox documents are not used for any billing calculations
- Sandbox processing may be slower during periods of low priority allocation
Testing checklist
1
Get a sandbox key
Request a sandbox API key from support@truenroll.com.
2
Submit a test case
Upload a sample academic document using
POST /cases. Verify you receive a caseId
and a valid upload object in the response.3
Verify webhook delivery
Register a webhook endpoint (a service like
webhook.site works well for initial testing) and confirm you receive
case.classification.completed, case.extraction.completed, and other expected events.4
Fetch results
Once the extraction webhook fires, call
GET /cases/{id}/extraction and validate the
response shape against your integration code.5
Test error paths
Try submitting an unsupported file type, a missing
externalId, or requesting a
feature your organization doesn’t have. Confirm your error handling code responds
correctly.6
Switch to production
Replace the sandbox base URL and key with your production credentials. No other
changes should be required.