Apideck is a unified API gateway: one integration that normalizes records across 200+ services in categories like Accounting, CRM, HRIS, ATS, File Storage, E-commerce, and Issue Tracking. Connecting Apideck to clariBI gives the planner one consistent schema over whichever back-end systems a given consumer has connected through Apideck Vault.
Why connect Apideck
Each downstream tool has its own field names and quirks, so analyzing data across an accounting system, a CRM, and an HRIS usually means three separate integrations and three reconciliation steps.
With Apideck connected, you can ask "List open invoices across every accounting system we connect", "How many CRM opportunities are in each pipeline stage?", or "Show employee headcount by department from our HRIS" and the AI engine reads the normalized records live.
How the connection works
clariBI talks to Apideck through its hosted MCP server at https://mcp.apideck.dev/mcp. Authentication uses an API key you generate in your vendor account. Tokens stay encrypted server-side and never leave clariBI in clear form.
sequenceDiagram
actor U as You
participant C as clariBI
participant V as Apideck
U->>V: Generate an API key in Apideck dashboard
U->>C: Paste the key into the connect wizard
C->>V: list_tools (verify the key)
V-->>C: Tools available
C->>C: Encrypt and store credentials
C-->>U: Connection ready
Available tools
clariBI exposes the read-only Apideck tools that the vendor's MCP server publishes at connection time. Write operations (create, update, delete, send, refund) are filtered out by a name-pattern blocklist before any tool reaches the analysis engine, so connecting Apideck cannot modify data on the vendor side.
The exact tool inventory depends on the Apideck features your account has access to. After connecting, try a few natural-language questions to see what Apideck data clariBI can pull.
Data flow during analysis
When you ask a question that maps to Apideck, the AI engine routes to the right tool, reads the result, and pairs the answer with a chart you can pin to a dashboard.
sequenceDiagram
actor U as You
participant C as clariBI
participant AI as AI engine
participant V as Apideck
U->>C: Ask a question about normalized cross-category business records
C->>AI: Plan the analysis
AI->>V: Call the right tool
V-->>AI: Tool result
AI->>AI: Summarize and chart
C-->>U: Answer plus visual
Setting up the connection
- Open Data Sources in the clariBI sidebar.
- Click Add data source.
- Open the MCP Servers tab.
- Click the Apideck card.
- In the Apideck dashboard, open the API Keys page and copy your API key and your application id (App ID).
- Paste the API key and App ID 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).
- Click Connect, name your data source, and click Finish.
Permissions and data access
clariBI authenticates with the Apideck API key and App ID you paste and scopes every call to the consumer id you supply, so it only reads the integrations that consumer has connected through Apideck Vault. The catalog exposes read tools only (listing and reading records across the unified APIs); clariBI never creates, updates, or deletes a downstream record. Rotate the key from the Apideck dashboard, or disconnect from Settings → Integrations in clariBI.
Troubleshooting
| Error | Cause | Fix |
|---|---|---|
| "Invalid API key" | The pasted key is for a different Apideck application or environment. | Copy the key again from the API Keys page in the Apideck dashboard and confirm it matches the application that holds the consumer. |
| "No records for a connector" | The supplied consumer id has not connected that downstream service in Apideck Vault, or the connection is paused. | Check the consumer's connections in Apideck Vault and confirm the target service is connected and active. |