Create Bounty Submission
Creates a submission on a workforce bounty. Include a deliverable payload — any combination of links and uploaded files, with at least one of the two — and the submission goes straight to review; create is the only step. For data_capture bounties, omit the deliverable: this starts a claimed attempt whose proof accumulates server-side, and the separate submit endpoint sends it to review once complete. Requires a user credential — account API keys cannot author submissions.
Authorizations
An Account API key, account-scoped JWT, App API key, or user OAuth token. Prepend the key or token with Bearer, for example Bearer ***************************.
Headers
A unique key that makes this request safe to retry. See Idempotent requests.
255"d9105228-4a08-46b1-8b91-42fed586d383"
Pins the request to a dated API version.
"2026-08-05-1"
Body
The bounty to submit to (bnty_ tag).
Affiliate code crediting the referrer, when the worker arrived through one.
The submitted work. Combine urls, file_ids, and caption freely; at least one link or file is required.
Optional capture metadata describing where and how the footage was recorded. Persisted on the submission. On a data_capture bounty every field except fov is required whenever metadata is provided.
Response
submission created with an inline deliverable
The bounty the work was submitted to, prefixed bnty_.
The vendor filename stem Country_City_Site_Station_Operator, derived from the capture metadata. null until every component is present.
Number of verified capture clips accepted for this submission so far. 0 for submissions whose deliverable doesn't accumulate clips.
Total verified duration of accepted capture clips, in whole seconds. 0 for submissions whose deliverable doesn't accumulate clips.
Capture metadata: city the footage was recorded in. null unless capture metadata was provided.
Written proof the worker submitted with their work.
Capture metadata: country the footage was recorded in. null unless capture metadata was provided.
When the submission was created, as an ISO 8601 timestamp.
How the work arrived when it came in through the API in one shot, informational only — read the work from deliverable_urls, files, and capture_clips directly. null for submissions whose proof is a livestream recording, including ones that attached links or files on submit.
content_url, media, data_capture, null "content_url"
Links submitted as work, followed by temporary download URLs for the uploaded files. null when the submission carries neither.
Why the submission was denied, when a presentable reason exists. Always null unless status is denied.
Capture metadata: device the footage was recorded on. null unless capture metadata was provided.
Capture metadata: horizontal field of view in degrees. null when not reported.
Submission ID, prefixed btys_.
Capture metadata: identifier of the person who recorded the footage. null unless capture metadata was provided.
When the submission was approved or denied, as an ISO 8601 timestamp. null until then.
Capture metadata: site or venue the footage was recorded at. null unless capture metadata was provided.
Capture metadata: station or position within the site. null unless capture metadata was provided.
Lifecycle state. in_progress submissions are active attempts that have not submitted proof yet; submitted submissions await review; approved submissions were accepted and paid; denied submissions were rejected.
in_progress, submitted, approved, denied "in_progress"
When proof was submitted for review, as an ISO 8601 timestamp. null while the attempt is in progress.
When the submission was last updated, as an ISO 8601 timestamp.
User who submitted the work.

