Create Bounty Submission
Submits work to a workforce bounty. Include a deliverable payload matching the bounty’s accepted deliverable type: content_url for link-based bounties, media for upload-based bounties. The submission lands directly in review. Requires a user credential — account API keys cannot author submissions.
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"
Body
Response
submission created with an inline deliverable
The bounty the work was submitted to, prefixed bnty_.
Written proof the worker submitted with their work.
When the submission was created, as an ISO 8601 timestamp.
Deliverable shape the worker submitted. content_url is links to posted content; media is uploaded files. null on submissions authored before deliverable types existed.
content_url, media, null "content_url"
The submitted content links. Only set when deliverable_type is content_url.
Why the submission was denied, when a presentable reason exists. Always null unless status is denied.
Submission ID, prefixed btys_.
When the submission was approved or denied, as an ISO 8601 timestamp. null until then.
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.

