Turnitin similarity checks use the Core API

Turnitin is automatable today through the Turnitin Core API for similarity checking. The Core API page describes a RESTful API that lets an integration submit a file, generate a Similarity Report, and show it without leaving the host platform. The iThenticate integrator guide says the API uses JSON and a tenant URL such as https://customerA.turnitin.com/api. The workflow is create a submission, upload the file, wait for processing, request a Similarity Report, wait again, and request a report viewer URL. Calls are authorized with an API key sent in an HTTP header. An administrator creates that key as a Secret on the Integrations tab, one scope and key per integration. The FAQ says to set X-Turnitin-Integration-Name to the LMS or software name and X-Turnitin-Integration-Version to that software's version. Webhooks signal SUBMISSION_COMPLETE and SIMILARITY_COMPLETE. Get Submission Info and Get Similarity Report Info are the polling equivalents. The same public guides name Get Features Enabled, Create Webhook, List Webhooks, Upload Submission, and Generate Report. The Core API page says the API reference itself requires login credentials, issued through a partner request, an account manager, or sales. TCA is listed for Similarity, iThenticate 2.0, Crossref Similarity Check v2, and SimCheck. License flags such as exclude_small_matches come back from Get Features Enabled. The FAQ forbids programmatic use of the viewer to harvest report data or PDFs. LTI 1.3 is a separate Feedback Studio integration that Turnitin validates only after 1EdTech certification. No first-party MCP server was established. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 5 because the submission and report workflow is documented, while the reference, the key, and the feature set are tenant-gated and the report body is not returned as data.

Best path today: api · Overall automatability: 5/10