How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Backendless Data API

CRUD and search over schema-backed database tables.

Backendless Data API is one of 8 APIs that Backendless publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Data. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against a single base URL, https://api.backendless.com/{app-id}/{rest-api-key}.

6 operations 3 paths 2 schemas 1 DELETE3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.backendless.com/{app-id}/{rest-api-key}/data
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Backendless Data API declares 1 security scheme for authenticating requests. An API key is passed in the header as user-token (userToken). By default, every request must be authenticated.

  • userToken — Session token returned by POST /users/login. Required on operations that run in the context of an authenticated user. The application id and REST API key that…

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Data 6

CRUD and search over schema-backed database tables.

POST
/data/{table-name}
Save a single object
createObject 1 param body → 200400
GET
/data/{table-name}
Find objects
findObjects 8 params → 200400
GET
/data/{table-name}/{object-id}
Retrieve object by id
getObjectById 2 params → 200404
PUT
/data/{table-name}/{object-id}
Update a single object
updateObject 2 params body → 200400
DELETE
/data/{table-name}/{object-id}
Delete a single object
deleteObject 2 params → 200404
GET
/data/{table-name}/count
Count objects
countObjects 2 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are DataObject (5 properties), ErrorResponse (2 properties). Each schema is shown below with its type and property counts.

DataObject
object
A persisted object. Includes Backendless system properties.
5 properties
ErrorResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

backendless-data-api-openapi.yml Raw ↑

Other APIs Backendless publishes across the network.

Backendless Cache API
Backendless CloudCode API
Backendless Counters API
Backendless Files API
Backendless Geo API
Backendless Messaging API
Backendless Users API
Where this information came from

This is an independent, third-party profile of Backendless Data API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.