Apideck + clariBI
Connect Apideck through clariBI's MCP catalog. One read-only API key, and normalized records across Accounting, CRM, HRIS, and more sitting next to the rest of your data.
Native Apideck connector via the MCP catalog.
Connect with an Apideck API key, App ID, and consumer id, keep the access read-only, and ask questions across every connected back-end system in plain English. The setup is the same MCP flow as PostHog, Stripe, or Jira.
What is Apideck?
Apideck is a unified API platform. Instead of integrating each SaaS tool separately, you integrate Apideck once and read normalized records across 200+ connectors spanning Accounting, CRM, HRIS, ATS, File Storage, E-commerce, and Issue Tracking. Each customer's connections live behind a consumer id in Apideck Vault.
clariBI reaches Apideck through its hosted MCP server using your API key, App ID, and a consumer id. Reads are scoped to that consumer's connected services, returned in Apideck's consistent schema, and clariBI never writes back to any downstream system.
Learn more at apideck.com
Connect Apideck in three steps
Open Data Sources in clariBI
In clariBI, go to Data Sources → Add Data Source → MCP Servers tab. Find Apideck in the catalog and click Connect.
Paste your API key, App ID, and consumer id
Copy your API key and application id (App ID) from the API Keys page in the Apideck dashboard and paste them into clariBI. Then enter the consumer id for the customer whose connected accounts you want to read, the same id you use in Apideck Vault. Credentials are Fernet-encrypted at rest.
Ask questions, get dashboards
clariBI reads normalized records across that consumer's connected services. Ask "How many CRM opportunities are in each pipeline stage?" and the AI engine queries Apideck alongside your other tools.
What you can analyze
Out of the box with the Apideck MCP connector:
- Open invoices and bills across every connected accounting system
- CRM opportunities by pipeline stage and owner
- Employee headcount by department from the connected HRIS
- Candidates and applications by stage from the connected ATS
- Orders and products from connected e-commerce platforms
- Cross-source: CRM opportunities → accounting invoices → paid versus outstanding
Apideck is one of 90+ vendors in the clariBI MCP catalog. See the full list →
What the AI engine can call
clariBI discovers Apideck's tool surface at connection time and exposes the read-only tools to the planner. Write or configuration tools are filtered out by the catalog's read-only heuristic, so the connector stays analytical.
When you connect, clariBI lists the tools your Apideck MCP server advertises and keeps the read-only ones: listing and reading records across the Accounting, CRM, HRIS, ATS, File Storage, E-commerce, and Issue Tracking unified APIs.
Anything that would change Apideck is excluded at the catalog layer and never reachable through clariBI.
See the live tool list once connected, or read the setup guide →
Cross-source questions Apideck makes possible
Apideck data is most useful next to your other tools. clariBI's planner composes it with your CRM, billing, and product data through the same entity-join primitives that back every cross-source analysis.
Apideck × Stripe
"Which CRM opportunities have an outstanding invoice in our accounting system?"
Planner: read won opportunities from the Apideck CRM API, match them to invoices from the Apideck Accounting API, and flag any still marked unpaid.
Apideck × Product analytics
"Does headcount growth in a department track with its product usage?"
Planner: read department headcount from the Apideck HRIS API and join it to product usage over the same months.
Apideck connector FAQ
What do I need to connect Apideck?
An Apideck API key and application id (App ID) from the API Keys page in your dashboard, plus the consumer id whose connected accounts you want clariBI to read. You paste all three into clariBI; there is no OAuth popup for this connector.
What is a consumer id and why does clariBI need one?
In Apideck Vault, each of your customers (or internal accounts) is a consumer that owns its own set of connected services. The consumer id scopes every read to one consumer's connections, so clariBI only sees the integrations that consumer has authorized.
Can clariBI change records in the downstream systems?
No. The catalog exposes read tools only, and the read-only heuristic filters out anything that writes. clariBI lists and reads normalized records; it never creates, updates, or deletes data in any connected service.
Which clariBI plan includes the Apideck connector?
MCP integrations are available on the Trial, Starter, Professional, and Enterprise plans. You can connect Apideck during the free 14-day trial.
Start your free trial and connect Apideck in a minute
API key in, read-only, dashboards in seconds.
Start free trial