Initially, Nexus creates and manages Bounties on your behalf; eventually you will be able to create and manage your own. To get started defining your Bounties, please contact your account manager or ask in a shared Slack or Discord channel.
Bounty properties
Section titled “Bounty properties”| Property | Description |
|---|---|
| Name | Name of the bounty |
imageSrc | URL of the thumbnail image for this bounty |
| Description | Description of the bounty |
| Reward Description | Text description of the bounty rewards |
| Limit | How many times the bounty may be completed (infinite if not set) |
startsAt | Date/time that the bounty becomes available |
endsAt | Date/time that the bounty ends |
| Prerequisites | Bounties that must be completed at least once before this bounty is available |
| Objectives | Requirements for completion |
| Rewards | Rewards offered upon completion |
Objectives
Section titled “Objectives”A bounty may have any number of objectives. Each objective has a type and condition which describe its requirements for completion.
Objective types
Section titled “Objective types”A referral objective completes when the creator receives a specified number of referrals.

An event objective completes after Nexus receives a specific number of events for a given Creator Group Event Code. These objectives reward in-game progress, for either Referral or Creator events.
Referral event objectives
Section titled “Referral event objectives”A Referral Event objective progresses when Nexus receives Creator Group Events originating from a user that has referred a creator.

Creator event objectives
Section titled “Creator event objectives”A Creator Event objective progresses when Nexus receives Creator Group Events that originate from the creator themselves in game.

A Nexus Purchase objective completes when the creator makes a specified number of sales on their Nexus storefront. A Nexus purchase objective type limits which purchases count toward it.
Category purchase objective type
Section titled “Category purchase objective type”SKUs sold on a Nexus storefront may be assigned a category and an objective. The “Category” purchase objective type counts only sales in a given category. For example, if the “Great Game” includes microtransaction SKUs that may be sold on a creator’s Nexus, they would all be assigned a category of “Great Game.” An objective with this category would progress with any purchase of a “Great Game” microtransaction SKU.
Publisher purchase objective type
Section titled “Publisher purchase objective type”Any SKUs you have for sale on Nexus are associated with your Publisher account. An objective with the “Publisher” purchase objective type progresses on a purchase of any of your SKUs.
SKU purchase objective type
Section titled “SKU purchase objective type”An objective with the “SKU” purchase objective type progresses only on the purchase of a SKU in a specified list.
Examples
Section titled “Examples”

An attribution objective completes when the creator receives a specified number of attributions, reaches a specific subtotal across attributions, or earns a specific amount of revenue share through attributions.
Examples
Section titled “Examples”Quantity
Section titled “Quantity”
Amount
Section titled “Amount”
Revenue share
Section titled “Revenue share”
Objective condition
Section titled “Objective condition”An objective carries a condition of either AND or OR. A bounty can mix the two across its objectives.
- A bounty requires every
ANDobjective. - Where it has several
ORobjectives, any one of them satisfies that side. - Where it has both, the bounty completes once the creator finishes all of the
ANDobjectives and at least one of theORobjectives.

Rewards
Section titled “Rewards”A bounty may have any number of rewards. A reward may be of type External, SKU, or Payment.
An external bounty reward is one you provide to the creator yourself, instead of Nexus handling it. For example, this reward type would be used in the event that a user would be automatically awarded some amount of in-game currency upon bounty completion, instead of having Nexus provide them with a key to redeem in-game.
When a creator completes a bounty with an external reward, Nexus notifies you by webhook. The reward also appears in the response from any Bounty Creator Progress API route.
When a creator completes a bounty with a SKU reward, Nexus delivers a key they can redeem for the reward (in-game, Steam, and so on). They retrieve it the same way a buyer retrieves a key after purchasing a SKU from a Nexus store.
A bounty with a payment reward generates a creator transaction for the payment amount. Nexus pays these bounty rewards in its normal monthly payment process.
You will be invoiced monthly for these payments.