Developer Platform
Build a custom integration, define triggers and actions with JSON schema, configure auth and rate limits, and publish to the Revo marketplace.
The developer platform lets you build your own integration and ship it to every Revo customer through the marketplace, with a Developer Console, JSON schema definitions, configurable authentication, rate limits, and an SDK.
How it works
Register your app. Open the Developer Console and create an application entry with name, icon, category, support contact, and marketplace description. The console generates client credentials (a public ID and a secret key) that you can rotate at any time without affecting the app identity.
Define triggers and actions. Declare them with JSON schema, specifying inputs, outputs, required and optional fields, types, and descriptions. The platform validates every workflow against your schema and renders the descriptions as inline help in the editor.
Configure auth and rate limits. Set the authentication method, scopes, and redirect path that end users complete on install. Define rate limits per second, minute, and day, plus optional per user limits. The platform enforces both on every workflow.
Publish to the marketplace. Submit for review against documentation, schema correctness, and quality standards. Once approved, every Revo customer can find and install your integration in one click.
Key capabilities
- Developer Console workspace with client credentials, rotation, and install, usage, and error monitoring.
- Custom triggers and actions defined declaratively with JSON schema as the contract.
- Secure authentication configuration; the platform handles credential storage, refresh, and revocation.
- Configurable rate limits per second, minute, and day, with optional per user limits.
- App marketplace publishing with install, active user, and feedback tracking.
- SDK in TypeScript, JavaScript, Python, Go, Ruby, PHP, and Java, plus a webhook guide.
Tips
The schema, rate limits, auth configuration, and metadata are the source of truth. Editor documentation reads directly from them, so there is no separate docs site to keep in sync.