Optional Internal_For internal use by the frontend.
OptionalapproachHow the claim is expected to be completed. This is for display purposes for the frontend.
Available options:
Typically, you will use the in-site approach
OptionalassignAlgorithm to determine the claim number order. Blank is just incrementing claim numbers.
For most cases, you will not need to specify this.
OptionalcacheCache policy for the claim. Only needed for on-demand claims.
OptionalcategoriesThe categories of the claim
Unique claim ID.
OptionalcollectionCollection ID that the claim is for (if applicable - collection claims).
OptionalcreatedThe original creator of the claim
OptionalestimatedEstimated cost for the claim.
OptionalestimatedEstimated time to satisfy the claim's requirements.
OptionallastLast updated timestamp for the claim.
OptionalmanagedThe BitBadges address of the user who is currently managing this
OptionalmanualIf manual distribution is enabled, we do not handle any distribution of claim codes. We leave that up to the claim creator.
Only applicable for on-chain token claims. This is only used in advanced self-hosted cases.
OptionalmetadataMetadata for the claim.
Claim plugins. These are the criteria that must pass for a user to claim.
OptionalrewardsRewards for the claim.
OptionalsatisfyCustom satisfaction logic.
If left blank, all plugins must pass for the claim to be satisfied. Otherwise, you can specify a custom method to determine if the claim is satisfied.
OptionalseedSeed code for the claim. Only used for on-chain token claims.
This is how we produce all reserved codes for the on-chain merkle challenge / proofs.
OptionalshowIf true, the claim will be shown in search results
OptionalstandaloneStandalone claims are not linked with a token or list.
OptionaltrackerThe tracker details for the claim (if applicable - collection claims).
The version of the claim.
Whether the claim fetch includes private params