Microsoft SharePoint
Microsoft SharePoint is a web-based collaborative platform that integrates with Microsoft Office. It provides enterprise content management, document management, and collaboration capabilities.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Microsoft SharePoint the way a machine reads it — 89 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Microsoft SharePoint scores 61.1/100 (strong), with a separate agent-readiness read of 81/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Microsoft SharePoint
Each block below is one kind of artifact we hold for Microsoft SharePoint. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
SharePoint CSOM (Client-Side Object Model)
Client-side object model for SharePoint that provides access to SharePoint objects through .NET managed or JavaScript libraries.
SharePoint Webhooks API
SharePoint webhooks provide a way to get notified about changes to SharePoint lists and document libraries.
Microsoft SharePoint Files API
File upload, download, and management
Microsoft SharePoint Items API
List item operations
Microsoft SharePoint Lists API
List and library operations
Microsoft SharePoint Search API
Search query operations
Microsoft SharePoint Sites API
Site and web operations
Microsoft SharePoint User Profiles API
User profile operations
Scroll within the panel for all 8 ·
Arazzo Workflows 7
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
SharePoint Ensure a List Item Exists
Find an item by title and create it only when missing, then read it back.
ARAZZOSharePoint List Item Full Lifecycle
Create, read, update, verify, and delete a list item as an end-to-end conformance run.
ARAZZOSharePoint Provision a List and Seed Its First Item
Create a list only if it does not already exist, read it back, and seed an item.
ARAZZOSharePoint Search for a Document and Download It
Run a search query, take the top hit's path, and fetch the document bytes.
ARAZZOSharePoint Verify Site Connection and Identity
Escalate from a cheap reachability probe to identity, site detail, and visible lists.
ARAZZOSharePoint Site Content Inventory
Walk a site from its title down through lists, recent items, and library files.
ARAZZOSharePoint Upload a Document and Verify It
Survey a library folder, upload a file with overwrite, then read the bytes back.
ARAZZOScroll within the panel for all 7 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
sharepoint-mcp.yml
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Sharepoint Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Sharepoint Finops
FINOPSFeatures 12
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Sites and Webs
Create, read, update, and delete SharePoint sites and subsites.
Lists and Libraries
Full CRUD operations on lists, document libraries, and list items.
Document Management
Upload, download, check in/out, and manage documents and file versions.
Folders and Files
Create folder hierarchies and manage files within document libraries.
Permissions and Security
Manage site, list, and item-level permissions with role assignments.
Search
Full-text search across sites, documents, and content using the Search REST API.
User Profiles
Access user profile properties, people search, and organizational data.
Content Types
Manage content types, site columns, and metadata schemas.
Webhooks
Subscribe to change notifications for lists and libraries via webhooks.
Microsoft Graph Integration
Access SharePoint data through Microsoft Graph API for unified Microsoft 365 integration.
Batch Requests
Combine multiple REST operations into a single batch request.
OData Query Support
Filter, select, expand, and order data using OData query operators.
Scroll within the panel for all 12 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Sharepoint Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Microsoft SharePoint API Rules
SPECTRALMicrosoft SharePoint API Rules
SPECTRALJSON Schema 11
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
FileCollection
JSON SCHEMAFile
JSON SCHEMAListCollection
JSON SCHEMAListCreateRequest
JSON SCHEMAListItemCollection
JSON SCHEMAListItemCreateRequest
JSON SCHEMAListItem
JSON SCHEMAList
JSON SCHEMASearchResult
JSON SCHEMAUserProfile
JSON SCHEMAWeb
JSON SCHEMAScroll within the panel for all 11 ·
JSON Structure 11
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Sharepoint File Collection Structure
JSON STRUCTURESharepoint File Structure
JSON STRUCTURESharepoint List Collection Structure
JSON STRUCTURESharepoint List Create Request Structure
JSON STRUCTURESharepoint List Item Collection Structure
JSON STRUCTURESharepoint List Item Create Request Structure
JSON STRUCTURESharepoint List Item Structure
JSON STRUCTURESharepoint List Structure
JSON STRUCTURESharepoint Search Result Structure
JSON STRUCTURESharepoint User Profile Structure
JSON STRUCTURESharepoint Web Structure
JSON STRUCTUREScroll within the panel for all 11 ·
Examples 11
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Sharepoint File Example
EXAMPLESharepoint List Example
EXAMPLESharepoint List Item Example
EXAMPLESharepoint Web Example
EXAMPLEScroll within the panel for all 11 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Sharepoint Trust Center
SOC 1 Type 2, SOC 2 Type 2, SOC 3, ISO 27001, ISO 27017, ISO 27018, ISO 27701, ISO 22301, ISO 9001, FedRAMP High, HIPAA / HITECH, HITRUST CSF, PCI DSS, GDPR, CSA STAR
SECURITYScopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Document Automation
Automate document upload, metadata tagging, and approval workflows.
Intranet Content Management
Programmatically manage site pages, news posts, and navigation.
Data Integration
Sync SharePoint list data with external databases and applications.
Migration
Migrate content between SharePoint sites or from file shares to SharePoint.
Custom Applications
Build SPFx web parts and extensions with SharePoint Framework.
Compliance and Governance
Manage retention policies, sensitivity labels, and audit logs.
Search Integration
Build custom search experiences with facets, refiners, and result types.
Power Automate Flows
Trigger and manage automated workflows based on SharePoint events.
Scroll within the panel for all 8 ·
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Microsoft 365
Native integration with Teams, OneDrive, Outlook, and other Microsoft 365 apps.
Microsoft Graph
Unified API access to SharePoint alongside all Microsoft 365 services.
Power Platform
Power Apps, Power Automate, and Power BI integration for low-code solutions.
Azure
Azure AD for authentication, Azure Functions for serverless processing.
Teams
SharePoint powers file storage and document collaboration in Microsoft Teams.
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
SharePoint Online
Cloud-hosted SharePoint as part of Microsoft 365 with REST and Graph APIs.
SharePoint Server
On-premises SharePoint with REST, CSOM, and server-side object model.
SharePoint Framework (SPFx)
Modern client-side development framework for building web parts and extensions.
Resources
Every other property we hold for Microsoft SharePoint — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 13
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 13 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 6
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/sharepoint · machine-readable index on apis.io