Developer API

Code Plagiarism Detection API

Build plagiarism detection into your applications with our powerful REST API. Detect copied code across 20+ billion sources with industry-leading accuracy.

99.7%
Accuracy
51+
Languages
20B+
Sources
5
SDKs
Get Your API Key View Documentation

API Playground

Not Connected

Connect your API key to test endpoints in real-time

Introduction Authentication View Checks Create Check
VIEW CHECKS

Retrieve Your Check History

Access your complete plagiarism check history through the API. This endpoint returns all checks associated with your account, including their current status, creation dates, and metadata—perfect for building dashboards, monitoring workflows, or syncing data with your application.

API Endpoint
POST https://codequiry.com/api/v1/checks

How This Endpoint Works

The /checks endpoint provides a comprehensive list of all plagiarism checks in your account. Each check object contains essential information like its name, creation date, current status, and unique identifier. Results are ordered by most recent first, making it easy to track your latest analyses.

Pro Tip: This endpoint returns your entire check history. For accounts with hundreds of checks, consider implementing client-side pagination or filtering to improve performance in your application.
Common Use Cases
Dashboard Building

Display recent checks and their statuses in your application interface

Data Synchronization

Keep your local database in sync with Codequiry's check records

Audit & Reporting

Generate reports on plagiarism detection activity over time

Status Monitoring

Track in-progress analyses and identify completed checks

Making the Request

This endpoint requires only authentication—no additional parameters needed. Simply include your API key in the headers and you'll receive your complete check history.

Example Request
		curl -X POST \
  https://codequiry.com/api/v1/checks \
  -H 'Accept: application/json' \
  -H 'apikey:  YOUR_API_KEY_HERE '
		

			

				cURL Command
Request Parameters

No additional parameters required—authentication via the apikey header is sufficient.

Example Response 
		[
    {
        "id": 1542,
        "course_id": 412,
        "name": "Python Assignment Check",
        "created_at": "2024-01-15 14:30:22",
        "updated_at": "2024-01-15 14:45:18",
        "status_id": 3,
        "job_id": 8847
    },
    {
        "id": 1541,
        "course_id": 410,
        "name": "JavaScript Project Review",
        "created_at": "2024-01-14 09:15:44",
        "updated_at": "2024-01-14 09:28:12",
        "status_id": 3,
        "job_id": 8846
    },
    {
        "id": 1540,
        "course_id": 410,
        "name": "Java Final Exam Code",
        "created_at": "2024-01-13 16:22:11",
        "updated_at": "2024-01-13 16:35:55",
        "status_id": 2,
        "job_id": 8845
    }
]
		

			

				JSON Array Response
Connect Your API Key: To test this endpoint directly, connect your API key using the playground at the top of the page.

Understanding the Response

Each check object in the response array contains important metadata about your plagiarism detection jobs:

Field Type Description
id Integer Unique identifier for this check—use this to retrieve detailed results
course_id Integer The course/project ID this check belongs to (for organizational purposes)
name String The human-readable name you assigned when creating this check
created_at DateTime Timestamp when the check was initially created (UTC timezone)
updated_at DateTime Last modification time—typically when processing completed
status_id Integer Current processing status (see status reference below)
job_id Integer Internal processing job identifier (0 indicates not yet processed)

Check Status Reference

The status_id field indicates the current state of your plagiarism check. Use these values to display progress indicators or determine when results are ready:

Status ID: 1
Pending

Check created but analysis not yet started—awaiting user action

Status ID: 2
Processing

Currently analyzing code for plagiarism—results not yet available

Status ID: 3
Completed

Analysis finished successfully—plagiarism results are ready to view

Status ID: 4
Failed

Processing encountered an error—contact support if this persists

Best Practices & Tips

Efficient Polling

Instead of repeatedly calling this endpoint, use specific check IDs with the /check/get endpoint when monitoring individual analyses

Client-Side Filtering

Filter results by status, date, or name in your application to quickly find specific checks without additional API calls

Caching Strategy

Cache check lists for a few minutes in your application to reduce API calls for frequently-accessed data

Pagination

For accounts with many checks, implement pagination in your UI to improve loading times and user experience

Continue Your Journey

Now that you know how to retrieve your check history, explore these related endpoints:

Create a New Check

Start a fresh plagiarism detection analysis by creating a new check and uploading code files.

Create Check Guide
Get Detailed Results

Retrieve comprehensive plagiarism analysis results for a specific check ID.

Results Guide