SIS Integration

TCEvaluator can deliver confirmed evaluation results into your Student Information System (SIS), so transfer credit decisions land in the student’s record without re-keying.

Two paths into your SIS

Webhooks (self-serve). If your SIS (or an integration layer in front of it) can receive HTTPS calls, configure an On Completion webhook with Complete Evaluation Info under Admin Settings › Integrations — see Webhooks. Custom headers and field mapping cover most ingestion APIs.

Managed SIS connector. For SIS platforms with dedicated support (for example CampusNexus), TCEvaluator operates a connector service that delivers completed evaluations directly into the SIS. Connectors are provisioned per institution — contact your TCEvaluator account manager to set one up for your SIS.

How delivery works

Once a connector is enabled for your institution:

1. An evaluator finishes an evaluation as usual.
2. The confirmed results — matched courses, credits, and student identifiers — are delivered to your SIS automatically.
3. Delivery status is visible on the evaluation itself.

When delivery fails

If the SIS rejects or fails a delivery, the completed evaluation shows an SIS errors alert — open it to see the error details for each item. The most common causes are on the SIS side:

• the student doesn’t exist yet in the SIS (or identifiers don’t line up),
• a course code in the results isn’t recognized by the SIS,
• SIS-side permissions or maintenance windows.

Fix the underlying record in the SIS, then ask your account manager to re-deliver, or re-run the evaluation if the results themselves need to change.

Which path should we use?

Start with webhooks if you have any integration middleware (Boomi, MuleSoft, Zapier-class tools, or an in-house API) — you control the mapping end to end and can go live today. Choose the managed connector when you want TCEvaluator to own delivery into a supported SIS directly.