API introduction
In Aikount, the API is the product; the web UI is the fallback for humans. Everything you can do from the web —issue invoices, capture expenses, reconcile the bank, prepare the AEAT tax models— can be done with an HTTP call. Any agent or script can run the books with a token.
This is not an add-on: it is the design. Aikount is built so an AI agent can operate the accounting end to end, and so you or your accountant supervise the result. The web exists for the people who prefer to click buttons.
The core idea
- Accounting is a set of repetitive, verifiable operations: create an invoice, book an expense, link a payment to its invoice, list a quarter's VAT.
- Each of those operations is an endpoint. An agent chains endpoints the same way a person chains clicks.
- With a valid token the agent acts inside your company (tenant) and obeys the same rules the web does: multi-tenant isolation, purchase deduplication, posting to the Spanish chart of accounts.
Base URL and public surfaces
The API base is:
https://api.aikount.com
Business endpoints live under /api/v1 (for example /api/v1/invoices). You have three ways to explore the API in detail:
| Surface | URL | What for |
|---|---|---|
| Swagger UI | https://api.aikount.com/docs | Explore and try endpoints from the browser |
| OpenAPI JSON | https://api.aikount.com/openapi.json | Machine-readable spec (source of truth) |
| Redoc | https://api.aikount.com/redoc | Browsable, read-oriented reference |
The OpenAPI spec is the source of truth for parameters, types and responses. If this documentation and
openapi.jsondisagree,openapi.jsonwins.
What to read next
- To get a token and start calling: Authentication and API keys.
- To connect an agent over MCP (Claude Code, Cursor, Gemini CLI, Codex): MCP and Connect an agent.
- For the map of the business endpoints: Core endpoints.
- For the cross-cutting rules (money, dates, IDs, errors, pagination): API conventions.