Format
A manifest is a JSON object with a format version and a list of fields.Common field properties
All field types have these properties.The name of the field. Use 1 to 64 characters: a to z first, then a to z, 0 to 9, or
_. Each key must be unique in the manifest.Field types
Text and secret
Number
Numbers are whole numbers. For an amount, use minor units, for example cents.Select
A select field has a fixedoptions list, or options_url for dynamic options. Give one of the two, not both.
Up to 200 items. Each item has
value and label, each 1 to 100 characters. Values must be unique.An HTTPS URL on a public host name. It cannot have a port, credentials, or a fragment. Up to 2048 characters.
Lets the merchant pick more than one item. The value is then an array of strings. This also applies to
events, products, and currencies.Dodo pickers
events, products, and currencies show a picker that Dodo Payments fills for the merchant. A products field has no default.
Limits
Example manifest
Upload a manifest
These endpoints are in the developer API that the developer dashboard uses. You can also use the manifest editor on the app page.The examples use
$DEVELOPER_API_URL and $DEVELOPER_API_TOKEN as placeholders for the developer API base URL and your developer credentials.Preview
Checks a manifest and shows the review result. It does not store anything.The review reason codes of the change.
Upload
Stores a new version. The body is the raw manifest, at most 64 KiB. Only an owner or an admin of the app can upload.List versions
GET /apps/{id}/manifests returns { "items": [...] }. Each item has id, app_id, version, status, manifest, review_reasons, created_by_user_id, live_at, created_at, and updated_at.
Versions
Each upload creates a new version number for the app. A live version never changes.
An installation moves to the newest live version when the merchant saves. Until then,
manifest_version in the settings response is older than live_manifest_version.
If your app is private, or has not been listed yet, every version goes live at once. For a listed app, a version with no review reason goes live at once, and a version with a reason goes to review.
Changes that need review
A stored value that fails a stricter rule is listed in
invalid_keys. The installation shows Action needed until the merchant fixes it.
These changes need no review: new labels, help text, order, defaults, a new optional field that is not secret, and a removed field. Values of a removed field stay stored, but your app no longer receives them.