Vibeleaderboard
Index / tool
Visit github.com
Category
Developer Tools
Rank
No. 3065Tools index

Previous survey · No. 2874 ·

Pricing
Open Source
Type
TOOL
Use case
Software Testing & Quality
Latest release
v1.1.2
Date

About

TwinStub simulates APIs deterministically for testing integrations. Stateful YAML scenarios play back as a real HTTP server with sessions, state and HMAC-signed webhook chains, so a sequence like a payment followed by a later chargeback can run in seconds. It ships as a single Go binary with no cloud dependency.

At a glance

TwinStub serves scripted API scenarios over HTTP, with per-session state and signed webhooks. It is worth using when a static mock cannot reproduce a delayed chargeback, a duplicate event or another sequence your integration must handle.

Good fit

Teams testing how their application responds to third-party API events and verifying the resulting local state.

Consider something else when

Use a simple stub for an isolated request with no state change or callbacks.

Start here

Point a test integration at the chargeback scenario with synthetic data. Assert that payment first succeeds and later reverses, then replay an event and confirm the balance changes only once.

Cost and requirements

The MIT-licensed Go tool runs locally. You need a scenario, a webhook receiver and test signing configuration.

Limits to know

A scenario covers only the behavior you encode. Verify critical assumptions with the provider’s own documentation and sandbox.

Tags

api-simulationtestingwebhooksgoyamlmocking

Tech Stack

GoDocker

Comments (0)

No comments yet

Editorially curated, with community endorsements as a secondary signal. Corrections welcome.