SharePoint APIConnect SharePoint without building on its API
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. If you're reading the docs because you need SharePoint to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across SharePoint and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessSelf-serve
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.
Building on the SharePoint API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get SharePoint credentials, and manage tokens and refreshes. | Connect your SharePoint account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the SharePoint task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting SharePoint work off someone's desk, the build is the slow part.
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.
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. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
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.
Connect SharePoint without the build.
Drop your work email and pick a time. We'll show you Caddi running your SharePoint workflow end to end.