Morgen So Morgen API

Name: Morgen API
Brand: Morgen API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbearer, apiKey24 EndpointsREST

For Agents

Read and modify a user's calendars, events, tasks, task lists, and virtual rooms across Google, Microsoft, iCloud, and other providers connected to Morgen.

Install Jentic One Beta

Connect the Morgen API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Morgen 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# 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 instance

Jentic 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 Morgen API.

List linked calendar accounts and their connected providers via /accounts/list

Create, update, and delete events on any connected calendar through the /events endpoints

Manage tasks and task lists alongside calendar events using the /tasks and /taskLists routes

GET STARTED

Start building with Morgen API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Morgen API, keeping it validated and agent-ready. Morgen is a calendar and task workspace that aggregates events across Google, Microsoft, iCloud, and other providers and adds task lists, virtual rooms, and integration controls. The API exposes 24 endpoints for managing calendar accounts, listing and editing events, creating tasks and task lists, configuring third-party integrations, and provisioning virtual meeting rooms. Authentication uses a bearer token or an Authorization API key header.

Use Cases

Patterns agents use Morgen API for, with concrete tasks.

★ Cross-Provider Calendar Scheduling

Morgen aggregates calendars from Google, Microsoft, iCloud, and other providers behind a single API surface, so an assistant can read availability and create events without integrating each provider directly. The /calendars/list and /events endpoints expose every connected source uniformly, and writes propagate back to the underlying provider. This collapses what would normally be three OAuth integrations into one.

Call GET /calendars/list to find the user's primary Google calendar, then POST to /events to create a 30-minute meeting with two attendees on tomorrow at 10:00 local time.

Task Triage from a Single Inbox

Morgen blends tasks and calendar events in one workspace. Agents can list every task across every connected task list, filter by due date, and reschedule or close them in bulk via the /tasks endpoints. This is useful for a daily-planner agent that drafts a focus list at the start of the day and updates statuses at the end.

List all tasks across the user's task lists, filter to those due in the next 24 hours, and update each completed task's status via the /tasks endpoint.

Virtual Room Provisioning for Meetings

Morgen can attach a virtual room to any event so attendees join via a stable URL. Agents create the room with /virtualRooms/create, attach it to an event, and update or remove it later. This is useful when a scheduling agent needs to add a video link to an event without forcing a specific provider on the user.

Create a Morgen virtual room via /virtualRooms/create and attach the resulting URL to an existing event using /events update.

AI Scheduling Agent via Jentic

An AI agent looking to schedule a meeting searches Jentic for the Morgen event creation operation, loads its input schema, and executes the call. The agent never sees the bearer token — Jentic injects it from the encrypted vault. The same flow handles task creation, integration connection, and identity reads.

Search Jentic for 'create a calendar event in Morgen', load the POST /events operation, and execute it to book a 1:1 with a teammate at 3pm tomorrow.

Key Endpoints

24 endpoints — jentic publishes the only available openapi specification for morgen api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/calendars/list

List all connected calendars

GET

/accounts/list

List linked calendar/task accounts

POST

/virtualRooms/create

Create a virtual meeting room

POST

/virtualRooms/update

Update an existing virtual room

POST

/integrations/{serviceName}/auth

Initiate auth for a provider integration

GET

/identity

Read the authenticated user's identity

POST

/identity/update

Update the authenticated user's identity

GET

/calendars/list

List all connected calendars

GET

/accounts/list

List linked calendar/task accounts

POST

/virtualRooms/create

Create a virtual meeting room

POST

/virtualRooms/update

Update an existing virtual room

POST

/integrations/{serviceName}/auth

Initiate auth for a provider integration

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Morgen bearer tokens and API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access — Jentic attaches the Authorization header at call time so raw tokens never enter the agent's prompt.

Intent-based discovery

Agents search Jentic with intents like 'create a calendar event' or 'list my tasks' and Jentic returns the matching Morgen operation along with its input schema, so the agent can pick the right endpoint without browsing docs.

Time to first call

Direct Morgen integration plus per-provider OAuth: 2-3 days to wire up auth, error handling, and retry logic. Through Jentic: under an hour — search, load, execute.

FAQs

Specific to using Morgen API through Jentic.

Why is there no official OpenAPI spec for Morgen API?

Morgen does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Morgen API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Morgen API use?

Morgen accepts a bearer token or an API key passed in the Authorization header. Through Jentic, the credential is stored in the encrypted vault and injected into each request — agents never receive the raw token in their context.

Can I create events on a Google Calendar through the Morgen API?

Yes. Once the user has connected a Google account via /integrations/{serviceName}/auth, that calendar appears in /calendars/list and you can create events on it with POST to the /events endpoints. Morgen handles the underlying Google Calendar write.

What are the rate limits for the Morgen API?

Morgen does not publish hard rate limits in the spec. Treat the API as fair-use per workspace and back off on 429 responses. Cache calendar and account lists rather than polling for every event read.

How do I schedule a meeting through Jentic?

Run pip install jentic, then search 'create a calendar event in Morgen', load the POST /events operation, and execute it with the meeting details. Jentic supplies the bearer token from your vault.

Is the Morgen API free?

Morgen offers a free personal tier and paid plans for teams and advanced scheduling features. API access is included with all paid plans; check morgen.so for current pricing.

Morgen So Morgen API

Connect the Morgen API to your agent

Capabilities

Start building with Morgen API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs