SendSafely API Documentation
This is the complete API documentation for connecting to the SendSafely API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.
MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.
Meet SendSafely: Secure file exchange and workspace management for SendSafely packages, recipients, directories, files, and contact groups. Keep reading to get started.
Quickstart
Before you run your first SendSafely request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one SendSafely connection — create or choose one in Connections. Note its
connectionId.
Every SendSafely action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/sendSafely/latest/actions/{actionSlug}You need a MindCloud API Key and a SendSafely connection. Then call an action such as Get Contact Group:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/sendSafely/latest/actions/get-contact-group" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--get \
--data-urlencode "connectionId=$CONNECTION_ID"Every response comes back in the same envelope, with your rows in a data array:
{
"success": true,
"data": [
{ "id": "1042", "name": "Ava" }
],
"meta": {}
}After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.
Authentication
Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected SendSafely account that should run the action. MindCloud stores and refreshes the SendSafely credentials behind that connection, so you never send provider tokens with your requests.
Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.
SendSafely actions
All 40 published actions for this SendSafely version. Each page documents the endpoint, arguments, and response controls.
- PUTAdd Contact Group Member
- PUTAdd Contact Group to Package
- POSTAdd File
- POSTAdd Recipient
- POSTAdd Recipients
- POSTCopy File To Workspace
- POSTCreate Contact Group
- POSTCreate Package
- POSTCreate Subdirectory
- DELETEDelete Contact Group
- PUTDelete Contact Group from Package
- DELETEDelete Directory
- DELETEDelete Package
- DELETEDelete Package File
- DELETEDelete Recipients
- PUTFinalize Package
- GETGet Contact Group
- GETGet Directory
- GETGet File Information
- GETGet Package Information
- GETGet Recipient
- GETGet User Information
- GETGet Workspace Activity Log
- GETList Archived Packages
- GETList Collaborators
- GETList Package Permissions
- GETList Received Packages
- GETList Sent Packages
- GETList User Contact Groups
- GETList Workspace Packages
- PUTMove Directory
- PUTMove Workspace File
- PUTRemove Contact Group Member
- DELETERemove Recipient
- PUTRename Directory
- GETSearch Package
- PUTUpdate File
- PUTUpdate Package
- PUTUpdate Recipient
- GETVerify Credentials
Related apps
More Content & Files apps on the Universal API, behind the same REST shape. Or browse all apps.