Skip to main content
RevoEngine exposes several developer surfaces because managing an enterprise application estate, invoking a public endpoint, executing code, and promoting a release are different operations. All surfaces converge on the same instance-scoped BaaS control plane: versioned definitions, IAM/ACL, operational evidence, and lifecycle actions—not a collection of unrelated APIs.

​
Choose an interface

​
Base URLs

The public Platform API uses an environment-specific API origin. Production examples use:
Endpoint runtime and Sandbox origins belong to the authenticated instance. Read them from the instance profile or the platform UI instead of constructing hostnames. The standalone SDK performs this discovery from GET /api/v1/me automatically.

​
A typical delivery flow

1

Build

Create a low-code, library, or Custom Node.js component. Use generated editor types so local code matches the active platform contract.
2

Validate

Debug transient source in Sandbox, inspect structured logs, and verify success and failure inputs.
3

Expose or automate

Attach the component to an Endpoint, schedule, event, or another supported trigger. Keep definitions inactive until validation is complete when the workflow requires controlled rollout.
4

Operate

Activate a verified version, observe execution identifiers and history, and promote changes between environments with an explicit plan.

​
Contract sources

  • The API reference is generated from the current Platform API OpenAPI document.
  • Sandbox request DTOs and the published SDK contract define executable payloads.
  • CLI-generated types describe the effective low-code and library surface for the authenticated instance.
Never place API keys, secret values, signed upload URLs, or raw authorization headers in source control, browser code, logs, screenshots, or Assistant prompts.
Last modified on September 5, 2026