Apideck APIs
16 APIs356 Endpoints9 Categories
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 endpointsATS 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 endpointsConnector 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.
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.