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

API Playground

Not Connected
AUTHENTICATION

Authentication & Your First API Request

Welcome to the Codequiry API! This guide will walk you through authenticating your requests and making your first successful API call. All API requests require authentication using your unique API key to ensure secure access to your account.

Base API Endpoint
https://codequiry.com/api/v1/

How Authentication Works

The Codequiry API uses API key authentication for secure and simple access control. Every API request must include your unique API key in the request headers. This method ensures that only authorized users can access your account data and perform operations.

Security Best Practice: Always keep your API key secure and never expose it in client-side code, public repositories, or browser applications. Treat it like a password—if compromised, regenerate it immediately from your dashboard.
Required HTTP Headers

Include these headers in every API request:

  • apikey Your unique 64-character authentication token (Required for all endpoints)
  • Accept: application/json Specifies that you want JSON responses
  • Content-Type: application/json Required for POST/PUT requests with JSON payloads

Test Your Authentication

The best way to verify your API key works correctly is to call the /account endpoint. This endpoint returns your account information and usage statistics without consuming any API credits—making it perfect for testing and debugging your integration.

API Endpoint
POST https://codequiry.com/api/v1/account
Example Request

Replace YOUR_API_KEY_HERE with your actual API key from the dashboard.

		curl -X POST \
  https://codequiry.com/api/v1/account \
  -H 'Accept: application/json' \
  -H 'apikey:  YOUR_API_KEY_HERE '
		
cURL Command
Request Parameters

No additional parameters required. Authentication is handled entirely through the apikey header.

Expected Response
		{
    "user": "John Developer",
    "email": "[email protected]",
    "peer_checks_remaining": "unlimited",
    "pro_checks_remaining": 187,
    "submissions": 1318
}
		
JSON Response
Understanding Response Fields
  • user — Your account display name as configured in your profile
  • email — The email address associated with your Codequiry account
  • peer_checks_remaining — Number of peer review checks available (may show "unlimited" for certain plans)
  • pro_checks_remaining — Number of professional-grade checks remaining in your quota
  • submissions — Total number of code submissions you've analyzed across all checks
Connect Your API Key: To test endpoints directly from this documentation, connect your API key using the playground at the top of the page.

Troubleshooting Authentication Errors

If your authentication isn't working, you'll receive one of these common HTTP error responses:

401 Unauthorized

Cause: Missing or invalid API key

Solution: Verify your API key is correct, properly included in the apikey header, and hasn't been regenerated or revoked.

429 Too Many Requests

Cause: Rate limit exceeded

Solution: Implement exponential backoff and retry logic. Check our rate limits in the API Info section.

Next Steps in Your API Journey

Congratulations! You've successfully authenticated with the Codequiry API. Now you're ready to start detecting code plagiarism. Here's your recommended learning path: