Documentation
Find the guide you need to integrate Factuarea.
Choose what you want to build. We take you to the right guide; the live reference is at docs.factuarea.com.
- In Spanish, English and Catalan
- Sandbox with a fact_test_ key
- Included with paid plans and the trial
Compatible integrations and formats
WhatsApp
Factuarea Docsdocs.factuarea.com- Quickstart/guides/quickstart
- Invoice reference/api-reference/invoices
- Official SDKs/sdks
The route
Start with what you want to build
You do not need to read hundreds of pages. Pick the outcome and open the first guide in that route.
The size of it
797 pages. None of them is meant to be read whole.
The documentation is not a manual, it is a warehouse. More than half of its surface is endpoint pages and error pages you look up once, when you need them. What is actually read end to end is forty-eight guides.
413reference pages
One per operation, generated from the OpenAPI spec: 413 operations across 37 resources. You look them up, you do not read them.
See one: list invoicesopens docs.factuarea.com in a new tab311error codes
One code, one page. You arrive from the failing response, not from the index.
The codes by categoryopens docs.factuarea.com in a new tab48guides
The only part read straight through: authentication, idempotency, webhooks, time tracking, managed companies.
The home page, with the indexopens docs.factuarea.com in a new tab25SDKs, MCP, CLI and help
The TypeScript and PHP SDKs, the MCP server, the CLI, pricing and limits, FAQ, support and changelog.
The official SDKsopens docs.factuarea.com in a new tab
And the same 797, in full, in Spanish, English and Catalan.
Machine-readable
Web, llms.txt and llms-full.txt for people and agents
API documentation is no longer read by a person alone: it is read by the agent that person asked to do the integration. And an agent does not browse, it downloads. The two addresses below exist for that, served from the same domain.
docs.factuarea.com
To read it
The site, with search, and a button on every page that copies it as Markdown.
- Languages
- 3
- Pages
- 797
/llms.txt
To find things
The curated index of the llms.txt convention: every link with one line of what is inside.
- Size
- 750 KB
- Links
- 2,391
/llms-full.txt
All documentation in one file
Every page concatenated as clean Markdown, no components and no layout, each one carrying its canonical URL so it can be cited.
- Size
- 5.9 MB
- Pages
- 1,565
It is 1,565 and not 2,391 because the endpoint reference is identical in all three languages and appears once: 413 shared pages plus 384 per language. The dump tells the truth, and you can check it with a subtraction.
Published surface
An integration that fits your stack
The OpenAPI contract, SDKs and MCP server share the same API. These figures are checked against the published surface so you can assess scope and maintenance before integrating.
- API operations
- 413
- resources
- 37
- MCP tools
- 391
- documentation pages
- 797
Compatible technologies and clients
OpenAPI
TypeScript
PHP
Claude
Logos identify compatible technologies or clients; they do not imply a commercial relationship or endorsement.
Doubts
Before you open the documentation
In full in Spanish, English and Catalan: not a translated index, all 797 pages. Same address with the prefix in front, /es/guides/quickstart or /ca/guides/quickstart. The only thing that does not change language is the code of an error.
Now you know where to start.
The first guide on the route ends with an invoice issued and sent. Against the sandbox, without spending a single number of your real numbering.