For a long time, Sharetru's REST API handled the administrative side of the platform, while moving files meant the web client, a secure link, or a script talking to an SFTP/FTPS server. That works — but not every system speaks FTP, and not every network team wants another set of firewall rules to open and maintain. Partner feeds at 2 a.m., nightly backups, a system that needs the same file every hour: all of that should be easy to automate from the tools you already run.
So we changed it. With our latest release, Sharetru's REST API can move files itself — your systems check for new files and move them on their own schedule, over native HTTPS, with nothing leaving your compliance boundary.
If you run IT, security, or the integrations that keep a regulated operation moving, this one's for you.
Plenty of file transfer can be scripted over SFTP/FTPS today, and many Sharetru customers do exactly that. But a lot of modern infrastructure — cloud jobs, schedulers, integration platforms, internal apps — is built to talk HTTPS. Getting it to drive an FTP client means extra tooling, extra moving parts, and firewall changes your network team has to approve. When automation is harder than it should be, files end up getting moved by hand, and "by hand" doesn't scale or run overnight.
That creates risk you don't see until something slips. A transfer that depends on one person's calendar is a transfer that happens late, or twice, or not at all when that person is out.
Our REST API started out managing the administrative side of Sharetru — users, groups, and permissions. Now it does the thing people actually spend their day on: it moves the files.
The new HTTPS File Transfer API lets your own systems push and pull files programmatically — no FTP client, no interactive login. Staged, resumable uploads and byte-range downloads mean that if a connection drops, you can resume an interrupted transfer instead of starting over.
Concretely, that looks like moving files to and from Sharetru from your scripts and jobs, including ones running in Microsoft Azure, automating partner exchange and backups, and running scheduled transfers that just happen.
API usage is metered: requests are rate-limited per second and count toward a monthly call allowance set by your plan. If you're planning high-volume or very large transfers, check your plan's API limits when you size the job.
You don't have to leave the API to manage who gets in. Through the same interface, you can add a user to a group and set their manager rights in one call as people and projects change, delegate scoped manager rights without handing over site-level governance, and drive group membership straight from your identity, HR, or provisioning systems so access stays accurate on its own.
There are new administrative, provisioning, and reporting endpoints alongside it — so the API isn't just a file pipe, it's a way to wire Sharetru into the operations you already run.
Here's the part worth saying out loud, because it reframes what Sharetru is. For years, you've had three ways to move files with us: interactively through the web-based client, over SFTP/FTPS/FTPeS, and through secure file-sharing links. Programmatic transfer over the REST API is the fourth — and it's the first one that's native HTTPS, with no FTP client or firewall rules needed.
Four distinct, governed ways to send and receive files, under one roof, with the same controls behind all of them. Pick the one that fits the job.
None of this is automation bolted on the side. Every API call runs inside the same posture as the rest of Sharetru: FedRAMP Moderate Authorized, encryption validated to the newest FIPS 140-3 federal standard, with full audit logs and retention. So the answer to "what did that automated job touch, and when?" is the same answer you'd give for anything a person did — it's all in the log.
That matters when the files in question are ePHI, PII, CUI, or ITAR-regulated data. You shouldn't have to choose between moving that data efficiently and being able to prove where it went.
Automation and governance usually pull against each other. Here they don't.
This matters even more if your internal collaboration lives in Microsoft GCC or GCC High. Those environments are built for internal work — not for governed external file exchange over standard protocols. Running Sharetru in parallel lets you automate external transfer and partner access without forcing every workflow through GCC, and without the admin overhead that usually comes with it.
These endpoints are useful on their own today. But they're also the foundation for what we're building next. Moving Sharetru from something you operate by hand to something your software can operate is the groundwork for a 2026 roadmap aimed squarely at automation, integration, and administrative control.
If you're evaluating file transfer platforms, the question isn't only what can a user do here? It's what can your systems do here, on their own, without giving up the audit trail? That's the question this release is built to answer.
The REST API is available now to all Sharetru customers whose plan includes it. The documentation is at developer.sharetru.com and code examples — in Python, PowerShell, Bash, PHP, and Node.js — are on GitHub: github.com/sharetru/api-files-upload.
Current customer? Reach us at support@sharetru.com and we'll point you at the right endpoints and your plan's API limits. New here and want to see it run in your environment? Grab a demo.