Apideck APIs

16 APIs356 Endpoints9 Categories

API Catalog

Accounting API

Apideck Accounting is a unified API that maps a single schema for invoices, bills, payments, ledger accounts, customers, suppliers, and tax rates onto many downstream accounting platforms such as Xero, QuickBooks, Sage, NetSuite, and FreshBooks. The 95 operations cover the day-to-day finance objects most apps need plus reports like Balance Sheet, Profit and Loss, and Aged Debtors. Apideck routes each call through Apideck Vault, so customer credentials for the underlying platform stay in Apideck's vault instead of being passed in by the calling app.

95 endpoints

ATS API

Apideck ATS is a unified API that maps a single schema for jobs, applicants, applications, offers, and activities onto downstream applicant tracking systems such as Greenhouse, Lever, Workable, SmartRecruiters, and BambooHR. The 12 operations cover the recruiting hand-off most apps need: read open roles, read candidate records, post applications, and write offers. Apideck routes each call through Apideck Vault, so per-customer ATS credentials stay in Apideck's vault rather than being passed to the calling app.

12 endpoints

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 endpoints

CRM API

Apideck CRM is a unified API that maps a single schema for companies, contacts, leads, opportunities, pipelines, activities, notes, and users onto downstream CRMs such as Salesforce, HubSpot, Pipedrive, Zoho, and Microsoft Dynamics. The 40 operations cover the day-to-day CRM objects most apps need, and Apideck routes each call through Apideck Vault so per-customer CRM credentials never reach the calling app. Builders typically replace 5+ direct CRM integrations with a single Apideck contract.

40 endpoints

Customer Support

Apideck Customer Support is a unified API that maps a single customer schema onto downstream support platforms such as Zendesk, Freshdesk, Intercom, and HubSpot Service Hub. The 9.5.0 spec is intentionally narrow: 5 operations focused on the customer object, so a SaaS app can pull or push customer records through one integration regardless of which help desk the end user runs. Apideck routes each call through Apideck Vault so per-customer help-desk credentials never reach the calling app.

5 endpoints

Ecommerce API

Apideck Ecommerce is a unified API that maps a single schema for orders, products, customers, and stores onto downstream e-commerce platforms such as Shopify, WooCommerce, BigCommerce, and Squarespace Commerce. The 10.14.0 spec is intentionally narrow with 7 operations focused on the highest-leverage objects, so a SaaS app can read orders, look up products, and pull customer records through one integration regardless of which storefront the merchant runs.

7 endpoints

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.

12 endpoints

File Storage API

The Apideck File Storage API is a unified interface for working with files, folders, shared links, and resumable upload sessions across multiple cloud storage providers including Google Drive, Dropbox, Box, OneDrive, and SharePoint. A single set of 33 endpoints covers listing, uploading, downloading, copying, and renaming files plus drive and drive-group management, eliminating per-vendor SDKs. It supports multipart upload sessions for large files and a search endpoint for full-text and metadata queries. Authentication is a single bearer-style Authorization header on the unify.apideck.com base URL paired with consumer and application headers identifying the end user's connected drive.

33 endpoints

HRIS API

The Apideck HRIS API is a unified interface across HR information systems including BambooHR, Gusto, Workday, ADP, and Rippling. A single set of 25 endpoints covers employees, companies, departments, payrolls, employee schedules, and time-off requests, eliminating the need to maintain a separate integration per HRIS vendor. Employee records support the standard CRUD lifecycle, while payroll endpoints are read-only — payroll runs are surfaced as data, not triggered through this API. Time-off requests can be created and updated, making it usable for self-service leave workflows.

25 endpoints

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

15 endpoints

Lead API

The Apideck Lead API is a focused unified interface for working with sales leads across CRMs and lead-capture tools including Salesforce, HubSpot, Pipedrive, and Zoho. Five endpoints cover the full CRUD lifecycle on a single normalised lead resource — list, create, get, update, and delete — so a marketing form, chat widget, or AI agent can push qualified leads into whichever CRM the customer uses without per-vendor code. Authentication uses the standard Apideck Authorization header alongside x-apideck-app-id and x-apideck-consumer-id.

5 endpoints

POS API

The Apideck POS API is a unified interface across point-of-sale platforms including Square, Clover, Lightspeed, Toast, and Shopify POS. A single set of 46 endpoints covers orders, payments, merchants, locations, items, modifiers, modifier groups, order types, and tenders, eliminating the need to maintain a separate integration per POS vendor. Orders, payments, and the surrounding catalog resources support full CRUD plus a dedicated POST /pos/orders/{id}/pay endpoint that closes out an order. Designed for marketplaces, loyalty programs, and back-office tools that need to read or write to whichever POS the merchant runs.

46 endpoints

Proxy API

The Apideck Proxy API forwards arbitrary HTTP requests to a connector's underlying API while reusing the OAuth token and configuration that Apideck has already negotiated with the end user. Five endpoints — GET, POST, PUT, PATCH, DELETE — all on the single /proxy path expose the full HTTP surface, with the target service identified by Apideck headers and the path passed through to the upstream provider. It exists as an escape hatch when a Unified API does not cover a feature the agent or product needs to call directly. Authentication uses the Apideck Authorization header plus x-apideck-app-id; the consumer ID identifies which connection the request is forwarded over.

5 endpoints

SMS API

The Apideck SMS API is a focused unified interface for sending and managing SMS messages across providers including Twilio, MessageBird, Vonage, and Plivo. Five endpoints cover the full message lifecycle — list, create, get, update, and delete — so a SaaS product can hand SMS sending to whichever provider the customer has connected without writing per-vendor code. Authentication uses the standard Apideck Authorization header alongside x-apideck-app-id and x-apideck-consumer-id. Designed for transactional messaging, OTPs, and notifications rather than for bulk marketing campaigns.

5 endpoints

Vault API

The Apideck Vault API manages connections, OAuth flows, consumer records, and custom field mappings that power every Apideck Unified API call. Thirty-one endpoints cover creating Vault sessions for end-user authorisation UIs, listing and configuring connections per consumer, importing pre-existing tokens, validating and refreshing connection state, and exposing logs for debugging. Custom-mappings endpoints let teams map their internal field IDs to each connector's native fields so Unified API payloads pass through correctly. Authentication uses the Apideck Authorization header alongside x-apideck-app-id; consumer IDs identify which end user a connection belongs to.

31 endpoints

Webhook API

The Apideck Webhook API manages webhook subscriptions and delivery for events emitted by Apideck Unified APIs. Ten endpoints cover subscription CRUD, manual webhook execution against a specific service, callback resolution paths used by connectors that push events back, and event log retrieval for debugging. A subscription is identified by ID and scoped to a service, with execute and resolve endpoints allowing replay or on-demand delivery. Authentication uses the Apideck Authorization header alongside x-apideck-app-id and x-apideck-consumer-id.

10 endpoints

Connect Your Agent

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 | sh

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