Skip to main content
​
type
string
invalid_request_error
​
status
number
404

​
What happened

The candidate_alias you provided does not match any candidate in your account. This can happen if the value is wrong or the candidate belongs to a different account. 
{
  "error": {
    "type": "invalid_request_error",
    "code": "CANDIDATE_NOT_FOUND",
    "message": "No candidate with candidate_alias 018e1b2c-3d4e-5f6a-7b8c-9d0e1f2a3b4c",
    "status": 404,
    "doc_url": "https://done.mintlify.app/errors/candidate-not-found"
  }
}

​
How to fix

Call GET /v1/candidates to retrieve your candidates and confirm the candidate_alias. 
curl https://api.georgekats.com/v1/candidates \
  -H "Authorization: Bearer <your_token>"

​
Common causes

Double-check the candidate_alias value — a single wrong character produces a 404.
Each candidate is scoped to the account that created it. A token from account A cannot access candidates from account B.
POST /v1/events expects a candidate_alias in the body, not a schema id or an internal database id. Make sure you are passing the value you provided as candidate_alias when creating the candidate.