Status Codes

Success

Code	Label	Description
`200`	OK	Request succeeded. Response body contains the requested data.
`201`	Created	A resource was created synchronously.
`202`	Accepted	Work was durably accepted for asynchronous processing. Auto Apply will use this at launch.

200 OK

{
  "data": [
    {
      "id": "a1b2c3d4-5678-9abc-def0-123456789abc",
      "title": "Senior Software Engineer",
      "company": { "name": "Acme Corp" }
    }
  ],
  "total": 1,
  "page": 1,
  "page_size": 25
}

202 Accepted

The coming-soon Auto Apply create and cancel calls will return 202 once the request is durably accepted. Creating an application begins in queued state:

{
  "api_version": "2026-07-21",
  "id": "6f9227f6-b704-4b58-a553-79773a041933",
  "apply_url": "https://boards.greenhouse.io/acme/jobs/4567890",
  "status": "queued",
  "cancel_requested": false,
  "queued_at": "2026-07-21T09:30:00Z"
}

Client Errors

Code	Label	Description
`400`	Bad Request	Invalid request parameters. Check `message` or Problem Details `detail`.
`401`	Unauthorized	Missing or invalid API key. Include `X-Api-Key` header.
`402`	Payment Required	Insufficient credits. Top up your wallet.
`403`	Forbidden	API key doesn’t have permission for this resource.
`404`	Not Found	The requested resource doesn’t exist.
`409`	Conflict	Request conflicts with current state or prior idempotent request.
`422`	Unprocessable Content	Target is valid JSON but cannot be processed.
`429`	Too Many Requests	Rate limit exceeded. Check `Retry-After` header.

At launch, Auto Apply domain errors will use Problem Details and add a stable code:

{
  "title": "webhook_secret_not_configured",
  "status": 409,
  "detail": "Configure an account webhook secret before creating applications.",
  "code": "webhook_secret_not_configured"
}

400 Bad Request

{
  "status": 400,
  "error": "Bad Request",
  "message": "Parameter 'page_size' must be between 1 and 100."
}

Common causes: missing required parameters, invalid enum values, out-of-range numbers, malformed JSON body.

401 Unauthorized

{
  "status": 401,
  "error": "Unauthorized",
  "message": "Missing or invalid API key. Include 'X-Api-Key' header."
}

Common causes: missing X-Api-Key header, revoked or rotated API key, or calling the wrong API host.

402 Payment Required

{
  "status": 402,
  "error": "Insufficient credits",
  "credits_required": 10,
  "credits_balance": 3
}

Common causes: wallet balance too low for the requested operation. Add credits in the dashboard.

403 Forbidden

{
  "status": 403,
  "error": "Forbidden",
  "message": "Your subscription does not include access to the Feed API."
}

Common causes: attempting to access subscription-only endpoints on a free plan, key restricted to specific endpoint scopes.

404 Not Found

{
  "status": 404,
  "title": "application_not_found",
  "detail": "Application not found.",
  "code": "application_not_found"
}

Common causes: deleted resource, typo in ID, resource belongs to a different account.

409 Conflict

For Auto Apply, common conflict codes are webhook_secret_not_configured, idempotency_key_reuse, idempotency_key_in_flight, ambiguous_ats, and not_cancelable. Fix the configuration or request state before retrying.

422 Unprocessable Content

Auto Apply returns job_apply_url_missing when a known job has no application URL and unsupported_ats when the resolved URL is not covered by the active provider catalog. Select another target; retrying the same request unchanged will not help.

429 Too Many Requests

{
  "error": "Rate limit exceeded",
  "detail": "Per-minute request limit reached.",
  "group": "General",
  "retry_after_seconds": 60
}

Common causes: exceeding per-minute, per-hour, or per-day request quotas. See Rate Limits.

Server Errors

Code	Label	Description
`500`	Internal Server Error	Something went wrong on our end. Retry the request.
`503`	Service Unavailable	Service is temporarily down for maintenance. Retry shortly.

For the coming-soon Auto Apply API, POST /api/auto-apply/applications is deployment-gated and currently returns 503 application/problem+json with code: "auto_apply_coming_soon". This is an availability signal, not a transient capacity failure; wait for the launch announcement before retrying.

500 Internal Server Error

{
  "status": 500,
  "error": "Internal Server Error",
  "message": "An unexpected error occurred. Please retry your request."
}

503 Service Unavailable

The current Auto Apply create gate returns:

{
  "title": "auto_apply_coming_soon",
  "status": 503,
  "detail": "Auto Apply application creation is coming soon.",
  "code": "auto_apply_coming_soon",
  "api_version": "2026-07-21"
}

Other services may return a transient 503 such as:

{
  "status": 503,
  "error": "Service Unavailable",
  "message": "The service is temporarily unavailable for maintenance. Please try again in a few minutes."
}

Retry Strategy

Status	Retry?	Strategy	Details
`400`	❌	Fix the request parameters	Read `message` or Problem Details `detail`; retry only after changing the invalid request.
`401`	❌	Check your API key	Verify the key is active in your dashboard. If you recently rotated keys, ensure you’re using the new one.
`402`	❌	Add credits	Check `credits_required` vs `credits_balance` in the response to see what the request needed.
`403`	❌	Upgrade your plan	This endpoint requires a higher subscription tier or specific permissions.
`404`	❌	Verify the resource ID	Confirm the resource exists and belongs to your account.
`409`	❌	Resolve the state conflict	Use the problem `code` to fix webhook setup, idempotency reuse, or terminal application state.
`422`	❌	Choose a processable target	Supply a job with an apply URL or an application URL supported by the active provider catalog.
`429`	✅	Wait for `Retry-After` seconds	Use the exact value from the `Retry-After` header. Implement exponential backoff with jitter for repeated 429s.
`500`	✅	Retry with exponential backoff	Start at 1s, double each attempt, cap at 30s. Max 3–5 retries. If persistent, check jobo.world/status.
`503`	⚠️	Inspect the problem code	Do not retry `auto_apply_coming_soon`; wait for launch. Retry transient maintenance responses with bounded backoff.

Getting Started

Resources

Success

200 OK

202 Accepted

Client Errors

400 Bad Request

401 Unauthorized

402 Payment Required

403 Forbidden

404 Not Found

409 Conflict

422 Unprocessable Content

429 Too Many Requests

Server Errors

500 Internal Server Error

503 Service Unavailable

Retry Strategy

​Success

​200 OK

​202 Accepted

​Client Errors

​400 Bad Request

​401 Unauthorized

​402 Payment Required

​403 Forbidden

​404 Not Found

​409 Conflict

​422 Unprocessable Content

​429 Too Many Requests

​Server Errors

​500 Internal Server Error

​503 Service Unavailable

​Retry Strategy

Success

200 OK

202 Accepted

Client Errors

400 Bad Request

401 Unauthorized

402 Payment Required

403 Forbidden

404 Not Found

409 Conflict

422 Unprocessable Content

429 Too Many Requests

Server Errors

500 Internal Server Error

503 Service Unavailable

Retry Strategy