Integrate the SharePoint API.Caddi writes and runs the integration for you.
SharePoint has a REST API through Microsoft Graph. Self-serve for any developer who registers an Entra app, but data access requires a Microsoft 365 tenant with SharePoint and admin/user consent.
- 99%of agent runs complete successfully
- ~45 minon average to build your first agent
- 1M+back-office tasks completed
The connection is a project before it does anything.
Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. Resource-unit throttling per app per tenant (e.g., 1,250 RU/min and 1.2M RU/24h for tenants under 1,000 licenses) and 3,000 requests per user per 5 minutes.
Register an app, store SharePoint credentials, refresh tokens and code around the rate limits.
Connect your SharePoint account once. Caddi holds the connection.
The job doesn't stop at SharePoint.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The SharePoint API only reaches SharePoint.
Each extra system is another API, another set of credentials, another integration to own.
One automation runs across every tool the job touches, each through its API.
Someone has to own the code.
API versions change, fields get added and your process moves.
A developer patches and redeploys the integration each time.
The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.
What the SharePoint API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 via Microsoft Entra ID (delegated or app-only)
- Who can get access
- Self-serve for any developer who registers an Entra app, but data access requires a Microsoft 365 tenant with SharePoint and admin/user consent.
- What it covers
- Sites, lists, list items, document libraries (drives), files (driveItems), permissions, and pages.
- Limits
- Resource-unit throttling per app per tenant (e.g., 1,250 RU/min and 1.2M RU/24h for tenants under 1,000 licenses) and 3,000 requests per user per 5 minutes.
Official docs: learn.microsoft.com. Checked September 2026. Vendors change access terms, so confirm with SharePoint before you build.
When to build the SharePoint integration in-house
When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting SharePoint work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the SharePoint API for
Cash Receipt Reconciliation
Caddi extracts invoice and payment details from cash receipt emails and writes them to the correct tracker row, reducing manual reconciliation work for billing and finance teams.
Authorization Document Renaming
Caddi verifies claim details and renames treatment authorization and vocational approval documents to the required naming convention.
Initials-Based File Naming
Caddi looks up claim numbers in the matter system to confirm the assigned paralegal and renames documents with the correct initials.
Check PDF Uploads
Caddi renames check PDFs to a standard format, uploads them to the correct matter, and shares them with clients through the client portal.
Everything Caddi does with SharePoint.
SharePoint API questions
Does SharePoint have an API?
Yes. SharePoint has a REST API through Microsoft Graph, authenticated with OAuth 2.0 via Microsoft Entra ID (delegated or app-only). The official documentation is at https://learn.microsoft.com/en-us/graph/api/resources/sharepoint.
How do I get access to the SharePoint API?
Self-serve for any developer who registers an Entra app, but data access requires a Microsoft 365 tenant with SharePoint and admin/user consent.
Does the SharePoint API have rate limits?
Resource-unit throttling per app per tenant (e.g., 1,250 RU/min and 1.2M RU/24h for tenants under 1,000 licenses) and 3,000 requests per user per 5 minutes.
Can I connect SharePoint to my other tools without writing code against its API?
Yes. With Caddi you show the SharePoint task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across SharePoint and the other tools the job touches. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.
Do I need a developer to automate SharePoint with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for SharePoint is reviewed before it runs in production, and every run is logged.