SharePoint Python API Docs | dltHub

Build a SharePoint-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

SharePoint REST API supports CRUD operations for lists and items; official documentation is available at Microsoft Learn; complete property references may be found in JSOM documentation. The REST API base URL is https://{site_url}/_api and All requests, particularly for remote add-ins, require a Bearer token for authentication..

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 SharePoint data in under 10 minutes.


What data can I load from SharePoint?

Here are some of the endpoints you can load from SharePoint:

ResourceEndpointMethodData selectorDescription
web_listsweb/listsGETd/results or valueRetrieves all lists in a specific SharePoint site
list_by_titleweb/lists/GetByTitle('{list_title}')GETd/results or valueRetrieves a specific list by its title
list_itemsweb/lists/getbytitle('{list_name}')/itemsGETd/results or valueRetrieves items from a specific list
sitesiteGETRetrieves information about the current site
webwebGETRetrieves information about the current web
list_item_versionsweb/lists/getbytitle('{list_name}')/items({item_id})/versionsGETd/results or valueRetrieves versions of a specific list item

How do I authenticate with the SharePoint API?

Authentication for the SharePoint REST API typically involves OAuth 2.0, requiring a Bearer token to be passed in the Authorization header for each request.

1. Get your credentials

Instructions for obtaining API credentials from a dashboard are not directly available in the provided documentation. SharePoint authentication for add-ins usually involves registering an add-in and configuring permissions, often through Azure Active Directory, to obtain the necessary client ID, client secret, and tenant ID for OAuth 2.0 flows.

2. Add them to .dlt/secrets.toml

[sources.sharepoint_sp2019_api_source] access_token = "your_access_token_here" site_url = "https://your_sharepoint_site.sharepoint.com"

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 SharePoint 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 sharepoint_sp2019_api_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline sharepoint_sp2019_api_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 web_lists and list_items from the SharePoint 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 sharepoint_sp2019_api_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{site_url}/_api", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "web_lists", "endpoint": {"path": "web/lists", "data_selector": "d/results or value"}}, {"name": "list_items", "endpoint": {"path": "web/lists/getbytitle('{list_name}')/items", "data_selector": "d/results or value"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sharepoint_sp2019_api_pipeline", destination="duckdb", dataset_name="sharepoint_sp2019_api_data", ) load_info = pipeline.run(sharepoint_sp2019_api_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("sharepoint_sp2019_api_pipeline").dataset() sessions_df = data.web_lists.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM sharepoint_sp2019_api_data.web_lists LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("sharepoint_sp2019_api_pipeline").dataset() data.web_lists.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 SharePoint 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 SharePoint?

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