When a page is not the whole job
Most of the time you will work Thogits from a page or from the assistant. That is the product: an AI-native workspace with a database and generated UIs.
Sometimes you need a custom setup. A script. A private admin tool. A warehouse job. A bridge to a system you will never click through. That is what the API is for.
The API is powerful. It covers records and the product. It is how you treat Thogits as infrastructure instead of only as a screen.
We will not paste an endpoint catalogue here. If you are the person who needs the API, you already know you want read/write on the system of record, not a marketing list of routes.
What you can do with it
Use the API to:
- Create, read, update, and query typed records
- Keep a custom setup in sync with the space
- Drive the same database the pages show
- Sit next to integrations you wired with credentials or OAuth
The records you touch are the same records everyone in the organisation sees. Same tickets, people, invoices, notes. No shadow database.
That matters for agencies with an existing stack, operations with a nightly job, and founders who already have a script they trust.
API vs MCP vs the assistant
Three ways in
Three ways in. Different jobs.
- Assistant — chat, email, phone calls. Can build pages. Can work records in language.
- MCP — your own agent can see and edit records. It cannot build pages, run automations, or the full agent loop.
- API — your code. Custom setups. Batch work. The product as a system you can call.
Pick the narrowest door that works. Do not stand up a service if you only needed to ask the assistant for a dashboard. Do not expect MCP to ship a UI. Do not expect the API to replace a conversation.
The API talks to a real data engine. The pages on top are screens the assistant built on those records. Your code can use the same source of truth.
Custom setups that still stay honest
A custom setup should not fork the facts. The API is there so your extra piece writes back.
Examples:
- A nightly script that loads jobs for tomorrow
- A small internal tool for a process that will never deserve its own page
- A bridge from a tool you connected, where the OAuth token is not enough on its own
- A report you generate outside Thogits, from live records
Automations can run a script on a schedule inside the product. The API is what that script, or yours, should call. Reminders stay for humans. The API stays for systems.
Start from a template if you want types and pages first. Add the API when the starting system is in place and you know the extra path you need.
Who this is for
You do not need the API to use Thogits. Small teams and small businesses can live in pages and chat.
You need the API when the workspace has to meet code you already run. Then it should be a powerful API, not a toy.
Try it
Stand up a space, create a few records in a page, then read them back from your own code. See all Features, check pricing, or sign up and treat the database as something you can call.