> For the complete documentation index, see [llms.txt](https://developerdocs.instructure.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developerdocs.instructure.com/services/canvas/external-tools/plagiarism-detection-platform/plagiarism_detection_submissions.md).
# Plagiarism Detection Submissions
**LTI API for Plagiarism Detection Submissions (Must use** [**JWT access tokens**](/services/canvas/external-tools/plagiarism-detection-platform/file.jwt_access_tokens.md) **with this API).**
#### A Submission object looks like:
```js
{
"lti_course_id": "66157096483e6b3a50bfedc6bac902c0b20a8241",
"course_id": 10000000000060,
// The submission's assignment id
"assignment_id": 23,
// This is the submission attempt number.
"attempt": 1,
// The content of the submission, if it was submitted directly in a text field.
"body": "There are three factors too...",
// The types of submission ex:
// ('online_text_entry'|'online_url'|'online_upload'|'media_recording'|'student_
// annotation')
"submission_type": "online_text_entry",
// The timestamp when the assignment was submitted
"submitted_at": "2012-01-01T01:00:00Z",
// The URL of the submission (for 'online_url' submissions).
"url": null,
// The id of the user who created the submission
"user_id": 134,
// UTC timestamp showing when the user agreed to the EULA (if given by the tool
// provider)
"eula_agreement_timestamp": "1508250487578",
// The current state of the submission
"workflow_state": "submitted",
// Files that are attached to the submission
"attachments": null
}
```
#### A File object looks like:
```js
{
"size": 4,
"content-type": "text/plain",
"url": "http://www.example.com/files/569/download?download_frd=1",
"id": 569,
"display_name": "file.txt",
"created_at": "2012-07-06T14:58:50Z",
"updated_at": "2012-07-06T14:58:50Z"
}
```
## [Get a single submission](#method.lti/submissions_api.show)
[Lti::SubmissionsApiController#show](https://github.com/instructure/canvas-lms/blob/master/app/controllers/lti/submissions_api_controller.rb)
#### `GET /api/lti/assignments/:assignment_id/submissions/:submission_id`
**Scope:** `url:GET|/api/lti/assignments/:assignment_id/submissions/:submission_id`
Get a single submission, based on submission id.
## [Get the history of a single submission](#method.lti/submissions_api.history)
[Lti::SubmissionsApiController#history](https://github.com/instructure/canvas-lms/blob/master/app/controllers/lti/submissions_api_controller.rb)
#### `GET /api/lti/assignments/:assignment_id/submissions/:submission_id/history`
**Scope:** `url:GET|/api/lti/assignments/:assignment_id/submissions/:submission_id/history`
Get a list of all attempts made for a submission, based on submission id.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://developerdocs.instructure.com/services/canvas/external-tools/plagiarism-detection-platform/plagiarism_detection_submissions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.