Meetings
Find, search and schedule meetings.
Morse for developers
Your meetings.Your workflows.One API.
Build with meetings, transcripts and knowledge using one personal access token.
Tokens are part of Scale. See plans
- Personal access tokens
- OpenAPI reference
- Live event streams
Everything you need to build.
Meetings, transcripts, notes and knowledge, all through a single, simple API.
Transcripts
Read what was said, live or after the call.
Notes
Get meeting summaries and action items.
Knowledge
Work with your folders and saved knowledge.
Voice notes
Access recordings and their audio.
Live feeds
Follow meetings as transcripts and notes change.
One token. Your account. Your permissions.
Explore the API referenceFrom token to first request.
Get up and running in minutes. A single token gives you access to your meetings, transcripts and more.
- Create a token
Settings → API tokens → New token.
- Name it and set an expiry
Choose a duration that fits your workflow.
- Copy it once
Keep it safe. It is shown only once.
Your first request
export MORSE_TOKEN=mp_…200 OK[ {"title": "Pricing review", "duration_minutes": 30}]Example response
Built for scripts.Ready for agents.
Give an assistant a token to work with your account and permissions. Anything that can make an HTTP request can use one, with nothing to install and nothing to approve.
Read the agent instructionsAn agent holding a token reaches your meetings, notes and knowledge through Morse.
Know the boundaries.
A few important things to keep in mind when building with Morse.
- Token management stays in Settings
- Create, revoke and manage tokens in your account settings, never over the API.
- Browser sign-out does not revoke tokens
- Signing out in your browser will not revoke active tokens. Manage them in Settings.
- Google Calendar needs your approval
- Google needs a person to click Allow. Once connected, events read and write with a token.
- Use a server, a script or an agent
- The API sends no CORS headers, so a web page on another site cannot call it.
- Tokens act as members, not guests
- Tokens work with your account and permissions, just like you.
A few things before you build.
Still have a question?hello@onmorse.com
How do I create a token?
Open Settings → API tokens in Morse and choose New token. Name it, choose when it expires, then copy it. The token starts mp_, is 49 characters long, and is shown exactly once.
What can my token access?
It acts as you. It reaches your meetings, transcripts, notes, knowledge, voice notes and live feeds, and it can schedule meetings and invite people. If you are an admin, it reaches the admin pages too.
Can I use Morse with an AI agent?
Yes. Morse publishes a block of instructions you paste into an assistant along with your token. It then fetches the OpenAPI document and calls routes in your account, asking you before anything irreversible.
Can I call the API from a browser?
No. The API sends no CORS headers, so a web page on another site cannot call it. Call it from a server, a script or an agent instead. A browser’s EventSource also cannot send the header live feeds need.
When does my token expire?
Whenever you chose: 30, 60 or 90 days, a day you pick, or never. A token left unused for a year stops working. Revoke one in Settings and it stops on its next request.
How do file uploads work?
In three steps: ask Morse where to put the file, send it straight to storage, then tell Morse it is there. Files never pass through Morse’s own server. Photos, voice-note audio and knowledge files all work this way.