This guide shows how to integrate Eagle Doc as a business and process documents on behalf of your clients. You keep calling the same receipt, invoice, any-document, split and RAG endpoints — you simply authenticate with a business API key and, optionally, tag each request with the client it belongs to.
Nothing about personal API-… keys changes. The business features below are purely additive — existing integrations keep working untouched.
Two additive mechanics turn any Eagle Doc integration into a multi-client one:
APIB-… and sent in the same api-key header. Usage is billed to the business subscription, not to any individual person.Your organization on Eagle Doc: it owns the subscription, the API keys and the clients. All usage rolls up to it.
A customer you serve. A pure attribution label — no login, no key, no separate bill. Usage and RAG examples can be split per client.
An APIB-… key that authenticates machine calls as the business. Create as many as you need; revoke any individually.
Every client’s pages count against the one business subscription. You still see a per-client breakdown for your own reporting.
Go from zero to a client-attributed extraction in five steps.
In the dashboard, create a business, then open Settings → API keys and copy a new APIB-… key. You can also automate this — see Authentication.
Send it in the same api-key header you already use — the APIB- prefix is what makes the call business-scoped.
Add x-sub-business-ref with your own client number. On first use Eagle Doc creates the client automatically — you never pre-register anything.
Everything else is identical to a personal-key integration. Here is a receipt extraction attributed to client A-1023:
curl --location 'https://de.eagle-doc.com/api/receipt/v3/processing' \
--header 'api-key: APIB-your-business-key' \
--header 'x-sub-business-ref: A-1023' \
--form 'file=@"receipt.jpeg"'
import requests
resp = requests.post(
"https://de.eagle-doc.com/api/receipt/v3/processing",
headers={
"api-key": "APIB-your-business-key",
"x-sub-business-ref": "A-1023", # your own client number
},
files={"file": open("receipt.jpeg", "rb")},
)
print(resp.json())
import fs from "node:fs";
const form = new FormData();
form.append("file", new Blob([fs.readFileSync("receipt.jpeg")]), "receipt.jpeg");
const resp = await fetch("https://de.eagle-doc.com/api/receipt/v3/processing", {
method: "POST",
headers: {
"api-key": "APIB-your-business-key",
"x-sub-business-ref": "A-1023", // your own client number
},
body: form,
});
console.log(await resp.json());
Call GET /api/usage/v1/current with the business key for the rolled-up quota, or view the per-client breakdown in the dashboard. See Usage & quota.
Create and manage business API keys, and how to send them.
Zero-touch vs. strict client tagging, and the client management API.
Any-document, invoice, receipt, split and finance with a business key.
Teach the model per client so accuracy improves independently.
Rolled-up quota and the per-client usage breakdown.
Building your multi-client integration and something is unclear? We are glad to help so your project succeeds.
Reach us at support@eagle-doc.com
Copyright © S2Tec GmbH