Skip to main content
The TruEnroll sandbox is a fully functional environment that mirrors production behavior (the same API, the same pipeline, the same webhook events) using isolated data that never touches your production tenant.

​
Sandbox base URL

The interactive playground in these docs uses the sandbox by default. To switch to production, change the environment selector in the playground.

​
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.

​
Postman collection

Every Partner API route, including the evaluation endpoints, is available as a Postman collection with environments for local, sandbox, and production.

Collection

TruEnroll Partner API requests.

Sandbox environment

Base URL and empty apiKey / caseId variables.
Import both, then set apiKey in the environment. A production environment and a local environment are also available. The collection ships with no key in it; keep your key in the environment, which Postman stores as a secret.

​
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 evaluation results

Arrange for an operator to evaluate your sandbox case in TruEnroll. Poll GET /cases/{id}/evaluation, then download a credential PDF and XLSX using a completed evaluationId. Check that unfinished reports return 409. Test combined separately because combined readiness can lag credential completion: poll GET /cases/{id}/evaluation/combined until it reports completed, then download the report. Keep JSON polling as a fallback for the best-effort case.evaluation.completed notification.
6

Test a case created in the UI

Have an operator create a case in TruEnroll directly, without going through POST /cases. Fetch it by its case number and confirm your code tolerates externalId: null and uploadId: null, and that it reads the feature list rather than assuming every feature is present.
7

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.
8

Switch to production

Replace the sandbox base URL and key with your production credentials. No other changes should be required.