Provider-Hosted SharePoint File Connector
Budget: $30 – $250 USD
I need a provider-hosted SharePoint add-in that can both push documents from any SharePoint library to our already-running REST API and pull the processed file back into the same (or a chosen) library. The API endpoint is live and documented, so the focus here is on the SharePoint side: authentication, file transfer, and a clean user experience inside the tenant.
Here’s how I picture the flow:
• User selects one or multiple items in a library and chooses the custom ribbon/ECB action you build.
• Add-in packages the file(s), calls our HTTPS endpoint, passes the required headers (token and metadata are provided).
• When the API finishes, the add-in retrieves the returned file and places it back, preserving or updating metadata as needed.
Please build this with standard provider-hosted patterns (C#, .NET, CSOM or PnP Core, registered Azure AD app for OAuth). A lightweight UI—SharePoint Framework panel or classic dialog—is fine as long as it’s intuitive.
Deliverables:
1. Source code and deployable package for the add-in.
2. Setup instructions for app registration, permissions, and deployment.
3. Brief README describing how to extend or modify the API call parameters.
Acceptance will be based on successfully transferring a sample Word document and receiving the processed version in the target library without data loss.
Here’s how I picture the flow:
• User selects one or multiple items in a library and chooses the custom ribbon/ECB action you build.
• Add-in packages the file(s), calls our HTTPS endpoint, passes the required headers (token and metadata are provided).
• When the API finishes, the add-in retrieves the returned file and places it back, preserving or updating metadata as needed.
Please build this with standard provider-hosted patterns (C#, .NET, CSOM or PnP Core, registered Azure AD app for OAuth). A lightweight UI—SharePoint Framework panel or classic dialog—is fine as long as it’s intuitive.
Deliverables:
1. Source code and deployable package for the add-in.
2. Setup instructions for app registration, permissions, and deployment.
3. Brief README describing how to extend or modify the API call parameters.
Acceptance will be based on successfully transferring a sample Word document and receiving the processed version in the target library without data loss.