Microsoft Office 365 Outlook Calendar Python API Docs | dltHub

Build a Microsoft Office 365 Outlook Calendar-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Microsoft Office 365 Outlook Calendar REST API allows programmatic access to calendar data; it uses standard HTTP methods for CRUD operations. Documentation is available at https://learn.microsoft.com/en-us/graph/outlook-calendar-api-overview. The REST API base URL is https://graph.microsoft.com/v1.0 and all requests require a Bearer access token (OAuth 2.0).

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Microsoft Office 365 Outlook Calendar data in under 10 minutes.


What data can I load from Microsoft Office 365 Outlook Calendar?

Here are some of the endpoints you can load from Microsoft Office 365 Outlook Calendar:

ResourceEndpointMethodData selectorDescription
me_events/me/eventsGETvalueList events from the signed-in user's mailbox
users_events/users/{user-id}/eventsGETvalueList events in a specified user's calendar
calendars/me/calendarsGETvalueList user's calendars
users_calendars/users/{user-id}/calendarsGETvalueList calendars for a specific user
calendar_view/users/{user-id}/calendarView?startDateTime={start}&endDateTime={end}GETvalueGet events in a time range (expanded instances)
groups_calendar_events/groups/{group-id}/calendar/eventsGETvalueList events in a Group calendar
calendars_calendarid_events/me/calendars/{calendar-id}/eventsGETvalueList events in a specific calendar
event_get/me/events/{event-id}GET(single object)Get a single event's properties
create_event/me/eventsPOSTvalueCreate an event (included for completeness)

How do I authenticate with the Microsoft Office 365 Outlook Calendar API?

Microsoft Graph uses OAuth 2.0 access tokens issued by Azure AD. Include header Authorization: Bearer <access_token> on every request.

1. Get your credentials

  1. Register an app in Azure AD (Azure Portal > App registrations > New registration). 2) Note Application (client) ID and Directory (tenant) ID. 3) Under Certificates & secrets create a client secret (if using delegated or app-only credentials) and copy its value. 4) Grant required API permissions (e.g., Calendars.Read, Calendars.Read.Shared) and grant admin consent if using app-only. 5) Acquire an access token from Azure AD token endpoint (https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token) using authorization code or client_credentials flow with scope https://graph.microsoft.com/.default or offline_access openid profile Calendars.Read.

2. Add them to .dlt/secrets.toml

[sources.microsoft_o365_outlook_calendar_source] client_id = "your_client_id" client_secret = "your_client_secret" tenant_id = "your_tenant_id"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Microsoft Office 365 Outlook Calendar API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python microsoft_o365_outlook_calendar_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline microsoft_o365_outlook_calendar_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset microsoft_o365_outlook_calendar_data The duckdb destination used duckdb:/microsoft_o365_outlook_calendar.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline microsoft_o365_outlook_calendar_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads me_events and calendars from the Microsoft Office 365 Outlook Calendar API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def microsoft_o365_outlook_calendar_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://graph.microsoft.com/v1.0", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "me_events", "endpoint": {"path": "me/events", "data_selector": "value"}}, {"name": "calendars", "endpoint": {"path": "me/calendars", "data_selector": "value"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="microsoft_o365_outlook_calendar_pipeline", destination="duckdb", dataset_name="microsoft_o365_outlook_calendar_data", ) load_info = pipeline.run(microsoft_o365_outlook_calendar_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("microsoft_o365_outlook_calendar_pipeline").dataset() sessions_df = data.me_events.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM microsoft_o365_outlook_calendar_data.me_events LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("microsoft_o365_outlook_calendar_pipeline").dataset() data.me_events.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Microsoft Office 365 Outlook Calendar data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Microsoft Office 365 Outlook Calendar?

Request dlt skills, commands, AGENT.md files, and AI-native context.