API Simulator Editions

There are two API Simulator editions:

The Standalone API Simulator runs as a lightweight process started and stopped independently of the clients using the API Simulations it provides. There can be multiple Standalone API Simulator instances running on the same host (server, VM, workstation, laptop, Docker container in a Kubernetes pod…​).

Modeling API Simulations for the Standalone API Simulator is via an intuitive and simple to use YAML DSL (Domain-Specific Language), or by using the online browser-based API Simulation Modeler_(beta).

The applications that use Standalone API Simulator can be written in any programming language. They only have to "speak" HTTP.

Standalone API Simulator excels in simulating APIs that do not exist yet, or APIs your applications depend on and require during development and testing. A great Use Case is simulating API dependencies in load testing to help create a controlled, self-sufficient environment for repeatable tests, including during performance tuning of applications.

Learn more…​

The Embedded API Simulator runs in the same JVM as the clients that call over the network the API Simulations it provides. The clients control its lifecycle – they start and stop an Embedded API Simulator as needed. There can be multiple Embedded API Simulator instances running in the same JVM.

Modeling API Simulations for Embedded API Simulator is through an intuitive and simple to use Java DSL (Domain-Specific Language).

Embedded API Simulator is a great tool for Java applications to simulate API calls over the network in tests or the calling of APIs that do not exist yet.

Learn more…​

We would love to hear your feedback! Shoot us a quick email to [feedback at APISimulator.com] to let us know what you think.

Happy API Simulating!