App Store listing - PlatformDTC

Public apps are listed in the App Store at platformdtc.com/apps. An app appears there only when all of these hold:

distribution is public,
it has an approved version,
its listing is published (listings are reviewed like versions), and
the app is active (not delisted or suspended).

Custom-distribution apps have no listing; you share their install link directly.

Made by PlatformDTC

Some listings are PlatformDTC’s own features, such as POS or the support inbox. They carry a Made by PlatformDTC label (made_by_platform: true in the catalog API) and follow the same listing rules as partner apps. Every store already has them, so there is nothing to install: the listing’s Open button goes straight to the feature in the dashboard (launch_path), and the OAuth, token and install endpoints answer 400 BUILTIN_APP_NO_INSTALL for them. Merchants can rate them once their store is 48 hours old.

Edit and submit a listing

Edit the listing in the partner dashboard (your app → Listing), or through the API:

Call	Does
`GET /partner/apps/{id}/listing?locale=en`	The open draft, or a new draft copied from the published listing.
`PUT /partner/apps/{id}/listing`	Save the draft.
`POST /partner/apps/{id}/listing/media`	Upload a screenshot or video (multipart). `PATCH` / `DELETE …/listing/media/{mid}` to change or remove one.
`POST /partner/apps/{id}/listing/submit`	Send the draft to review. When it is approved it replaces the published listing.

Paths are under https://api.platformdtc.com/api/v1/appstore. Your published listing stays live while a new draft is in review.

Listing fields

Field	Required to submit	Rules
Tagline	yes	At most 100 characters. Shown on the app card.
Intro	yes	At most 500 characters. The first paragraph of your app page.
Icon	yes
Screenshots	yes, at least 3	Every image needs alt text.
Privacy policy URL	yes
Primary category	yes	Pick from the category tree (`GET /categories`). You may add further categories.
Details	no	Markdown.
Features	no	At most 8.
Search keywords	no	At most 5.
Support email or support URL	yes (one of them)	How merchants reach you. At least one is required to submit.
Website URL, demo store URL	no	Shown on your app page when set; nothing is shown when empty.
Languages, works with	no

Pricing shown on your app page comes from your app’s pricing plans, not from listing text.

Automated review requirements

When you submit a version or a listing, these checks run automatically and appear in the review case with their result. A failed check blocks approval until it passes or a reviewer waives it.

Requirement	Passes when	How to pass
`listing_complete`	The listing has a tagline, an intro, an icon, at least 3 screenshots each with alt text, a privacy policy URL, a primary category and a support email or URL.	Fill every field marked required above.
`redirect_uris_https`	Every redirect URI uses `https`.	Replace any `http://` or localhost URL left from `dtc app dev`, then `dtc app config push`.
`webhook_hmac_rejects_invalid`	A webhook sent to your endpoint signed with the wrong secret is answered with `401`.	Verify the signature on every request before doing anything else, and return `401` when it does not match.
`agent_tools_reject_invalid_signature`	Every agent tool your version declares answers `401` to a call signed with the wrong secret. Runs only when the version declares tools.	Verify `X-PlatformDTC-Signature` before reading the arguments, and return `401` when it does not match.
`compliance_webhooks_reachable`	Each of `customers/data_request`, `customers/redact` and `shop/redact` answers `2xx`, or `401` for a bad signature.	Declare all three compliance topics and deploy handlers for them.
`scope_justifications_complete`	Every requested scope has a non-empty justification.	Add one per scope under `[access_scopes.justifications]`.
`app_url_reachable`	Your app URL responds.	Make sure `application_url` is deployed and publicly reachable, not a tunnel.
`pricing_matches_listing`	The pricing on your listing matches your active pricing plans.	Describe pricing only through pricing plans, and keep listing text consistent with them.

Reviewers also check the app by hand; see Versions & review for what gets an app rejected.

Ratings

A merchant can rate your app 48 hours after installing it, including after they uninstall.
One rating per store; the merchant can edit or delete it.
Ratings are 1–5 stars with a written review.
You can post one public reply per rating (POST /partner/ratings/{id}/reply).
Ratings can be reported; the trust & safety team may hide a rating that breaks the rules.

Apps with no ratings show no stars.

Built for PlatformDTC

The Built for PlatformDTC badge is awarded automatically. An app earns it when it meets all of these, and loses it when it no longer does:

at least 50 active installs,
an average rating of 4.0 or higher from at least 5 ratings,
a 30-day uninstall rate below 20%,
a webhook endpoint that has stayed healthy for 30 days,
an approved version less than 180 days old,
no open trust & safety enforcement.

Merchants can filter the App Store to badged apps. PlatformDTC takes 0% of your app revenue. You keep everything merchants pay for your app, and payment processing fees aren’t taken out of your earnings. Merchants are billed through PlatformDTC; your earnings are paid to your Stripe Connect account on the 1st and 16th of each month. Payouts are held until a payout account is connected. Refunds are deducted from your earnings.

​Made by PlatformDTC

​Edit and submit a listing

​Listing fields

​Automated review requirements

​Ratings

​Built for PlatformDTC

​Revenue share