Skip to main content
Understanding these concepts is enough to navigate every part of TruEnroll.

GlossaryGlossary

Case

Case

A case is the central unit of work. It is identified by your externalId and groups all document submissions for a single candidate or evaluation subject. Each submission adds an upload to the case.A case is the central unit of work. It is identified by your externalId and groups all document submissions for a single candidate or evaluation subject. Each submission adds an upload to the case.
Key behaviors:
  • externalId is unique per organization. Submitting to an existing externalId adds a new upload to the existing case rather than creating a new one.
  • Status is aggregate. A case is completed only when every upload (and every enabled feature within each upload) has reached a terminal state.
  • Your organization’s cases. Cases operators create in TruEnroll are readable and listed too, and you can link one to an externalId.
  • Delete. Deleting a case you created removes it from TruEnroll and from list results; its externalId cannot receive new uploads.

Credential

A credential is the structured representation of a single education qualification identified by classification. One uploaded file can produce multiple credentials. For example, a transcript covering two degrees produces two credentials, one per qualification. Non-education documents (ID cards, cover letters, etc.) are identified and excluded from further processing.
Key behaviors:
  • externalId is unique per organization. Submitting to an existing externalId adds a new upload to the existing case rather than creating a new one.
  • Status is aggregate. A case is completed only when every upload (and every enabled feature within each upload) has reached a terminal state.
  • Soft delete. Deleting a case excludes it from list results; the case cannot receive new uploads.

Credential

A credential is the structured representation of a single education qualification identified by classification. One uploaded file can produce multiple credentials. For example, a transcript covering two degrees produces two credentials, one per qualification. Non-education documents (ID cards, cover letters, etc.) are identified and excluded from further processing. A credential holds:A credential holds:
  • The document type (e.g., academic transcript, diploma)
  • Candidate identity (name, date of birth)
  • The issuing institution (name, country, accreditation)
  • Qualification details (degree, program, enrollment period)
  • A list of courses with codes, credits, and grades
Extraction, forensics, and grade normalization all run per credential.

Features

Features are opt-in capabilities you specify at case submission time. Your organization must be provisioned for a feature before it can be used. Requesting an unavailable feature fails synchronously with 403 before any files are stored or processed.
  • The document type (e.g., academic transcript, diploma)
  • Candidate identity (name, date of birth)
  • The issuing institution (name, country, accreditation)
  • Qualification details (degree, program, enrollment period)
  • A list of courses with codes, credits, and grades
Extraction, forensics, and grade normalization all run per credential.

Features

Features are opt-in capabilities you specify at case submission time. Your organization must be provisioned for a feature before it can be used. Requesting an unavailable feature fails synchronously with 403 before any files are stored or processed. Institution accreditation status is returned as part of the extraction result (the institution.accreditation object). It is not a separately requested featureInstitution accreditation status is returned as part of the extraction result (the institution.accreditation object). It is not a separately requested feature. Evaluation is completed by an operator in the UI. It is separate from the three upload features. Use evaluation results to check its progress; case and upload processing statuses do not indicate evaluation completion.

API keyAPI keys

Partner API keys are provisioned by your TruEnroll account manager and scoped to your organization. All Partner API routes (/partner/v1/...) require a partner key; other key types are rejectedPartner API keys are provisioned by your TruEnroll account manager and scoped to your organization. All Partner API routes (/partner/v1/...) require a partner key; other key types are rejected.

Webhooks


Webhooks

TruEnroll delivers results as events rather than requiring you to poll. A webhook configuration is a registered HTTPS endpoint that receives event payloads when processing stages complete.TruEnroll delivers results as events rather than requiring you to poll. A webhook configuration is a registered HTTPS endpoint that receives event payloads when processing stages complete.TruEnroll delivers results as events rather than requiring you to poll. A webhook configuration is a registered HTTPS endpoint that receives event payloads when processing stages complete. You register webhook endpoints yourself through the Partner API. An endpoint registered with partner audience receives all case.*.completed and case.*.failed events for your cases.

Configuring webhooks

Register an endpoint and set the shared secret.

Webhook event reference

Every event name, payload shape, and delivery behavior.

Configuring webhooks

Register an endpoint and set the shared secret.

Webhook event reference

Every event name, payload shape, and delivery behavior.
You register webhook endpoints yourself through the Partner API. An endpoint registered with partner audience receives all case.*.completed and case.*.failed events for your cases.You register webhook endpoints yourself through the Partner API. An endpoint registered with partner audience receives all case.*.completed and case.*.failed events for your cases.

Configuring webhooks

Register an endpoint and set the shared secret.

Webhook event reference

Every event name, payload shape, and delivery behavior.