-
Notifications
You must be signed in to change notification settings - Fork 2
10 API Introduction
Преподобный Ален edited this page Feb 18, 2026
·
1 revision
- Base endpoint: localhost:8080
- All endpoints return either a JSON object or a JSON array, depending on the number of records in the response. To override this behavior, add the query parameter
?data_array=true-- the response will then always be a JSON array regardless of the number of records. - Endpoints ending with
/listalways return a JSON array.
- HTTP
4XXreturn codes are used for malformed requests -- the issue is on the client side. - HTTP
5XXreturn codes are used for internal errors -- the issue is on the server side. It is important NOT to treat this as a failed operation. The execution status is UNKNOWN and may have been successful.
- Any endpoint may return an error.
Example response:
{
"error": {
"code": 404,
"message": "Not Found"
}
}- For
GETendpoints, parameters must be sent as a query string. - For
POSTendpoints, some parameters may be sent as a query string and some as a request body:- When sending parameters in the request body, the following content types are supported:
-
application/x-www-form-urlencodedfor query string encoding -
multipart/form-datafor HTML forms -
application/jsonfor JSON
-
- When sending parameters in the request body, the following content types are supported:
- Parameters may be sent in any order.
Concepts
API Guide
Authentication & Session
- Connection
- Registration
- Authorization (OAuth 2.0)
- Sign In
- Sign Out
- Password Recovery
- Verification Codes
- Authentication
- Authorization
- Who Am I?
Core Services
Object & Workflow Endpoints
Schema & Internals
Configuration Developer Guide
- Configuration Guide
- Creating an Entity
- Creating a Document
- Creating a Reference
- Workflow Customization
- REST Endpoint Guide
- Event Handler Guide
Operations