Reassign App Reassign REST API
60
AI ReadinessAI-Aware (B-)60/100
Official vendor OpenAPI document · agent-readyProductivityCalendar Schedulingbearer89 EndpointsREST
For Agents
Read a Reassign day, create and move events, book tasks into free time, capture Inbox items, log tracker moments, and turn a free-form command into a planned day.
Use for: Find a 90-minute slot for deep work tomorrow afternoon, Move my gym session to 7am on Thursday, Get my schedule for this week, I need to add three tasks to my Inbox
Not supported: Does not send meeting invites, host booking pages for other people, or manage team project boards. Use for planning one person's day in Reassign only.
The Reassign REST API drives Reassign, a 24-hour circular day planner: it reads a day or a range of days, creates, moves, and deletes events, and books work into free time without the caller computing slots. Around the schedule it manages the Inbox of unplaced tasks, areas and activity types, moment trackers and the values logged against them, connected calendar sources, and a daily reflection that can be confirmed or discarded. A command operation turns a free-form line or a braindump into events, Inbox items, and moments, with a dry-run mode that returns the plan without writing.
Install Jentic One Beta
Connect the Reassign REST API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Reassign REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freassign.app%2Freassign" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Freassign.app%2Freassign" | 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.
Capabilities
What an agent can do with Reassign REST API.
Book 1 to 20 tasks into free time with POST /api/v1/schedule/plan, each with a name, durationMinutes, and an exact start or an earliest and latest window
Create, update, shift, reflect on, or delete up to 50 events in one atomic call, or allow partial success with partial true
Address one occurrence of a recurring event with seriesId@YYYY-MM-DD, or that occurrence and every later one with scope future
Capture, schedule, park, or remove Inbox items, sized in whole minutes from 5 to 1440
Log a moment against a tracker, from a quick tap with only trackerId to an exact time, value, and note
Turn a free-form line or braindump into events and Inbox items with POST /api/v1/command, previewing first with apply false
Reverse up to 20 recent writes with the undoToken values they returned, before the tokens expire
Use Cases
Patterns agents use Reassign REST API for, with concrete tasks.
★ Day planning from an AI agent through Jentic
A planning agent can take 'fit in two hours of writing and a gym session tomorrow' and do it: read the day, book the work into free time, and report what moved. Through Jentic it searches for 'book work into free time', receives the schedule plan operation with its requests input, and calls it with a Personal Access Token injected by your self-hosted Jentic One instance. Writes return an undoToken, so a wrong placement can be reversed within 30 minutes.
Call GET /api/v1/schedule with from and to set to tomorrow, then POST /api/v1/schedule/plan with requests for 'Writing' with durationMinutes 120 and 'Gym' with durationMinutes 60, each with an earliest and latest window
Batch event edits
Rescheduling usually means touching several events at once. POST /api/v1/events takes 1 to 50 ops, each naming its verb such as create, update, shift, or delete, and runs them atomically unless partial is true. A span is a start and end as local datetimes in the account's time zone, and recurring events are edited per occurrence or for the rest of the series.
POST /api/v1/events with an update op that sets start '2026-11-19T07:00' and end '2026-11-19T08:00' on the gym event's occurrence id
Inbox capture and triage
Not every task has a time yet. The Inbox holds unplaced items: POST /api/v1/backlog captures items with a name, notes, and an estimated durationMinutes, and later schedules them at a local start or parks a placed event back into the Inbox. Each item takes a kind of blocking, non_blocking, or reference.
POST /api/v1/backlog with three capture ops named 'Reply to Sam', 'Draft Q1 plan', and 'Book dentist', each with durationMinutes 30
Habit and mood tracking
Moment trackers record things like mood, water, or focus over the day. POST /api/v1/trackers creates a tracker with a name and scale, POST /api/v1/moments logs an entry with only a trackerId for a quick tap or with a time, value, and note, and GET /api/v1/moments reads a day range back for review.
Call GET /api/v1/trackers to find the mood tracker's id, then POST /api/v1/moments with that trackerId, value 7, and note 'after lunch walk'
Key Endpoints
89 endpoints — the reassign rest api drives reassign, a 24-hour circular day planner: it reads a day or a range of days, creates, moves, and deletes events, and books work into free time without the caller computing slots.
METHOD
PATH
DESCRIPTION
GET
/api/v1/schedule
Read a day or a range of days
POST
/api/v1/schedule/plan
Book work into free time
POST
/api/v1/events
Create, change, or delete events
GET
/api/v1/events/search
Find events by text
POST
/api/v1/backlog
Capture and schedule Inbox items
POST
/api/v1/moments
Log a moment
POST
/api/v1/command
Run an AI quick command
POST
/api/v1/actions/undo
Reverse a recent write
GET
/api/v1/schedule
Read a day or a range of days
POST
/api/v1/schedule/plan
Book work into free time
POST
/api/v1/events
Create, change, or delete events
GET
/api/v1/events/search
Find events by text
POST
/api/v1/backlog
Capture and schedule Inbox items
POST
/api/v1/moments
Log a moment
POST
/api/v1/command
Run an AI quick command
POST
/api/v1/actions/undo
Reverse a recent write
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
R
Reassign REST API
- AI-Aware (B-)60/100
73
Foundational Compliance70
Developer Experience & Jentic Compatibility41
AI-Readiness & Agent Experience87
Agent Usability55
Security66
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
92%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
70
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B+Signals: 4
4%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
41
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
9%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
98%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
56%
Summary Coverage
Coverage of summaries across operations/tags/info.
87
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
87%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
55
Security
Trust, risk posture, and security compliance.
Grade: CSignals: 1
55%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
66
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
66%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Reassign by hand means minting a Personal Access Token with the right events scope, formatting local datetimes without offsets, and building ops arrays with the correct verbs and occurrence ids. Through Jentic you install once, import the Reassign REST API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Reassign takes event targets and verbs inside the request body of its batch operations, so rules bound which operations your agent may call, such as reading the schedule and booking work, not which events. You choose the operations it may call, so destructive ones like clearing the schedule, factory-resetting or deleting the account, or minting tokens are not included unless you add them.
Credential isolation
Your Reassign Personal Access Token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'book work into free time' or 'move an event', and Jentic returns the matching Reassign operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Reassign REST API through Jentic.
What authentication does the Reassign REST API use?
Per its OpenAPI spec, public operations take a bearer token in the Authorization header: either a Personal Access Token starting rsk_live_ or an OAuth 2.1 access token minted for the Reassign API v1 resource. Reads need the events:read or events:write scope and writes need events:write. App-only operations instead require the appSession scheme, an apiKey-type cookie named better-auth.session_token from a signed-in browser. Through Jentic, your token is stored encrypted by your own Jentic One instance and injected at execution time.
Is there a Reassign MCP server?
You don't need an MCP server to give your agent the Reassign REST API. Jentic connects it directly from the API Directory: import it, store your Personal Access Token once, and your agent calls it. Operations are discovered on demand, so the agent loads only the scheduling operation it needs instead of every tool definition.
Can I limit what my agent is allowed to do with the Reassign REST API?
Yes. A planning agent could get a rule that allows GET /api/v1/schedule, POST /api/v1/schedule/plan, POST /api/v1/backlog, and POST /api/v1/actions/undo, so it can read your day, book work, capture Inbox items, and undo its own changes, but cannot mint tokens, disconnect calendar sources, clear your schedule, or delete the account. Every call it makes is logged.
Does the Reassign REST API need a paid plan?
The spec states that public endpoints generally need Reassign Pro access, and that the 7-day free trial includes Reassign Pro. GET /api/v1/me/access reports the current access state for the token.
How does Reassign handle time zones?
Spans are a start and end as local datetimes in the form YYYY-MM-DDTHH:MM, with no seconds, offset, or Z, in the account's time zone. Responses name that time zone once as the top-level timezone field, dates are YYYY-MM-DD, and instants are ISO 8601 UTC strings.
What are the rate limits for the Reassign REST API?
The OpenAPI spec does not specify rate limits. Batch writes are bounded per call instead: POST /api/v1/events and POST /api/v1/backlog take 1 to 50 ops, and POST /api/v1/schedule/plan takes 1 to 20 requests. Check https://reassign.app for current usage limits.
How do I book a task into free time through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the Reassign REST API from the API Directory, and store a Personal Access Token with the events:write scope. Your agent searches for 'book work into free time', receives POST /api/v1/schedule/plan with its input schema, and calls it with a name, durationMinutes, and a time window. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED