For Agents
Create and manage Microsoft To Do task lists, tasks, checklist items, and linked resources for the signed-in user via Microsoft Graph.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Microsoft To Do API (Graph), or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Microsoft To Do API (Graph) API.
Create and organise personal task lists for the signed-in user
Add tasks with due dates, reminders, and importance levels to a specific list
Break tasks down into checklist items for granular subtask tracking
Attach linked resources such as Outlook emails or external URLs to a task
GET STARTED
Use for: I need to create a new task list called Sprint Planning, Add a task to my Today list with a due date of tomorrow, List all tasks in the Groceries list, Mark the task about reviewing the report as completed
Not supported: Does not handle calendar events, email, or team/shared project tracking — use for managing the signed-in user's personal Microsoft To Do tasks only.
Jentic publishes the only available OpenAPI document for Microsoft To Do API (Graph), keeping it validated and agent-ready.
Jentic publishes the only available OpenAPI specification for Microsoft To Do API (Graph), keeping it validated and agent-ready. The Microsoft To Do API exposes task management capabilities via Microsoft Graph, letting applications create and organise task lists, add tasks with due dates and reminders, attach checklist items, and link external resources. It uses OAuth 2.0 bearer tokens scoped to the signed-in user's mailbox and supports the same task data that surfaces in Microsoft To Do, Outlook Tasks, and Planner integration scenarios. The 14 endpoints cover full lifecycle operations on lists, tasks, checklist items, and linked resources.
Update task status and completion state to keep workflow agents in sync
Retrieve all tasks across a list to feed daily-standup or planning agents
Delete obsolete tasks and lists to keep the user's To Do workspace tidy
Patterns agents use Microsoft To Do API (Graph) API for, with concrete tasks.
★ Personal Productivity Sync
Keep an agent's task backlog in lockstep with the user's Microsoft To Do account so reminders, due dates, and completion state stay consistent across devices. The API surfaces the same tasks shown in Outlook Tasks and the To Do mobile app, so changes made by an agent are reflected wherever the user already works.
Create a task titled 'Submit expense report' in the user's default To Do list with a due date of next Friday and importance set to high.
Meeting Follow-Up Capture
After a meeting, an agent extracts action items from notes or a transcript and writes them as tasks into a dedicated To Do list, optionally attaching the meeting recording or notes as linked resources. The user sees the action items appear in Microsoft To Do without copying anything by hand.
Create a task list called 'Q3 Planning Follow-ups' and add 5 tasks parsed from a meeting transcript, attaching the OneDrive transcript URL as a linked resource on each.
Checklist Decomposition
When a user asks an agent to break a complex task down into smaller steps, the agent posts a parent task and then creates checklist items beneath it. The user can tick items off in the To Do app and the agent can read remaining items back later.
Create a task 'Prepare onboarding pack' and add five checklist items: write welcome email, prepare laptop, schedule intro calls, share docs, send swag.
Agent-Driven Task Management via Jentic
Through Jentic, an AI agent discovers To Do operations by intent, loads the input schema for the chosen endpoint, and executes the call using a scoped Microsoft Graph token held in the Jentic vault. The agent never sees the raw token and can be wired into any framework that supports MCP or the Jentic SDK.
Use Jentic search for 'create a task in microsoft to do', load the schema for POST /me/todo/lists/{todoTaskListId}/tasks, and execute it with a generated task title and due date.
14 endpoints — jentic publishes the only available openapi specification for microsoft to do api (graph), keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/me/todo/lists
List all task lists
/me/todo/lists
Create a task list
/me/todo/lists/{todoTaskListId}/tasks
List tasks in a list
/me/todo/lists/{todoTaskListId}/tasks
Create a task
/me/todo/lists/{todoTaskListId}
Update a task list
/me/todo/lists/{todoTaskListId}
Delete a task list
/me/todo/lists
List all task lists
/me/todo/lists
Create a task list
/me/todo/lists/{todoTaskListId}/tasks
List tasks in a list
/me/todo/lists/{todoTaskListId}/tasks
Create a task
/me/todo/lists/{todoTaskListId}
Update a task list
Three things that make agents converge on Jentic-routed access.
Credential isolation
Microsoft Graph OAuth 2.0 bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped, time-bounded access — raw tokens and refresh tokens never enter the agent's context.
Intent-based discovery
Agents search by intent (e.g., 'create a task in microsoft to do') and Jentic returns matching Graph operations with their input schemas, so the agent can call the right endpoint without browsing Microsoft Graph documentation.
Time to first call
Direct Microsoft Graph integration: 1-3 days for app registration, OAuth consent flow, token refresh, and Tasks scope handling. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Google Tasks API
Google's equivalent personal task list API across the Google Workspace user base.
Choose Google Tasks when the user signs in with a Google account; choose Microsoft To Do when the user is in the Microsoft 365 ecosystem.
Asana API
Team and project task management for handing off personal action items into shared projects.
Use alongside Microsoft To Do when an agent needs to escalate a personal task into a tracked project task with assignees and due dates.
ClickUp API
Cross-functional task and project platform with richer hierarchy than personal task lists.
Pick ClickUp when the user needs project-level structure (spaces, lists, sprints); pick Microsoft To Do for individual day-to-day tasks.
Specific to using Microsoft To Do API (Graph) API through Jentic.
Why is there no official OpenAPI spec for Microsoft To Do API (Graph)?
Microsoft Azure does not publish a dedicated OpenAPI specification for the To Do surface of Microsoft Graph. Jentic generates and maintains this spec so that AI agents and developers can call Microsoft To Do API (Graph) via structured tooling. It is validated against the live Microsoft Graph API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Microsoft To Do API use?
The API uses OAuth 2.0 bearer tokens issued by Microsoft identity platform, sent in the standard Authorization header as configured by the bearerAuth scheme. The token must be granted Tasks.ReadWrite delegated permission for the signed-in user. Through Jentic, the bearer token is held in the encrypted vault and never exposed to the agent's context.
Can I create checklist items under a task with this API?
Yes. After creating a task with POST /me/todo/lists/{todoTaskListId}/tasks, you can add granular subtasks using the checklist items endpoints under that task. The same data appears as the in-app checklist beneath the task in Microsoft To Do.
What are the rate limits for the Microsoft To Do API?
Microsoft Graph applies per-app and per-user throttling limits documented under the Graph throttling guidance. To Do operations fall under the Outlook service limits, typically 10,000 requests per 10 minutes per app per mailbox. Expect a 429 response with a Retry-After header when limits are hit.
How do I create a task in Microsoft To Do through Jentic?
Run pip install jentic, then use the Python SDK to search for 'create a task in microsoft to do', load the schema for POST /me/todo/lists/{todoTaskListId}/tasks, and execute with the list id and task body. Jentic injects the scoped Graph token automatically.
Does this API cover team or shared task lists?
No. The endpoints in this spec target /me/todo, which is the signed-in user's personal To Do data. For team task management on the same Graph, use Microsoft Planner or Microsoft Teams APIs instead.
/me/todo/lists/{todoTaskListId}
Delete a task list