VSCO Workspace API Documentation
This is the complete API documentation for connecting to the VSCO Workspace 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 VSCO Workspace: Manage studio leads, jobs, galleries, orders, and payments. Keep reading to get started.
Quickstart
Before you run your first VSCO Workspace 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 VSCO Workspace connection — create or choose one in Connections. Note its
connectionId.
Every VSCO Workspace action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/vSCOWorkspace/latest/actions/{actionSlug}You need a MindCloud API Key and a VSCO Workspace connection. Then call an action such as Get Contact:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/vSCOWorkspace/latest/actions/get-contact" \
--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 VSCO Workspace account that should run the action. MindCloud stores and refreshes the VSCO Workspace 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.
VSCO Workspace actions
All 30 published actions for this VSCO Workspace version. Each page documents the endpoint, arguments, and response controls.
- POSTApply Payment to Order
- POSTCreate Contact
- POSTCreate Event
- POSTCreate File
- POSTCreate Gallery
- POSTCreate Job
- POSTCreate Order for Job
- POSTCreate Payment
- GETGet Contact
- GETGet Event
- GETGet File
- GETGet Gallery
- GETGet Job
- GETGet My Studio
- GETGet Order
- GETGet Payment
- GETList Contacts
- GETList Events
- GETList Files
- GETList Galleries
- GETList Jobs
- GETList Orders
- GETList Orders for Job
- GETList Payments
- GETList Payments for Job
- PUTUpdate Contact
- PUTUpdate Event
- PUTUpdate Gallery
- PUTUpdate Job
- PUTUpdate Order
Related apps
More Sales & CRM apps on the Universal API, behind the same REST shape. Or browse all apps.