Skip to main content

​
Credit System

Current prices, wallet top-ups, and subscription options live on the pricing page and in the dashboard.
Credits are the wallet unit used by metered API calls. When a metered request succeeds, the API deducts the applicable credits from your wallet and returns headers you can use for logging, budget alerts, or usage reconciliation.

​
Metered Endpoints

These endpoint families can consume wallet credits depending on your plan:

Jobs Search

Full-text and advanced search across job listings. Search-style endpoints meter by delivered results, so a request that returns fewer records than the requested page size only bills for what was delivered.GET /api/jobs + POST /api/jobs/search + GET /api/companies/{id}/jobs

Jobs Feed

Cursor-paginated streams for high-volume job sync. Feed subscriptions can include this API family without wallet debits; pay-as-you-go access is metered by delivered results.POST /api/jobs/feed

Geocode

Convert raw location strings into structured city, region, country, and coordinate data. Geocoding is a flat metered lookup.GET /api/locations/geocode
Search, Feed, and the Companies list-jobs endpoint perform a balance precheck against the request size and debit the actual delivered quantity after the response is built. Flat metered endpoints debit before work begins. Failed 4xx / 5xx responses do not deduct credits.

​
Unmetered Endpoints

These endpoints do not deduct wallet credits:
EndpointNotes
GET /api/jobs/expiredDesigned to keep downstream inventories clean. The request still counts toward rate limits.
POST /api/jobs/feed (with Jobs Feed subscription)Wallet debits are waived for subscription holders.
GET /api/jobs/{id}Single job lookup by ID. The request still counts toward rate limits.
GET /api/companies/{id}Public company profile lookup. No API key is required.

​
Currently Unavailable

EndpointStatus
/api/auto-apply/*Temporarily disabled. Requests return 503 Service Unavailable while paused.

​
Request Flow

Every metered API request goes through this pipeline before a response is returned:
1

Authenticate

The API validates your X-Api-Key header when the endpoint requires one. If the key is missing or invalid, you receive 401 Unauthorized and no wallet activity occurs.
2

Rate Limit Check

Your request is checked against the rate-limit windows for your plan. If a window is exhausted, you receive 429 Too Many Requests with a Retry-After header. No credits are deducted on rate-limited requests.
3

Wallet Check

Metered endpoints verify that your wallet can cover the request before work begins. If the balance is insufficient, you receive 402 Payment Required with X-Credits-Required and X-Credits-Balance.
4

Debit and Response

When a wallet debit occurs, the response includes X-Credits-Deducted and X-Credits-Balance. Unmetered responses and zero-debit responses may omit credit headers.

​
Credit Response Headers

Credit headers appear only when wallet metering is relevant to the response:
HeaderWhen ReturnedDescription
X-Credits-Deductedwallet debitCredits consumed by this specific request.
X-Credits-Balancewallet debit, 402Your wallet balance after the debit or failed precheck.
X-Credits-Required402 onlyCredits the request would have needed to succeed.

​
Successful Metered Request

HTTP/1.1 200 OK
X-Credits-Deducted: <credits_used>
X-Credits-Balance: <remaining_balance>
Content-Type: application/json

​
Insufficient Credits

HTTP/1.1 402 Payment Required
X-Credits-Required: <credits_needed>
X-Credits-Balance: <current_balance>
Content-Type: application/json

{
  "error": "Insufficient credits",
  "credits_required": 123,
  "credits_balance": 45
}
Add credits in the dashboard, then retry the request.

​
FAQ

Use jobo.world/pricing for public pricing and the dashboard for your wallet, subscription, and billing status.
Metered endpoints return HTTP 402 Payment Required. The response includes X-Credits-Required and X-Credits-Balance so you can decide whether to add credits and retry.
No. Credits are only deducted when a metered request successfully completes and produces billable work. Rate limits, validation errors, authentication failures, and server errors do not deduct credits.
Yes. Rate limits apply per minute, per hour, and per day to protect service quality. Credits are deducted only after rate-limit checks pass. See the Rate Limits page for details.
Some subscriptions include specific API families without wallet debits. If an endpoint is included with your subscription, the API can still apply rate limits, but wallet credit headers may be absent because no debit occurred.
Use the dashboard to review wallet and billing settings. You can also monitor spend programmatically by reading X-Credits-Deducted and X-Credits-Balance on metered responses.