Developer API
Service Status
Build plagiarism detection into your apps. Check code against 20+ billion sources.
const response = await fetch('https://codequiry.com/api/v1/check', {
method: 'POST',
headers: { 'apikey': 'YOUR_API_KEY' },
body: formData
});
// Check created!
SERVICE STATUS
Service Status
Whether the checking engine and its live-progress stream are up. Read it before starting a batch, or to drive a status light in your own tool; Codequiry Desktop's sidebar indicator is this endpoint.
GET https://codequiry.com/api/v1/status
What it reports
Two probes: core (the engine that runs checks) and stream (the service that publishes live progress). online is true only when both are up. The answer comes from a one-minute cache shared with the dashboard's status badge, so however many clients poll it, the engine is probed once a minute. Poll this rather than the engine host itself.
While the engine is offline,
POST /check/start answers 503 and the check stays queued on your side; nothing is consumed.
Request Example
curl 'https://codequiry.com/api/v1/status' \
-H 'Accept: application/json' \
-H 'apikey: YOUR_API_KEY_HERE '
Response
{
"core": { "online": true },
"stream": { "online": true, "subscribers": 3, "aids": 2 },
"online": true,
"latency_ms": 412,
"cached_at": "2026-08-21T11:40:00+00:00"
}
| Field | Type | Description |
|---|---|---|
online | Boolean | true only when both core and stream are up |
core.online | Boolean | The checking engine answered its health probe |
stream.online | Boolean | The live-progress stream answered; subscribers is how many dashboards are watching checks right now |
latency_ms | Integer | How long the probe took when the cached answer was taken |
cached_at | String | When the cached answer was taken (ISO 8601) |
stale | Boolean | Present when a probe was already in flight and the last known answer was served instead |