AI & Models · Integration
Klippa DocHorizon
Add Klippa DocHorizon to your product for your customers, and give your AI agents governed access to it.
Embed a Klippa DocHorizon integration so your customers can turn the invoices, receipts and forms they hold in your product into structured data using their own DocHorizon credentials, with usage and cost on their account rather than a shared key you have to police. fastn handles per-customer credentials, retries and API upkeep, so document types and field mapping are configuration per tenant instead of code.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers submit documents from your product for data extraction using their own DocHorizon credentials.
Read the extracted fields back as structured data so your product never asks a user to retype them.
Classify or convert an uploaded file before your product decides what to do with it.
Keep extraction usage per tenant so one customer's volume never affects another's.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent extracts the fields it needs from a document before filing the result.
An agent classifies an inbound file to choose the right workflow, within governed permissions.
Every extraction call runs under the customer's own credentials and is logged per tenant.
Example prompt
Extract the supplier, invoice number, date and total from this PDF and return them as structured fields.
Set up Klippa DocHorizon in 4 steps
- 01Open the Klippa DocHorizon connector from your fastn dashboard.
- 02Have each customer authenticate their own Klippa DocHorizon account.
- 03Map the document types and output fields your product uses, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Klippa DocHorizon integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Klippa DocHorizon integration without building it. Your customers connect their own Klippa DocHorizon account inside your product and work their models, requests and outputs there, with no per-customer code on your side.
- Handle the part that actually costs time: per-customer keys, quotas and cost attribution matter more than schema here, because every call is billed. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Klippa DocHorizon update is not your on-call problem.
- One integration serves your product and your agents. The same governed Klippa DocHorizon connection powers in-product features and gives AI agents scoped, audited access, so you give your product and your agents a model call each customer pays for themselves without wiring it twice.
Used by these teams
Works well with
Docusign
Box
AWS Simple Storage ServiceOften used alongside
Tools the same teams tend to run next to Klippa DocHorizon, across other categories.
Snowflake
Airtable
PostgreSQL
AmplitudeKlippa DocHorizon integration FAQ
How do I add a Klippa DocHorizon integration to my product?
Enable the Klippa DocHorizon connector in your fastn dashboard, then let each customer authenticate their own Klippa DocHorizon account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Klippa DocHorizon client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Klippa DocHorizon account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Klippa DocHorizon account and only ever sees their own models, requests and outputs. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Klippa DocHorizon integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent extracts the fields it needs from a document before filing the result.
Who maintains the Klippa DocHorizon integration?
fastn does. When Klippa DocHorizon changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose Klippa DocHorizon API key and quota does each call use?
Each customer authorises their own Klippa DocHorizon account, so usage, rate limits and cost land on the customer that caused them. You are not metering a shared key and re-billing it, and one heavy customer cannot exhaust another's quota.
Are inputs and outputs auditable?
Yes. Every call is logged per tenant with the call, the input and the result, so an output can be traced back to what produced it. That matters more here than in most integrations, because a generated answer or an extracted field cannot be reconstructed from the request alone.
What can I build with the Klippa DocHorizon integration?
A common starting point: submit documents from your product for data extraction using their own DocHorizon credentials. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Klippa DocHorizon integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Klippa DocHorizon does not change your per-connector cost. You can start free with 3 connected accounts.
Add Klippa DocHorizon to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.