Update a marketplace listing
Change the name, description, or installable config of a listing your organization authored. Every field is optional — omit one to leave it unchanged. Set status to pending_review to submit the listing for approval, or back to draft to pull it out of the review queue. You cannot set status to published yourself: only a platform reviewer approves a listing. Requires the owner, admin, or developer role.
Authorizations
Dashboard JWT token from Clerk
Headers
Stripe-style idempotency token. Pass a stable, client-generated value (1-255 chars) to dedupe retries on transient timeouts. The same key+credential+path replays the original response for 24h on 2xx (5min on 4xx, 30s on 5xx). Returns 409 if a concurrent request with the same key is already in flight; replayed responses include the Idempotency-Replay: true response header.
1 - 255Sandbox opt-in for Clerk-session-authenticated requests. Set to true to route the call through the test-mode pipeline: no real provider delivery, no credits deducted, response meta.test_mode: true. Ignored for live API keys (dv_live_sk_*) — server-to-server clients must use a test-prefixed key (dv_test_sk_*) to exercise sandbox. Test-prefixed keys unconditionally enable sandbox regardless of this header.
true, false Path Parameters
Marketplace listing identifier, as returned by GET /marketplace.
Body
New listing name.
New listing description.
Replacement installable payload. Publicly readable once the listing is published, so it must not contain secrets.
Lifecycle status you are moving the listing to: draft or pending_review. published is reviewer-only; rejected is written by the review decision.
Response
The updated listing, wrapped in the standard { data, meta } envelope.
The updated listing, wrapped in the standard { data, meta } envelope.