marketplace

PUT `/v1/marketplace/listings/{listing_id}/packages`

Replace the whole package list.

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X PUT https://api.zinndigital.com/v1/marketplace/listings/{listing_id}/packages \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "packages": <object[]> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Whole-list, like the field schema and for the same reason: per-package create/delete reopens the read-then-write race defect **D824** recorded, and position ordering only means anything as a set. The cap is `Marketplace.max_packages` — a ROW an operator can change, not a database constraint that would need a migration (CLAUDE.md §2.35).

Parameters

Name	Type	Required	What it is
`listing_id (path)`	`string`	Yes	—

Request body

Name	Type	Required	What it is
`packages`	`object[]`	Yes	—

Response

Name	Type	Required	What it is
`data`	`MarketplacePackage[]`	Yes	—
`total`	`integer`	Yes	—
`max_packages`	`integer`	Yes	This vertical's cap, from a row an operator can change.
`permitted_billing_modes`	`MarketplaceBillingMode[]`	No	What this listing type allows. The form is TOLD rather than guessing: a UI that hardcoded both modes would render a control whose every submission is refused.
`permitted_billing_intervals`	`string<monthly, annual>[]`	No	—

Errors this endpoint can return

401 · 404 · 422

PUT /v1/marketplace/listings/{listing_id}/packages