Ecosystem API

Name: Ecosystem API API
Brand: Ecosystem API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsProject Managementnone12 EndpointsREST

For Agents

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

Connect the Ecosystem API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ecosystem API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Ecosystem API API.

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

GET STARTED

Start building with Ecosystem API API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Ecosystem API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

12 endpoints — the apideck ecosystem api exposes a read-only catalog of integration listings, categories, collections, and products that power apideck-hosted integration marketplaces.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Any Apideck Authorization or x-apideck-app-id header values are stored encrypted in the Jentic vault. Agents receive scoped execution tokens and never see the raw keys, even though most Ecosystem endpoints are read-only.

Intent-based discovery

Agents search by intent (for example 'list integration marketplace listings') and Jentic returns the matching Ecosystem GET operations along with their input schemas, so the agent can request listings by ecosystem_id without browsing Apideck docs.

Time to first call

Direct Apideck Ecosystem integration: half a day to a day to wire HTTP calls and pagination. Through Jentic: under 30 minutes — search, load the schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Apideck Vault API

Once a user picks a listing from the Ecosystem catalog, Vault handles the OAuth flow and stores the resulting connection.

Choose Vault when the agent needs to actually connect a user to an integration after they've browsed the Ecosystem catalog.

Complementary

Apideck Proxy API

After Ecosystem surfaces a listing and Vault stores the connection, Proxy forwards arbitrary requests to that connector.

Use Proxy when an agent needs to call an endpoint on a connected integration that isn't covered by an Apideck Unified API.

Alternative

Pipedream API

Pipedream offers a competing integrations directory with thousands of pre-built apps and workflow execution.

Choose Pipedream when the agent needs both a marketplace and runtime workflow execution; choose Apideck Ecosystem when only directory metadata is needed.

FAQs

Specific to using Ecosystem API API through Jentic.

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 the Jentic vault 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.