The Glento API
Read, create, update, complete and delete tasks in your matrix from anywhere. Included with Pro, with no API keys to manage.
Three ways in
With code
Use the API directly
A small REST API at api.glento.ai, described by an OpenAPI document your tooling can read. Bearer token, JSON, six endpoints.
Jump to the referenceWith an assistant
Connect an AI assistant
The same API, exposed to assistants that speak the Model Context Protocol, so you can ask for what is urgent and have tasks created for you.
Tell us what you useNo code
Connect with Zapier
Wire Glento to thousands of apps without writing anything. Two triggers, four actions and a search, covering create, update, complete and delete.
Ask for early accessConnecting an account
There are no API keys to copy and no password to hand over. A tool sends you to Glento, you sign in, you see exactly what is being asked for, and you approve. The connection refreshes itself and stops the moment you remove it in the tool.
Pro is required for anything that touches tasks. The connection test itself works on any account, so a tool can tell you Pro is what is missing instead of failing with a shrug.
Endpoints
| Method | Path | What it does |
|---|---|---|
| GET | /tasks | List and filter by quadrant or status. Poll with updated_since to see everything that changed, deletions included. |
| GET | /tasks/{id} | One task. |
| POST | /tasks | Create. Send an Idempotency-Key and a retry will not double up. |
| PATCH | /tasks/{id} | Change fields, complete or uncomplete, move quadrant, reorder. Omit a field to leave it alone, send null to clear it. |
| DELETE | /tasks/{id} | Delete. A repeat call returns 204, so retries are safe. |
| GET | /me | Account and Pro status. Use it to test a connection. |
Base URL https://api.glento.ai/functions/v1. The full schema, including every task field, lives at /openapi and is the authority when it and this page disagree. glento.ai/llms.txt points AI tools at it.
Rate limit 60 requests per minute per account. Pages hold 50 tasks, 200 at most. Errors are always { error, code }.
Three rules worth knowing
1. Days carry a timezone
Due dates and start dates are days, not moments. Send an IANA timezone whenever you set one, or filter by status, and the day lands where you meant it. Leave it out and the request is refused rather than guessed at.
{ "title": "Renew the domain", "quadrant": "important_not_urgent",
"due_date": "2026-09-30", "timezone": "America/Chicago" }2. Deletes are visible, not silent
A deleted task turns up in an updated_since poll with deleted_at set, so your automation can react to it instead of drifting out of step. Nothing is hard deleted behind your back.
3. The repeat itself is read-only
A repeating task reads and edits like any other: change its title, notes, priority or quadrant and it behaves normally. What the API will not do yet is change the repeat, complete or uncomplete a task that belongs to a series, or set or clear a start date on one, so a series is never quietly broken.