Introducing the Glento API: Your Matrix, Open to Your Other Tools
Every task app eventually hits the same wall. The work does not start in the app. It starts in an email, a form response, a calendar invite, a message from a client. Someone has to carry it across by hand, and that someone is you, several times a day.
Today we are opening the other end of that. Glento now has an API.
It is a Pro feature, and for a specific reason rather than an arbitrary one: the API reads the synced copy of your tasks, and syncing is what Pro pays for. Without sync your tasks only ever exist on your device, which is the default and the point. What you get on each plan lays out the whole picture, including what happens if you have Pro but are signed out.
What it is
A small REST API over your matrix. Six endpoints, JSON in and JSON out, and an OpenAPI document your tooling can import instead of you writing a client by hand.
- List and filter tasks, by quadrant or by status, or poll for everything that changed since a moment you name.
- Read a single task.
- Create a task, with a title, quadrant, priority, tags, notes, a due date and a start date.
- Update one: change fields, move it between quadrants, reorder it, complete it or reopen it.
- Delete one.
- Check a connection, which tells a tool whose account it is talking to.
The full reference is at glento.ai/developers, in English, Spanish, German and French. It is included with Pro at no extra cost: no separate plan, no per-call pricing, and nothing else changes about what you already pay.
Three things worth knowing before you build
These are the parts that surprise people, so they are worth saying plainly rather than burying in a schema.
Days carry a timezone. A due date is a day in your life, not a moment on a clock. Any request that sets a due date or a start date has to say which timezone that day belongs to. Leave it out and Glento refuses the request rather than guessing and quietly filing your task on the wrong day. It is a small amount of extra work at the call site that removes an entire category of off-by-one-day bugs.
Deletions are visible. When you poll for what changed, deleted tasks come back marked as deleted rather than silently vanishing from the results. An integration can react to a deletion instead of drifting out of sync with your matrix and never knowing why.
Repeating tasks are handled carefully. You can read and edit a repeating task like any other, changing its title, notes, priority or quadrant. What the API will not do yet is change the repeat itself, or complete a task that belongs to a series. That is deliberate. A half-applied change to a recurring series is worse than a change you have to make in the app.
How connecting works
There are no API keys to copy and no password to hand to anyone.
A tool sends you to Glento, you sign in, you see exactly what is being asked for, and you approve. The connection keeps itself alive from there, and it stops the moment you remove it in the tool. That is the same flow you have seen when connecting any modern app to another, and it is deliberately the only way in: there is no long-lived secret sitting in someone else's config file with the keys to your account.
Getting access today
The API is live in production now. Access is by request while the connectors that sit on top of it finish their reviews, so if you want to build against it, get in touch and tell us what you are building. We will set you up.
That is not a stalling tactic. It is a small product and we would rather talk to the first people using it than discover afterwards what we got wrong.
What comes next
A no-code connector is in review, so you will be able to wire Glento to thousands of other apps without writing anything at all. We will post again the day it goes live.
An AI assistant connection is coming after that, so you can ask an assistant what is urgent, or have it file tasks for you, without leaving the conversation you are already in.
What has not changed
Glento still works offline, still stores your tasks on your device first, and still does not require an account to use the core app. The API is an addition for the people who want it, not a new dependency for the people who do not.
Open the app and nothing looks different. That is on purpose. The matrix is still four quadrants and one question: what should I do right now? This just means fewer things have to arrive there by hand.
