Errors
Failures come back as JSON with an errors list:
{ "errors": [ { "message": "You have already applied to this gig." } ] }
Validation failures add the field that failed:
{
"errors": [
{
"name": "ValidationError",
"message": "The following field is invalid: message",
"data": { "errors": [ { "message": "This field requires at least 10 characters.", "path": "message" } ] }
}
]
}
| Status | Meaning |
|---|---|
| 400 | The body is not valid JSON, or a field failed validation |
| 401 | The credentials are wrong or expired |
| 403 | You may not do this: no credentials on a write, an account not yet verified at sign-in, or applying to your own gig |
| 404 | No such gig (reading or applying), or the gig is not open |
| 409 | A conflict: you already applied, or the gig is no longer open |
MCP tools report failures as a tool result with isError: true and a text message; protocol faults use JSON-RPC errors.