Standalone applications construct RevoClient. Construction is synchronous and performs no network request; the first platform-backed call validates the API key through /api/v1/me, resolves its instance, and discovers the instance’s Sandbox runtime.
Create a client
There is no separate init() or connect method.
Configuration
Explicit constructor options take precedence over environment variables:
Supported aliases, in precedence order within each group:
- URL:
REVO_URL, REVO_BASE_URL, REVOENGINE_URL, REVOENGINE_BASE_URL
- API key:
REVO_TOKEN, REVO_API_KEY, REVOENGINE_TOKEN, REVOENGINE_API_KEY
The default API origin is https://api.revoengine.com. The key identifies its instance, so RevoClient has no instance option.
The standalone SDK is for trusted server-side Node.js processes. Never bundle an API key into browser code. The SDK does not read or write CLI credential files.
Identity methods
The three identity methods are asynchronous in standalone mode because they depend on lazy profile discovery:
Execution-only context methods such as api.input(), api.getContext(), api.getExecutionId(), and runtime logging require a hosted execution and throw RevoRuntimeContextUnavailableError when called standalone.
Execute low-code with active libraries
TypeScript is the default; set language: 'javascript' when required. One execute() call creates one bounded execution. Source and library functions remain inside RevoEngine; only the request and serializable result cross the transport.
Discovery failures
401 indicates an invalid key, while 403 means the authenticated identity lacks runtime permission. A profile that does not contain the bound instance or Sandbox endpoint is reported as a protocol error rather than guessed from the API hostname.