ISOERP developer documentation
ISOERP is accounting, ERP and CRM with one assistant, Star. Everything you can do on the screens is also available through one HTTP API, and through an MCP endpoint for AI assistants. This documentation describes only what exists today.
What you can connect
- REST API: every screen calls the same API, so your software can read and prepare the same records a person can. See the API reference.
- MCP connector: AI assistants that speak the Model Context Protocol can use the same tools Star uses. See the MCP guide.
- Imports and exports: guided import of old books, and report exports as PDF, Excel (XLSX), CSV, HTML or JSON. See Import and export.
- Document verification: printed invoices, receipts and other documents carry a QR code that anyone can check. See Document verification.
Rules that always hold
- You act as a person, in one company, with that person's role. A key or connector never has more rights than its owner.
- Money changes follow the maker-checker rule: a draft is made, someone else approves, and posting is a separate step. Approving, posting and reversing are done by a person in the app, never through an API key or the assistant.
- Every company's data is separate. Row-level security in the database keeps one company's rows away from another's.
- Your data is yours: you can export it at any time.
Start here
- Read Authentication and create an API key in Settings → API keys.
- Call
GET /api/accountswith the key to check it works. - Browse the API reference or connect an assistant with the MCP guide.
Also useful: Data model glossary, Security and data ownership, Changelog, FAQ.