Errors & Troubleshooting
HTTP status codes, error responses, and solutions for the PaperStack API.
Errors & Troubleshooting
HTTP Status Codes
| Code | Meaning | Cause |
|---|---|---|
200 | OK | Request succeeded |
302 | Redirect | Root endpoint redirects to API reference |
400 | Bad Request | Invalid year format, filename, or malformed URL |
401 | Unauthorized | Missing or malformed Authorization header |
403 | Forbidden | Invalid, expired, or revoked API key |
404 | Not Found | Exam, year, shift, file, or diagram does not exist |
429 | Too Many Requests | Rate limit exceeded (2 req/s per key) |
500 | Internal Server Error | Gateway misconfiguration |
502 | Bad Gateway | Authentication service (Unkey) or data origin temporarily unavailable |
Error Response Format
All errors return JSON with a single field:
{
"error": "Human-readable error description"
}Common Errors
Debugging Tips
- Verify your key starts with
ps_ - Check the URL for typos — use
neet, notneet2024 - List available years first —
curl https://api.paperstack.qzz.io/neet - Use shorthand shifts —
s1instead of full shift names - Use the API Reference at /reference to test endpoints interactively
- Monitor your usage on the Dashboard