> ## Documentation Index > Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt > Use this file to discover all available pages before exploring further. # Developer Marketplace console walkthrough > Use the Developer Marketplace page to browse, install, and publish flow templates, integrations, and agent templates from the dashboard. # Developer Marketplace console walkthrough The Developer Marketplace puts published flow templates, integrations, and agent templates in one dashboard surface. Use it when you want to inspect a listing and install it without writing a request, or when you want to submit a resource for moderation. You need an authenticated workspace session to install or publish. The session must have the `owner`, `admin`, or `developer` role. Public catalog reads do not require a role. ## Open the unified marketplace 1. Sign in to your workspace. 2. Open **Developer → Marketplace**. 3. Choose **Browse** to find published listings, or **My listings** to track listings your workspace submitted. The Browse view has one search field and type tabs for **Flow templates**, **Integrations**, and **Agent templates**. **All** shows the complete published catalog. The same type tabs are available in **My listings**, where the cards also show the moderation status of your own listings. ## Browse and filter listings Enter a name or keyword in the search field, then choose a type tab to narrow the results. The page loads the public marketplace list and keeps the selected type in the request: ```http theme={null} GET /api/v1/marketplace?type=flow_template ``` The available type values are `flow_template`, `integration`, and `agent_template`. The **All** view omits `type`: ```http theme={null} GET /api/v1/marketplace ``` The list is paginated. The screen's page controls carry the API response's `limit` and `cursor` values forward, so the next request is equivalent to: ```http theme={null} GET /api/v1/marketplace?type=integration&limit=25&cursor= ``` Use the cursor from `meta.pagination.cursor` for the next page. A list row contains the listing name, type, description, install count, author, and status. The public list contains published listings only. ## Inspect a listing Select a listing card to open its details. The detail view shows the same public resource returned by: ```http theme={null} GET /api/v1/marketplace/:id ``` Review the description, type, install count, and the `config` payload before installing. `config` is the definition that the install copies into your tenant: for example, a flow graph, integration manifest, or agent definition. Do not treat a public listing's configuration as a place for credentials, API keys, or webhook secrets. If a listing is not published, it does not appear in Browse and its detail request returns `404`. To inspect your own unpublished submissions, switch to **My listings** instead. ## Install a listing 1. Open a published listing's details. 2. Confirm that the type and `config` are appropriate for your workspace. 3. Select **Install** in the install dialog. The action starts immediately; there is no separate approval step. The action calls `POST /api/v1/marketplace/:id/install`. It requires an `owner`, `admin`, or `developer` role on the current session. An install is a clone, not a live link: the configuration is copied into your tenant as a tenant-owned resource. Changes to the public listing do not change the copy you installed. The resource created depends on the listing type. An agent template creates a new agent in your tenant; flow templates and integrations copy their configuration into your tenant's corresponding resource. Review the new resource before using it in production. For request examples, retry behavior, and the complete install contract, see [Browse, install, and publish marketplace templates](/guides/marketplace-browse-install-publish). The dashboard and API use the same endpoint and role gate. ## Publish your own listing Use **Publish to marketplace** from the Browse or My listings view. The publish dialog asks for: * **Type**: `flow_template` or `integration`. * **Name**: the listing name. * **Description**: what the resource does and who should install it. * **Config (JSON)**: the optional template definition or integration manifest. Select **Save as draft** to submit the following payload through `POST /api/v1/marketplace`: ```json theme={null} { "type": "flow_template", "name": "Welcome series", "description": "A three-step welcome flow for new contacts.", "config": { "steps": [] } } ``` The dialog saves the listing as `draft`. Open **My listings** to review it, edit it, and submit it for moderation. The lifecycle is: ```text theme={null} draft → pending_review → published | rejected ``` A moderator, not the submitting workspace, decides `published` or `rejected`. Track each status in the **My listings** view or with the author-scoped endpoint: ```http theme={null} GET /api/v1/marketplace/mine?status=pending_review ``` The `status` values are `draft`, `pending_review`, `published`, and `rejected`. If a listing is rejected, read the reviewer's notes on its card, update the listing, and submit it again. Keep credentials out of `config`; anything in a published configuration can be read as part of the public listing detail. ## Choose the console or the API Use the console when you are exploring listings, reviewing a configuration before installation, or submitting one listing interactively. Use the API when you need a repeatable install, want to page through the catalog from a script, or are publishing as part of a deployment workflow. Both surfaces use the same endpoints, role gates, tenant ownership rules, and moderation lifecycle. The console is not a separate marketplace: it is a dashboard client for the public list and detail, install, create, update, and author-scoped listing endpoints. See [Browse, install, and publish marketplace templates](/guides/marketplace-browse-install-publish) for copy-paste API requests and rate-limit details. ## Troubleshoot common failures ### `403 Forbidden` when installing or publishing The session does not have an allowed workspace role. Check that the signed-in member is an `owner`, `admin`, or `developer`. A viewer or other workspace role cannot install or submit through the write endpoints. Ask a workspace owner to update the member's role, then sign in again and retry. ### `404 Not Found` for a listing The listing is not yet `published`, or the id is incorrect. Public list and detail requests intentionally hide `draft`, `pending_review`, and `rejected` listings. If you submitted the listing, find it under **My listings** or query `/api/v1/marketplace/mine?status=...` rather than the public detail route. ### My draft is missing from Browse Browse is the published catalog. Switch to **My listings**, select the relevant type tab, and check the status badge. A draft becomes visible to other workspaces only after moderation publishes it. ## Related guides * [Browse, install, and publish marketplace templates](/guides/marketplace-browse-install-publish) — API requests, install semantics, publishing, and rate limits * [Moderate agent template submissions](/guides/agents-marketplace-moderation) — platform-owner moderation for agent template submissions This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.