canonical: https://jentic.com/apis/apideck.com/ecosystem

# Apideck Ecosystem API

The Apideck Ecosystem API exposes a read-only catalog of integration listings, categories, collections, and products that power Apideck-hosted integration marketplaces. Applications query this API to render an in-product 'integrations' directory without maintaining their own metadata store, including descriptions, logos, and category groupings for each listing. All twelve endpoints are GET operations scoped under a parent ecosystem ID, with listings filterable by category or collection. It is designed for embedded marketplace UIs rather than for connecting to or executing calls against the underlying integrations.

## For AI agents

Read Apideck-managed integration marketplace data - list ecosystems, categories, collections, products, and individual listings to render an embedded integrations directory.

## Scope

Does not authenticate users to integrations, execute calls against connectors, or modify listing metadata - use for read-only marketplace catalog data only.

## Capabilities

- Retrieve a full ecosystem record including branding and metadata by ecosystem ID
- List every integration listing inside an ecosystem with logos, descriptions, and status
- Filter listings by category or by curated collection for marketplace browsing
- Look up a single listing by ID to render an integration detail page
- Walk product groupings to surface multi-app integration bundles
- Page through categories to build a navigation tree for an embedded directory

## Use cases

### Embedded Integrations Marketplace

Render an in-product integrations marketplace inside a SaaS application without managing logos, descriptions, or category metadata yourself. The Ecosystem API serves listings, categories, and collections from a single Apideck-hosted source so the marketplace stays current as new connectors are published. Read-only access keeps integration time short - a directory page can be wired up in a day against the twelve GET endpoints.

Example prompt: Fetch all listings under category 'crm' from ecosystem 'acme-marketplace' and return name, logo URL, and description for each

### Curated Integration Collections

Group related integrations into themed collections (for example 'Sales Stack' or 'Finance Essentials') and surface them on a marketplace homepage. The collections endpoint returns ordered lists of listings curated by the ecosystem owner, so featured groupings can be controlled centrally rather than hard-coded in the front end. Useful for onboarding flows that recommend integrations based on the user's role.

Example prompt: List all collections in ecosystem 'acme-marketplace' and for each collection retrieve its listings sorted by display order

### Category Navigation Tree

Build a side-nav category tree for an integrations directory page. The Ecosystem API exposes categories and the listings under each category, allowing front-end code to render filter chips, faceted search, or a hierarchical browse view. Because the data is centrally managed, taxonomy changes propagate without a deploy.

Example prompt: Retrieve all categories for ecosystem 'acme-marketplace' and return a JSON tree of category name, ID, and child listing count

### AI Agent Integration Discovery via Jentic

An AI agent uses Jentic to discover and call the Ecosystem API when a user asks 'what integrations does our product support?'. The agent searches Jentic for 'list integration marketplace listings', loads the Ecosystem operation schema, and executes against a specific ecosystem ID. Jentic stores the Apideck Authorization key separately so the raw secret never enters the agent's prompt context.

Example prompt: Through Jentic, search 'list integration marketplace listings', load the GET /ecosystems/{ecosystem_id}/listings operation, and execute it for ecosystem_id 'acme-marketplace'

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /ecosystems/{ecosystem_id} | Get ecosystem record |
| GET | /ecosystems/{ecosystem_id}/listings | List all listings in an ecosystem |
| GET | /ecosystems/{ecosystem_id}/listings/{id} | Get a single listing |
| GET | /ecosystems/{ecosystem_id}/categories | List categories |
| GET | /ecosystems/{ecosystem_id}/categories/{id}/listings | List listings within a category |
| GET | /ecosystems/{ecosystem_id}/collections | List curated collections |
| GET | /ecosystems/{ecosystem_id}/products | List products |

## Key resources

- **Ecosystem** — Top-level marketplace container - get a single ecosystem record with branding and configuration
- **Listing** — Individual integration entry with name, logo, description, and status; listable at the ecosystem, category, collection, or product level
- **Category** — Taxonomy node grouping listings by function (CRM, accounting, etc.) - list all or get one with its listings
- **Collection** — Curated themed group of listings (for example featured or onboarding bundles) - list all or get one with its listings
- **Product** — Apideck product grouping (Unified APIs, etc.) - list all or get one with its associated listings

## Why Jentic

- **Setup:** Wiring the Apideck Ecosystem API by hand means learning its marketplace ecosystem, listing, and category shapes and paging the catalogue yourself. Through Jentic you install once, import Apideck Ecosystem from the API Directory, and your agent calls it, no key to manage since this catalog surface is open.
- **Permission scoping:** The Apideck Ecosystem API puts the ecosystem id in the URL path (/ecosystems/{ecosystem_id}/...), so a rule can pin your agent to one ecosystem: it can read that ecosystem's listings and categories and nothing else. This surface is read-only marketplace data, so no listing metadata changes regardless of the operations you allow.
- **Credential handling:** Any header your Jentic One instance stores for this API is kept encrypted and injected at execution time. Nothing sensitive enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list marketplace listings' or 'browse ecosystem categories', and Jentic returns the matching Apideck Ecosystem operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Apideck Vault API** — Once a user picks a listing from the Ecosystem catalog, Vault handles the OAuth flow and stores the resulting connection.
- **Apideck Proxy API** — After Ecosystem surfaces a listing and Vault stores the connection, Proxy forwards arbitrary requests to that connector.
- **Pipedream API** — Pipedream offers a competing integrations directory with thousands of pre-built apps and workflow execution.

## FAQ

### What authentication does the Apideck Ecosystem API use?

The Ecosystem API spec does not declare a security scheme - listings, categories, and collections are read as marketplace metadata. When called through Jentic, any required Apideck Authorization header value is stored in your Jentic One instance and injected at execution time, so the agent never sees the raw key.

### Can I list all integrations in a specific category with the Ecosystem API?

Yes. Call GET /ecosystems/{ecosystem_id}/categories/{id}/listings to retrieve every listing tagged under a category. Use GET /ecosystems/{ecosystem_id}/categories first to discover available category IDs.

### What are the rate limits for the Apideck Ecosystem API?

The OpenAPI spec does not publish per-endpoint rate limits. Apideck applies platform-wide quotas - see https://developers.apideck.com for the current numbers tied to your plan. Cache responses where possible; ecosystem metadata changes infrequently.

### How do I fetch all listings for a marketplace through Jentic?

Install the SDK with `pip install jentic`, then run the search query 'list integration marketplace listings'. Jentic returns the GET /ecosystems/{ecosystem_id}/listings operation; load its schema and execute it with your ecosystem_id.

### Does the Ecosystem API let me trigger or call the underlying integrations?

No. The Ecosystem API is read-only and exposes marketplace metadata only. To actually call CRM, HRIS, or accounting integrations, use the corresponding Apideck Unified API (for example apideck.com/crm) or the Proxy API.

### What resources can I retrieve through the Ecosystem API?

Five top-level resources: ecosystems, listings, categories, collections, and products. All are accessed via GET - there are no create, update, or delete endpoints in this API.

### Can I limit what my agent is allowed to do with the Apideck Ecosystem API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The Ecosystem API carries the ecosystem ID in the URL path (/ecosystems/{ecosystem_id}/...), so you can pin the agent to a single ecosystem and let it read only that ecosystem's listings, categories, and collections. Every endpoint is a read-only GET, so no matter which operations you allow, the agent cannot create, update, or delete any listing metadata.