Apideck APIs
16 APIs356 Endpoints9 Categories
Categories
API Catalog(5 of 16)
Connector API
The Apideck Connector API is the meta-API that describes the integrations Apideck Unify supports. It exposes the list of connectors (Salesforce, HubSpot, Xero, Greenhouse, Slack, etc.), the unified APIs each connector implements (CRM, ATS, Accounting, and so on), the documentation pages, and the schema and example payload for any resource. Builders use it to render in-app integration catalogues, check coverage before they prompt a customer to authorise, and inspect the schema for an operation at runtime.
10 endpointsEcosystem 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.
12 endpointsIssue Tracking API
The Apideck Issue Tracking API is a unified interface across Jira, Linear, GitHub Issues, GitLab Issues, Asana, and Trello. A single set of 15 endpoints covers tickets, comments, users, tags, and the project-like 'collections' that group them, eliminating the need to maintain a separate integration per tracker. All ticket and comment operations support full CRUD, while users and tags are read-only — they reflect data managed in the underlying tool. Tickets are addressed by both collection_id (the project) and ticket_id, mirroring how trackers scope issues to a project or repository.
Connect Your Agent
1
Step 1: 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 | sh2
Step 2: 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 instanceJentic 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.