Code Plagiarism API BETA

Integrate your existing software with Codequiry's source code plagiarism checker.

API Demonstration

Connect your account to run the live examples.

3. Retrieving Checks

Before using the endpoints to retrieve and send data, we will need to make sure that each request is being sent with the correct header information.

Endpoint for retrieving check history

About: Checking History

This request will return a full history of checks ran under your account. Meaning that depending on your history size, requests can take longer. Retrieval of full checking history should be used carefully, in most cases it is not necessary as check id's are provided after a new check is created (more explained in the next sections).

Similar to retrieving account information, this request does not require sending of any additional data. We can retrieve checking history just by providing the API Key header.

				curl -X POST \
  https://codequiry.com/api/v1/checks \
  	-H 'Accept: */*' \
  	-H 'apikey:  YOUR_API_KEY_HERE ' 
				
cURL Command
Sample Response (JSON Array of Objects)
				[
    {
        "id": 1,
        "course_id": 412,
        "name": "Python Checks",
        "created_at": "2019-02-02 01:09:32",
        "updated_at": "2019-02-14 05:48:54",
        "status_id": 2,
        "job_id": 0
    }
]
				
JSON Array
About the data

This probably looks foreign to you, don't worry, we will explain what each property means, its importance, and the different values they can take on. For now all you need to know is how to retrieve your checking history for future usage. Note that the checks will be returned with the order of most recent being first in the array.

What's next

For optimal understanding of API usage, we recommend following this guide.

Our Mission

Codequiry aims to achieve an equally fair environment for fields relating to computer science by preventing the use of unoriginal code. The first step to preserving academic integrity and original source code starts here.

© 2019 Codequiry, LLC