M365

[amirhouieh]

We start SharePoint.
The entry point with share point ia defined as follows:

• SharePoint/ Website/ document library

At this stage we only use document libraries.

Service and API Endpoints with Data Types

SharePoint

Operation	API Endpoint	Data Types
List Sites	GET /sites?search={query}	Sites
Access Specific Site	GET /sites/{site-id}	Site details
Access Lists	GET /sites/{site-id}/lists	Lists in a Site
Access Documents	GET /sites/{site-id}/drive/root:/{path}:/children	Documents in libraries (Word, PPT, Excel, PDF)

Teams

Operation	API Endpoint	Data Types
List Teams	GET /teams	Teams
Access Channels	GET /teams/{team-id}/channels	Channels within a Team
Access Messages	GET /teams/{team-id}/channels/{channel-id}/messages	Messages within a Channel

OneDrive

Operation	API Endpoint	Data Types
List Files/Folders	GET /me/drive/root/children	Files and folders
Access Specific File	GET /me/drive/items/{item-id}	Specific file details
File Content	GET /me/drive/items/{item-id}/content	Content of a specific file

Data Syncing

Initial Data Fetching

Upon service initialization, utilize the specified API calls to retrieve all existing data from the selected SharePoint lists, Teams channels, and OneDrive folders.

Real-time or Interval Data Syncing

Webhooks (Real-time Notifications)

Feature	Description
Subscription	Subscribe to resource changes via POST /subscriptions.
Notification	Receive notifications at the specified notificationUrl.
Use Case	Best for applications requiring immediate data updates.

Delta Queries (Incremental Changes)

Feature	Description
Initial Request	Use GET /me/drive/root/delta to fetch all data and a delta token/link.
Subsequent Requests	Use the delta token to fetch updates since the last request.
Use Case	Suitable for applications where periodic updates are adequate.

Choosing Sync Method

• Webhooks for real-time updates.
• Delta Queries for periodic syncing.
• Hybrid approach can optimize immediacy and API efficiency, tailored to application needs.