Update offer
Patch fields on an existing offer. Only the keys included in the request body are modified; omitted keys are left untouched. Updates to starts_on, opening_id (when your organization versions offers on opening changes), or version-triggering custom fields create a new offer version for the same application rather than mutating the prior row — fetch the updated offer with current_only=true to find the new current version. The date-typed created_at, sent_on, and resolved_at fields are intended for backfilling offers managed outside Greenhouse; resolved_at updates are normalized to noon UTC on the supplied date. opening_id must be an open opening on the application's job that no other unresolved offer holds, and can only be set to null when your organization doesn't require an opening on offers. custom_fields entries set values for the offer's offer custom fields (including compensation components); only fields configured on the application's hiring plan apply. Offers carry private compensation data, so writing them is gated separately from the harvest:offers:update scope: when the access token includes a sub claim, the Site Admin it names must also hold the "See private notes, private fields, salary info, manage offers, request approval, and approve jobs/offers" advanced permission, or the request is rejected with 403 Forbidden. Tokens issued without a sub claim act as your integration user and are not subject to it.
Request
- Base URLhttps://harvest.greenhouse.io
- URLhttps://harvest.greenhouse.io/v3/offers/{id}
- Auth
- OAuth 2Authorization code: https://auth.greenhouse.io/authorizeClient credentialsToken URL: https://auth.greenhouse.io/token scopes: harvest:offers:update
- or HTTP bearer
Path parameters
Request body
Response
Successful
Changes
No recorded changes to this operation across all 1 revision of this API.