Scheduling
Outlook Calendar in your product and your AI agents, through one API
The Outlook Calendar toolkit covers calendars, events (list, read, create, update, delete), responses to meeting invitations (accept, decline, tentatively accept) and free/busy schedules, for Outlook.com and Microsoft 365 accounts. Customers connect with OAuth on your own app, and Connect renews the tokens and logs every execution.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/outlook_calendar_create_event/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"calendar_id": "<calendar_id>",
"start": {},
"end": {}
}
}How it works
From a connected customer to the first Outlook Calendar call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Outlook Calendar account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Outlook Calendar.
Book meetings from your product
Create an event with attendees and Outlook sends the invitations, with the online meeting join link returned by Get event.
Find a time that works
Call Get schedule for several people or rooms, read availabilityView and the busy blocks, then create the event in a free slot.
Assistant that handles invitations
An AI agent lists upcoming events and accepts, declines or tentatively accepts invitations, optionally proposing another time.
Tools
10 Outlook Calendar tools
- List calendarsGETLists the calendars of the user, with id, name, isDefaultCalendar, canEdit and owner. Use the id as calendar_id. Only the first page comes back.
- List eventsGETLists the events of a calendar between two times, with recurring events expanded into occurrences that have their own id. start and end come in UTC. Only the first page comes back: when the response has @odata.nextLink, ask again with a shorter window.
- Get eventGETReturns one event with its body as plain text, start and end in UTC, location, attendees with their responses, organizer, onlineMeeting with the join link, recurrence and webLink.
- Create eventPOSTCreates an event in a calendar and returns it with its id and webLink. With attendees, Outlook emails the invitations right away, and this cannot be turned off.
- Update eventPATCHChanges an event and returns it. Only the fields sent change. On a meeting the user organizes, Outlook emails the change to the attendees. Do not send a new body for an online meeting: the join details live in the body and would be lost.
- Delete eventDELETEDeletes an event from the calendar. When the user organizes the meeting, Outlook emails a cancellation to the attendees.
- Accept eventPOSTAccepts a meeting invitation and, unless sendResponse is false, emails the response to the organizer. The response is 202 with no body.
- Decline eventPOSTDeclines a meeting invitation, optionally proposing another time, and unless sendResponse is false emails the response to the organizer. The response is 202 with no body.
- Tentatively accept eventPOSTTentatively accepts a meeting invitation, optionally proposing another time, and unless sendResponse is false emails the response to the organizer. The response is 202 with no body.
- Get schedulePOSTReturns the free and busy times of people, distribution lists or rooms between two times. In availabilityView each digit is one slot: 0 free or working elsewhere, 1 tentative, 2 busy, 3 out of office. scheduleItems lists the busy blocks and workingHours the working hours. Only work or school accounts can call it.
OAuth with your product's app
You register your product's OAuth app once, with POST /api/merchants/credentials/outlook_calendar, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.
Questions about the Outlook Calendar toolkit
Do I need to build against the Outlook Calendar API?
No. Connect ships 10 Outlook Calendar tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Outlook Calendar account?
With the mode the toolkit accepts: OAuth with your product's app. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
