POST a file over HTTPS and have it land in SharePoint
POST a file to your DocEvent endpoint and it is delivered into a Microsoft 365 SharePoint document library. Your application never touches the Microsoft Graph API, app registrations or tokens — it just makes an ordinary multipart upload.
From
HTTP Upload
To
SharePoint
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How HTTP Upload to SharePoint routing works
Source
HTTP Upload
Files arrive via HTTP POST to a dedicated DocEvent channel endpoint.
DocEvent Channel
routes · retries · logs
Destination
SharePoint
Files are delivered into a SharePoint document library.
1
File arrives via HTTP Upload
REST endpoint accepts multipart/form-data file uploads with optional authentication headers.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to SharePoint
Delivery into a Microsoft 365 SharePoint document library through the Microsoft Graph API, using a reusable Microsoft connection rather than a secret pasted onto the endpoint. Pick the site, library and destination folder, and decide what happens when the name already exists — keep both, replace it (SharePoint keeps the version history), or fail the delivery. Large files are uploaded in chunks.
Common use cases
Real workflows that teams automate with a HTTP Upload → SharePoint channel.
- Let a web app or form upload straight into a SharePoint library
- Give an API client a SharePoint destination without Graph code
- Collect field or customer uploads into Microsoft 365
- Send application output to SharePoint with one HTTPS call
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the HTTP Upload or SharePoint side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
HTTP Upload
REST endpoint accepts multipart/form-data file uploads with optional authentication headers.
Files arrive via HTTP POST to a dedicated DocEvent channel endpoint.Destination:
SharePoint
Delivery into a Microsoft 365 SharePoint document library through the Microsoft Graph API, using a reusable Microsoft connection rather than a secret pasted onto the endpoint. Pick the site, library and destination folder, and decide what happens when the name already exists — keep both, replace it (SharePoint keeps the version history), or fail the delivery. Large files are uploaded in chunks.
Files are delivered into a SharePoint document library.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages
Related channel integrations
Other sources to SharePoint
- Amazon S3 → SharePoint
- Email → SharePoint
- AS2 → SharePoint
- Filerouter (on-premise) → SharePoint
- FTP Pull → SharePoint
- SFTP Pull → SharePoint
- S3 Compatible (pull) → SharePoint
- GCS Blob Pull → SharePoint
- Azure Blob Pull → SharePoint
- Azure Data Lake Pull → SharePoint
- Azure Files Pull → SharePoint
- SharePoint → SharePoint
- DocEvent Agent (on-prem) → SharePoint