Skip to main content
The Marketplace API is for publishers managing their listings and releases. Its base URL is:
Customers continue to browse, search, inspect published content, and manage installations through the REST API at /rest/v1/marketplace.

​
Use your existing credentials

Both APIs accept the same organization-scoped OAuth access tokens and personal tokens. Use the same API host and login; there is no separate Marketplace account or token exchange. See authentication. Scopes do not grant publisher ownership or enable publishing for an account. The authenticated member must also have the corresponding publisher permissions. All writes follow the shared idempotency and concurrency rules.

​
Find your listings

The publisher listing collection includes the listings you manage, including unpublished drafts:
For the customer catalog, use GET /rest/v1/marketplace/listings. Public categories and publisher profiles also remain in the REST API.

​
Prepare and publish a release

  1. Create a listing with POST /marketplace/v1/listings, supplying an authorized publisher_id. The response contains the listing and its initial draft release.
  2. Find source content with GET /marketplace/v1/sources?kind=skill, then add items to the draft. Supported source kinds are skill, automation, rule, and knowledge.
  3. Update the draft’s metadata, items, and artwork. Fetch the parent release’s current ETag before each conditional write.
  4. Validate with POST /marketplace/v1/releases/{id}/validate, then publish with POST /marketplace/v1/releases/{id}/publish.
  5. For a later version, create a new draft with POST /marketplace/v1/releases and its listing_id.
The reference below documents each request body, permission scope, and response. Publishing requires marketplace:publish; the default CLI login does not request that scope. Authorize it explicitly when needed.

​
Use the CLI

Command names stay the same. The CLI selects the API for the operation:
CLI 0.1.3 or later uses the new routes. Existing released clients continue to work through deprecated publisher routes during rollout. New integrations should use /marketplace/v1 for management. Read the CLI reference or download the Marketplace OpenAPI specification.