> ## Documentation Index > Fetch the complete documentation index at: https://docs.whop.com/llms.txt > Use this file to discover all available pages before exploring further. # List Workforce Bounties > Lists workforce bounties visible to the credential. Account API keys return the account's bounties, scheduled drafts included; user tokens return the bounties the user can see and work. Pass account_id to view one account's bounties as a team member (or a connected account of the caller's), or user_id (your own) to list the bounties you participated in. ## OpenAPI ````yaml /openapi/api-v1-native.json get /workforce/bounties openapi: 3.1.0 info: description: >- The Whop REST API. Please see https://docs.whop.com/developer/api/getting-started for more details. termsOfService: https://whop.com/tos-developer-api/ title: Whop API version: 1.0.0 x-api-version-date: 2026-07-08-1 servers: - description: Production Whop API url: https://api.whop.com/api/v1 - description: Sandbox Whop API url: https://sandbox-api.whop.com/api/v1 security: [] tags: - description: > An Account represents a person or business on Whop that can have its own profile, wallet, and account-scoped settings. Use accounts for customers, creators, merchants, sellers, or connected businesses your integration supports. Use the Accounts API to create accounts, list accounts visible to your credentials, retrieve or update an account, and retrieve the account associated with the current API key. name: Accounts x-whop-summary: 'A business on Whop: profile, wallet, capabilities, settings.' - description: > A User represents a person on Whop. Users have a public profile and can buy products, join accounts, and access experiences. Use the Users API to search for users, retrieve or update profiles, and check whether a user has access to an account, product, or experience. name: Users x-whop-summary: 'A person on Whop: profile and connected identities.' - description: > Stats represent aggregated activity for an account over time. They help you understand revenue, transactions, disputes, members, referrals, and advertising performance across reporting periods like days, weeks, or months. Use the Stats API to list available metrics and their filterable properties, then retrieve time-series values for a date range. name: Stats x-whop-summary: Aggregated account time series for reporting. - description: > A Ledger Activity row is a single financial event on an account's ledger — a payment, withdrawal, refund, transfer, on-chain deposit, swap, or card transaction. Each row is derived from the underlying ledger lines and carries a typed `resource` and `source` so you can present and link the event without extra lookups. Use Ledger Activity to build a statement or transaction feed for an account or user. Reconcile against your own records with `amount` (signed, in the currency's smallest precision units) and `posted_at`, and use `available_at` to know when inflows became withdrawable. name: Ledgers x-whop-summary: The activity feed behind an account or user's balance. - description: > Payouts represent money sent from an account or user balance to an external destination, such as a bank account, wallet, or other saved payout method. Use the Payouts API to create payouts from stablecoin accounts, list payout history for accounts or users, monitor payout statuses, and show expected arrival details for funds leaving Whop. name: Payouts x-whop-summary: Send money from a balance to a bank or wallet. - description: > Cards represent Whop-issued virtual payment cards that spend from an account or user balance. Cards can be assigned to cardholders and configured with spending limits for controlled spending. Use the Cards API to issue cards, list cards for an account or user, and retrieve active card details such as the card number and CVC. name: Cards x-whop-summary: Issue cards that spend from a balance. - description: > Transfers move value between identities on Whop. They are used for account-to-account money movement, user payouts inside Whop, crypto transfers, and claim links depending on the destination type. Use the Transfers API to create a transfer, list previous transfers, and retrieve a transfer by ID when reconciling money movement between accounts or users. name: Transfers x-whop-summary: Move funds between Whop accounts and users. - description: > Deposits describe ways to add funds to an account balance, including hosted deposit pages, bank deposit instructions, and supported crypto wallet addresses. Use the Deposits API to create deposit instructions for an account and retrieve existing bank deposit activity. name: Deposits x-whop-summary: Add funds to a balance. - description: > Swaps convert value between supported tokens, chains, or wallet destinations for an account. A swap quote describes the expected output, fees, and approval requirements before you create the swap. Use the Swaps API to quote a conversion, create the swap, list recent swaps, and retrieve status until the transaction completes. name: Swaps x-whop-summary: Convert a balance between currencies. - description: > A Verification represents an identity review for a person or business. Accounts and users complete verification when Whop needs to confirm who they are before enabling payouts or compliance-sensitive workflows. Use the Verifications API to start or resume a hosted verification session, check review status, and submit requested details or documents. If `requested_information` contains items, submit answers with [Update Verification](/api-reference/beta/verifications/update-verification). name: Verifications x-whop-summary: Identity review required before payouts and card issuing. - description: > A Product is a digital good or service sold on Whop. Products may contain plans for pricing and/or experiences for content delivery. Use the Products API to create products, list products visible to your credentials, retrieve product details, update product metadata or merchandising fields, and delete products that should no longer be sold. name: Products x-whop-summary: The things you sell. Each owns plans and a store page. - description: > A Plan defines how customers buy a product. It controls pricing, billing cadence, availability, tax behavior, checkout fields, and purchase visibility. Use the Plans API to create plans for products, list existing plans, retrieve or update plan configuration, calculate tax for checkout, and delete plans that should no longer be offered. name: Plans x-whop-summary: 'Pricing for a product: one-time, recurring, trials, stock.' - description: > A Checkout Configuration is a reusable checkout link owned by an account. In `payment` mode it sells a specific plan; in `setup` mode it collects and saves payment details without charging. Each configuration can also override which payment methods are accepted and how 3D Secure is enforced for that checkout. Use the Checkout Configurations API to create checkout links for an existing or inline plan, list configurations for an account, retrieve the configuration behind a checkout URL, and delete links that should no longer be used. name: Checkout Configurations x-whop-summary: Turn a plan into a shareable, prefilled checkout link. - description: > The Referrals API covers your Whop partner activity: the users you referred onto Whop, the businesses you referred and the earnings generated from their processing volume, and the partner leaderboard. Use it to enroll as a Whop partner, list the users you referred, list your referred businesses and review their earnings, and see the partner leaderboard. name: Partners x-whop-summary: >- The users and businesses you referred to Whop, and what you earn from them. - description: > A Workforce Bounty is a paid task posted by an account or user. The reward is held in escrow when the bounty publishes, workers submit proof of completed work, and each accepted submission is paid out until every winner slot fills. Use the Workforce Bounties API to list an account's bounties for reporting or dashboards, list the bounties a user can work or has participated in, and retrieve a single bounty by ID. name: Workforce Bounties x-whop-summary: Paid tasks with reviewed submissions and escrowed rewards. - description: > A Person represents a visitor or customer of an account, assembled from [pixel events](/api-reference/beta/events/event) and purchase activity — ad clicks, storefront visits, and checkouts. Use the People API to list the people of an account and retrieve a single person. name: People x-whop-summary: Visitors and customers of an account, aggregated from pixel events. - description: > An Event records conversion or engagement activity for an account, such as page views, purchases, or leads. Each event ties the action to the [person](/api-reference/beta/people/person) who took it, so activity can be attributed to the ads and links that drove it. Use the Events API to send new tracking events and list the events recorded for a person. name: Events x-whop-summary: Conversion and engagement events tracked for attribution. - description: > An Ad is the individual creative unit delivered by an [ad group](/api-reference/beta/ad-groups/ad-group). It holds the copy, creative assets, and destination URL for one ad. Use the Ads API to list ads for an account, create ads inside ad groups, retrieve or update creative details, delete ads that should stop running, and pause or resume delivery. name: Ads x-whop-summary: 'The creative: copy, assets, and destination URL.' - description: > An Ad Campaign is the top-level container for paid ads on an ad network. It sets the platform, objective, and budget strategy shared by its [ad groups](/api-reference/beta/ad-groups/ad-group) and ads. Use the Ad Campaigns API to create campaigns, list campaigns for an account, retrieve or update campaign settings, and pause or resume campaign delivery. name: Ad Campaigns x-whop-summary: Platform, objective, and budget for a set of ads. - description: > An Ad Group sits inside an [ad campaign](/api-reference/beta/ad-campaigns/ad-campaign) and controls delivery for [ads](/api-reference/beta/ads/ad). It sets the audience, placements, schedule, budget, and optimization goal for its ads. Use the Ad Groups API to create ad groups in campaigns, list or retrieve targeting and delivery settings, update budgets or targeting, delete groups that should stop running, and pause or resume delivery. name: Ad Groups x-whop-summary: Audience, placements, and schedule within a campaign. - description: > An Audience represents a customer list uploaded to Whop for ad targeting. Audiences belong to an account and sync to supported ad platforms as custom audiences. Use the Audiences API to create audiences from CSV uploads, monitor processing status, and list or delete audiences for an account. Created audiences are usable for targeting after processing reaches `ready` or `partial`. name: Audiences x-whop-summary: Reusable targeting lists for ad groups. - description: > A Media Asset is an AI-generated image or video created from a prompt and billed from an account balance. When generation finishes, the asset includes a file that can be attached anywhere Whop accepts files. Use the Media API to start a generation job and retrieve the asset while it processes or after it is ready. name: Media x-whop-summary: >- AI-generated assets, billed from a balance, attachable wherever files are accepted. - description: > A Social Account represents an external profile connected to a Whop account or user, such as a Facebook page or Instagram account. Connecting a social account lets Whop run [ads](/api-reference/beta/ads/ad) under that profile's identity and promote its existing posts. Use the Social Accounts API to list connected accounts, create a Whop-managed Facebook page, start an OAuth connection, disconnect a social account, and list a connected profile's posts. name: Social Accounts x-whop-summary: Connected Facebook and Instagram accounts that run ads. - description: > An App is software you build on Whop. It can be a hosted web app served at `.whop.app` or an API integration installed as an experience, and it belongs to the account that owns its credentials, settings, builds, and runtime logs. Use the Apps API to manage app configuration and, for hosted apps, read server runtime logs for console output, uncaught exceptions, and failed requests. Logs are retained for 7 days and can be filtered by build, level, time window, and message text. name: Apps x-whop-summary: 'Apps you build on Whop: metadata, hosted builds, runtime logs.' paths: /workforce/bounties: parameters: - $ref: '#/components/parameters/ApiVersionDate' get: tags: - Workforce Bounties summary: List Workforce Bounties description: >- Lists workforce bounties visible to the credential. Account API keys return the account's bounties, scheduled drafts included; user tokens return the bounties the user can see and work. Pass account_id to view one account's bounties as a team member (or a connected account of the caller's), or user_id (your own) to list the bounties you participated in. operationId: listWorkforceBounties parameters: - description: >- Scope the list to this account (`biz_` tag). Requires read access to the account; account API keys may pass their own account or a connected account. in: query name: account_id required: false schema: type: string - description: >- List the bounties this user participated in (`user_` tag). Must be the authenticated user. in: query name: user_id required: false schema: type: string - description: Filter by lifecycle state. in: query name: status required: false schema: enum: - scheduled - open - closed - completed - canceled type: string - description: Substring match on the bounty title or ID. in: query name: query required: false schema: type: string - description: Only bounties created after this ISO 8601 timestamp. in: query name: created_after required: false schema: type: string - description: Only bounties created before this ISO 8601 timestamp. in: query name: created_before required: false schema: type: string - description: Sort field. in: query name: order required: false schema: default: created_at enum: - created_at - gross_paid_out_amount type: string - description: Sort direction. in: query name: direction required: false schema: default: desc enum: - asc - desc type: string - description: Number of bounties to return from the start of the window. in: query name: first required: false schema: default: 20 maximum: 100 type: integer - description: Cursor to paginate forwards from. in: query name: after required: false schema: type: string - description: Number of bounties to return from the end of the window. in: query name: last required: false schema: maximum: 100 type: integer - description: Cursor to paginate backwards from. in: query name: before required: false schema: type: string responses: '200': content: application/json: schema: properties: data: items: $ref: '#/components/schemas/WorkforceBountyListItem' type: array page_info: properties: end_cursor: type: - string - 'null' has_next_page: type: boolean has_previous_page: type: boolean start_cursor: type: - string - 'null' required: - end_cursor - start_cursor - has_next_page - has_previous_page type: object required: - data - page_info type: object description: workforce bounties listed '400': $ref: '#/components/responses/InvalidParameters' description: invalid status filter '401': $ref: '#/components/responses/Unauthorized' description: missing credentials '403': $ref: '#/components/responses/Forbidden' description: credential lacks the bounty-read scope security: - bearerAuth: - bounty:basic:read components: parameters: ApiVersionDate: description: Pins the request to a dated API version. in: header name: Api-Version-Date required: false schema: example: 2026-07-08-1 type: string schemas: WorkforceBountyListItem: properties: accepted_submissions_count: description: Submissions accepted so far. type: integer accepted_submissions_limit: description: Number of submissions that can be accepted (winner slots). type: integer allowed_country_codes: items: description: >- Countries whose residents can work the bounty, as ISO 3166 alpha-2 codes. Empty means worldwide. type: string type: array budget_amount: description: >- Total gross budget committed to the bounty: `gross_reward_amount` times `accepted_submissions_limit`. type: number business_goal_type: description: What the poster wants the work to achieve. enum: - clipping - post_engagement - owned_account_growth - ugc_content - local_activation - other - null example: clipping type: - string - 'null' created_at: description: When the bounty was created, as an ISO 8601 timestamp. type: string currency: description: >- Currency for all amounts on the bounty, as a lowercase ISO 4217 code. type: string experience_id: description: >- Experience the bounty is hosted in, prefixed `exp_`. Null for platform-wide bounties; may belong to a different account than the funder. type: - string - 'null' funding_account: description: >- The account whose balance funds the bounty pool, or `null` when a user funds it personally. May differ from the account hosting `experience_id`. oneOf: - $ref: '#/components/schemas/AccountSummary' - type: 'null' gross_paid_out_amount: description: >- 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. type: number gross_reward_amount: description: >- Gross bounty-pool amount allocated per accepted submission, in whole currency units. type: number id: description: Bounty ID, prefixed `bnty_`. type: string poster: $ref: '#/components/schemas/UserSummary' description: The user who posted the bounty. scheduled_frequency: description: >- How often the schedule creates a new bounty. Each occurrence is a separate bounty; the original is not republished. enum: - once - hourly - daily - weekly - monthly - null example: once type: - string - 'null' scheduled_publish_at: description: >- 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. type: - string - 'null' spots_remaining: description: >- Unfilled winner capacity: `accepted_submissions_limit` minus `accepted_submissions_count`, clamped to zero. Not a signal that the bounty currently accepts new claims. type: integer status: description: >- 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. enum: - scheduled - open - closed - completed - canceled example: scheduled type: string submissions_closed_at: description: >- 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. type: - string - 'null' title: description: Short name of the task shown to workers. type: string unresolved_submissions_count: description: >- Submissions still awaiting an outcome: in progress or pending review. type: integer updated_at: description: When the bounty was last updated, as an ISO 8601 timestamp. type: string required: - id - title - status - currency - gross_reward_amount - budget_amount - gross_paid_out_amount - accepted_submissions_limit - accepted_submissions_count - unresolved_submissions_count - spots_remaining - business_goal_type - allowed_country_codes - submissions_closed_at - scheduled_publish_at - scheduled_frequency - experience_id - created_at - updated_at - poster - funding_account type: object AccountSummary: properties: id: description: Account ID, prefixed `biz_`. type: string title: description: Account display name. type: string required: - id - title type: object UserSummary: properties: id: description: User ID, prefixed `user_`. type: string name: description: Display name. type: - string - 'null' profile_picture: $ref: '#/components/schemas/UserProfilePicture' description: >- Avatar wrapper; its `url` is always present, using a generated placeholder when the user set no picture. username: description: Public username. type: string required: - id - username - name - profile_picture type: object V1ErrorResponse: properties: error: properties: message: description: Human-readable error message. type: string type: description: Machine-readable error code. type: string required: - type - message type: object required: - error type: object UserProfilePicture: properties: url: description: >- Avatar image URL. Always present — a generated placeholder when the user set no picture. type: string required: - url type: object responses: InvalidParameters: content: application/json: schema: $ref: '#/components/schemas/V1ErrorResponse' description: Invalid Parameters Unauthorized: content: application/json: schema: $ref: '#/components/schemas/V1ErrorResponse' description: Unauthorized Forbidden: content: application/json: schema: $ref: '#/components/schemas/V1ErrorResponse' description: Forbidden securitySchemes: bearerAuth: bearerFormat: auth-scheme description: >- 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 ***************************` scheme: bearer type: http ````