---
title: "Get job posting budget"
method: GET
path: "/v1/{account_id}/jobs/{job_id}/budget"
tags: ["Jobs"]
---

# Get job posting budget

`GET /v1/{account_id}/jobs/{job_id}/budget`

## Request

- Base URL: `https://api.curviate.com`
- URL: `https://api.curviate.com/v1/{account_id}/jobs/{job_id}/budget`
- Auth: HTTP bearer

Returns pricing to publish this job posting, the read-only companion to publishing, so you can price a publish before committing any money.

## Path parameters

- `account_id` string, required
- `job_id` string, required

## Response `200`

Pricing to publish this posting, the read-only companion to publishing, so a client can price a publish before committing money. There is no currency under `free`; currency only applies to promoted pricing.

- object
  - `object` 'job_posting_budget', required: Response type discriminator.
  - `promoted` object, required: Paid-promotion pricing.
    - `currency` string: ISO-4217 currency code.
    - `daily` object
      - `min` number: Minimum daily budget.
      - `max` number: Maximum daily budget.
      - `recommended` number: Recommended daily budget for PROMOTED.
      - `promoted_plus_recommended` number: Recommended daily budget for PROMOTED_PLUS.
    - `total` object
      - `min` number: Minimum total budget.
      - `max` number: Maximum total budget.
      - `recommended` number: Recommended total budget for PROMOTED.
      - `promoted_plus_recommended` number: Recommended total budget for PROMOTED_PLUS.
    - `estimated_daily_applicants_count` number: Estimated daily applicants if promoted.
  - `free` object, required: Free-posting eligibility. Note there is no currency field here, currency only applies to promoted pricing.
    - `eligible` boolean: Whether this posting can be published for free.
    - `estimated_daily_applicants_count` number: Estimated daily applicants if published for free.
  - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite.
    - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture.
    - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail).
    - `hint` object, required
      - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy.
      - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text.
    - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each.
    - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload.

## Other responses

- `400`: Missing or empty account_id.
- `401`: Missing or invalid API key.
- `403`: Forbidden. NO_ACTIVE_SEAT: the account is not attached to an active seat.
- `404`: The account_id does not belong to this tenant, or the job posting was not found. An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id.
- `422`: The account is restricted and cannot be queried.
- `429`: Rate limited, slow down and retry after the hinted delay.
- `500`: Internal error.
- `502`: A temporary error occurred. Please try again.
- `503`: Service unavailable.
- `504`: Gateway timeout.

---

[API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)