Backendless API Documentation

This is the complete API documentation for connecting to the Backendless 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 Backendless: Backendless is a backend-as-a-service platform for user management, data storage, file storage, caching, and atomic counters. Keep reading to get started.

Quickstart

Before you run your first Backendless request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Backendless connection — create or choose one in Connections. Note its connectionId.

Every Backendless action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/backendless/latest/actions/{actionSlug}

You need a MindCloud API Key and a Backendless connection. Then call an action such as Check Cache Key:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/backendless/latest/actions/check-cache-key" \
  --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 Backendless account that should run the action. MindCloud stores and refreshes the Backendless 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.

Backendless actions

All 40 published actions for this Backendless version. Each page documents the endpoint, arguments, and response controls.

• PUTAppend File
• POSTBulk Create Data Objects
• DELETEBulk Delete Data Objects
• PUTBulk Update Data Objects
• GETCheck Cache Key
• PUTCompare And Set Counter
• POSTCopy File Or Folder
• GETCount Data Objects
• GETCount Directory Items
• POSTCreate Data Object
• POSTCreate Directory
• PUTDecrement Counter
• DELETEDelete Cache Value
• DELETEDelete Data Object
• DELETEDelete File
• PUTExtend Cache TTL
• GETGet Cache Value
• GETGet Counter Value
• GETGet Data Object
• GETGet First Data Object
• GETGet Last Data Object
• PUTIncrement Counter
• GETList Counters
• GETList Data Objects
• GETList Directory
• GETList Root Directory
• GETLogin User
• GETLogout User
• PUTMove File Or Folder
• POSTPut Cache Value
• POSTRegister User
• PUTRename File Or Folder
• GETRestore User Password
• POSTSave Binary File
• PUTUpdate Data Object
• PUTUpdate User
• POSTUpload File
• PUTUpsert Data Object
• GETValidate User Login
• GETValidate User Token

Related apps

More IT Operations apps on the Universal API, behind the same REST shape. Or browse all apps.

GitHubNetlifyMySQLPostgreSQLFirebasePagerDutyGoogle Workspace AdminAdalo