Retrieve Workforce Bounty
Retrieves one workforce bounty by ID. The bounty must be visible to the credential; bounties outside the caller’s scope return 404.
Authorizations
A company API key, company scoped JWT, app API key, or user OAuth token. You must prepend your key/token with the word 'Bearer', which will look like Bearer ***************************
Headers
Pins the request to a dated API version.
"2026-07-08-1"
Path Parameters
Bounty ID (bnty_ tag).
Response
workforce bounty retrieved
Submissions accepted so far.
Number of submissions that can be accepted (winner slots).
Countries whose residents can work the bounty, as ISO 3166 alpha-2 codes. Empty means worldwide.
Total gross budget committed to the bounty: gross_reward_amount times accepted_submissions_limit.
What the poster wants the work to achieve.
clipping, post_engagement, owned_account_growth, ugc_content, local_activation, other, null "clipping"
When the bounty was created, as an ISO 8601 timestamp.
Currency for all amounts on the bounty, as a lowercase ISO 4217 code.
Full task instructions shown to workers.
Experience the bounty is hosted in, prefixed exp_. Null for platform-wide bounties; may belong to a different account than the funder.
The account whose balance funds the bounty pool, or null when a user funds it personally. May differ from the account hosting experience_id.
Gross amount paid out from the bounty pool across accepted submissions — worker payouts, platform fees, and affiliate shares together. Tips and reviewer rewards are excluded.
Gross bounty-pool amount allocated per accepted submission, in whole currency units.
Bounty ID, prefixed bnty_.
The user who posted the bounty.
How often the schedule creates a new bounty. Each occurrence is a separate bounty; the original is not republished.
once, hourly, daily, weekly, monthly, null "once"
When a scheduled bounty will publish, as an ISO 8601 timestamp. Null once published, for bounties that were never scheduled, and for terminally failed drafts parked for manual rescheduling.
Unfilled winner capacity: accepted_submissions_limit minus accepted_submissions_count, clamped to zero. Not a signal that the bounty currently accepts new claims.
Lifecycle state. scheduled bounties are unpublished drafts, visible to their poster and the account's authorized managers; open bounties accept new submissions; closed bounties are live but no longer accept new submissions; completed bounties paid out every winner slot; canceled bounties ended before filling their slots.
scheduled, open, closed, completed, canceled "scheduled"
When new submissions were explicitly stopped, as an ISO 8601 timestamp. Null when submissions were never explicitly stopped — including closed or completed bounties that simply filled every winner slot.
Short name of the task shown to workers.
Submissions still awaiting an outcome: in progress or pending review.
When the bounty was last updated, as an ISO 8601 timestamp.

