ReṼoman (Rev-Woman)

---

ReṼoman is an API Orchestration Engine for the JVM. You describe a workflow of interdependent API calls as executable API metadata; ReṼoman executes that graph — resolving data dependencies between calls, handling auth, polling, and type-safe payloads — and returns a structured Rundown of everything that happened. This makes it a building block for Agentic API Orchestration, with API test automation as one powerful application.

ReṼoman comes from the API-first SaaS company, Salesforce.

ℹ️	NO licensed Postman SDKs are used inside this project. This is written ground up natively in JVM.

💡	📖 Full documentation: sfdc.co/revoman-docs The sections below are a quick start. Every feature has a focused page on the site.

Artifact

Maven

<dependency>
    <groupId>com.salesforce.revoman</groupId>
    <artifactId>revoman</artifactId>
    <version>0.9.17</version>
</dependency>

Bazel

"com.salesforce.revoman:revoman"

Gradle Kts

implementation("com.salesforce.revoman:revoman:0.9.17")

Minimum Java Version required = 21

Tech-Talk given at Open Source Conf—2023, 🎴Slide deck

Documentation

Full docs: sfdc.co/revoman-docs

Each topic links to its published page. The source for every page lives in docs/modules/ROOT/pages/<page-name>.adoc (one concept per file) — e.g. the Hooks page below is docs/modules/ROOT/pages/hooks.adoc.

Overview / pitch	Agentic API Orchestration
Why ReṼoman?	Getting started
Configuration	Executable API metadata (v2/v3)
Rundown & toJson	Step procedure & failures
Variables	Type safety (Moshi)
Hooks	Scripts & pm APIs
Polling	Timing metrics
Mutable environment	Execution control
Applications (testing, etc.)	Troubleshooting & FAQ
Contributing

🙌🏼 Consume-Collaborate-Contribute

• The CONTRIBUTING doc has all the information to set up this library locally and get hands-on.

• Any issues or PRs are welcome! ♥️

• Join the Slack Community to discuss issues or PRs.