API Endpoints

The controlled connection between your gateway and every client application.

WBert exposes backend capabilities through configured API endpoints. Clients call the gateway, the gateway validates authentication and permissions, then routes the request to the correct backend service or business tool.

Gateway routing JWT security Role permissions Database CRUD Business logic

WEBWeb AppReact, Angular, MVC or custom UI

APPMobile AppiOS, Android or hybrid clients

DESKDesktop ToolsInternal tools and operators

GWGatewayAuthentication, routing and policies

ACLSecurityRoles, permissions and organization context

DBDatabase APIsCRUD, functions and schema operations

C#ProcessesAdvanced business logic

Configured endpoints instead of hidden backend wiring

API Endpoints make backend actions visible and testable from the administration area. Developers can inspect request examples, understand parameters, and keep the client contract aligned with the backend.

Group endpoints by area such as Authentication, Database JSON CRUD and Application Structure.
Keep request payloads visible without exposing real production credentials.
Use the same endpoint catalog as technical documentation for the client team.

Configured endpoints Authentication auth.Login auth.Logout auth.GetSession auth.GetPermissions

Database JSON CRUD Database db.GetList db.Get db.Insert db.ExecuteFunction

Security and permissions remain part of the endpoint definition

The client does not call backend services directly. Requests pass through the gateway, where user identity, organization membership, roles and endpoint permissions can be checked before the action is executed.

Authenticate users with email, Google, Apple or JWT-based sessions.
Map endpoint access to roles and permission checks.
Keep Special Admin unrestricted while normal organizations follow their plan and ACL limits.

Client

Gateway

Auth

Permissions

Service

Payloads that the client can reuse immediately

Endpoint examples help the frontend understand how to call backend actions. The payloads are kept generic and safe, while still showing the correct request shape.

Database endpoints can receive connector, table, columns, filters and paging.
Structure endpoints can return entities, fields, relations and indexes.
Process endpoints can execute advanced backend logic through a controlled interface.

Parameters JSON

{
  "connector": "main",
  "table": "customers",
  "columns": ["id", "name"],
  "where": {
    "is_active": true
  },
  "orderBy": "name",
  "limit": 50,
  "offset": 0
}

One API surface for client applications and backend tools.

WBert API Endpoints give the client a clear gateway to authentication, database operations, application structure and business logic, while administrators keep control of permissions, plans and backend configuration.