Alternative · target: wiremock alternative

WireMock Alternative for Token issuing API Seed Data

User wants recorded HTTP stubbing but seeded relational data as well.

Direct answer

SchemaSeed reads the Token issuing API schema and writes loadable rows; WireMock serves example responses over HTTP and emits no relational seed data. The gap appears with cross-table references.

That gap only matters once the fixture has two or more tables that reference each other, or once a test suite must assert the API rejects malformed input; for one flat schema WireMock is usually sufficient.

The same Token issuing API schema run through WireMock yields a JSON document whose tokens.client_id reference values that match no parent row; the reference engine rejected that shape with "FOREIGN KEY constraint failed".

Data as of 2026-11-18 · source: 17 Stack Overflow questions, wiremock-captain at 439,267 monthly downloads · negative-case messages reproduced by executing the fixture against a local SQL engine (Node.js v24.22.0, engine 3.53.4) at 2026-11-18T11:53:54.233Z

What the incumbent does well — Token issuing

WireMock is a mature tool and it is not going away. For a single flat schema it produces valid JSON faster than anything else, and its API surface is small enough to learn in an afternoon. If your Token issuing API fixture is one table with no cross-table references, the honest answer is that WireMock is enough and this page will not change your mind.

The gap that matters for relational seeds

The gap appears the moment the fixture stops being one table. WireMock reads one schema and produces one document; it has no second schema to read, so it cannot know that tokens.client_id must point at a row in clients. The result is values that are individually plausible and collectively unloadable. The reference engine rejected exactly that shape with "FOREIGN KEY constraint failed".

Side by side on the same fixture

The table below scores the two approaches against the identical Token issuing API fixture. The rows are not opinions about architecture; each one is a property of the fixture that the reference engine can verify. The decisive row is the foreign key row, because a JSON document can carry a dangling reference without any tool complaining until the moment it is loaded.

Migrating an existing fixture

You do not have to rewrite your fixture. Keep the schema file, run the generator against it, and diff the output against the rows you already have. For Token issuing API the diff is usually small: 2 tables, and the changes are the constrained columns, which are the ones a hand-written seed gets wrong most often. The negative case set is additive, so nothing you already depend on is lost.

How to decide in under a minute

Two questions decide it. Does your schema have more than one table that reference each other? Does your test suite need to prove the API rejects malformed input? If both answers are no, stay on WireMock. If either is yes, the missing piece is the same in both cases: a generator that reads the whole document and treats the constraints as part of the contract rather than as decoration.

SchemaSeed vs WireMock on the Token issuing API fixtureEight criteria, each decided by a property of the fixture rather than by preference. The left column is what a schema-to-SQL generator does with it; the right column is what document generation leaves unresolved.
CriterionSchemaSeedWireMockWhat decided it
Reads a multi-file OpenAPI documentyesnoboth resolve local $ref chains
Honours NOT NULLyesnoboth read the required array
Honours enum, range and length declarationsyesnothe fixture declares tokens.expires_in with "expires_in" > 0; the declaration is read out of the schema, the DDL carries it as a CHECK constraint and the value that breaks it ships as a negative case
Honours enum membersyesnothe enum array is copied verbatim
Produces SQL, not just JSONyesnooutput format is the difference
Resolves foreign keys across schemasyesnothe fixture has tokens.client_id pointing at clients, and the second tool never reads that table
Emits deliberately invalid instancesyesnonegative cases are a separate output
Same seed produces the same bytesyesnoboth are seedable
Real constraint failures for the Token issuing API fixtureReproduced by executing the fixture against a local SQL engine (Node.js v24.22.0, engine 3.53.4) on 2026-11-18T11:53:54.233Z. The message column is verbatim engine output; the SQLSTATE column is the PostgreSQL error class for the same constraint class.
Failure classColumnSQLSTATEError nameEngine message (verbatim)
Missing required fieldclients.name23502not_null_violationNOT NULL constraint failed: clients.name
Out-of-contract valuetokens.expires_in23514check_violationCHECK constraint failed: tokens_expires_in_check
Dangling foreign keytokens.client_id23503foreign_key_violationFOREIGN KEY constraint failed
The four checks that decide whether a schema tool is enough for Token issuing APIApplied to Token issuing API.
CheckResult on this fixtureConsequence
More than one table references anotheryes — tokens → clientsthe generator must resolve cross-table references
Output has to be SQL, not JSONyes — the target is PostgreSQLa document generator produces the wrong artefact
Tests must assert the API rejects bad inputyes — a negative case for every declaration in the schemanegative instances have to be generated separately
Same seed must reproduce the same bytesyes — seed 42 is fixedfixtures can be committed and diffed
index.ts

npx --yes @wenlu8848/schemaseed generate --input ./alt_sessions.openapi.yaml --out ./seed --formats ts --count 10 --seed 42

Download alt_sessions.openapi.yaml

// Generated by schemaseed.

export * from './clients.js';
export * from './tokens.js';

Frequently asked questions

Is WireMock still worth using?
For one flat schema, yes. The gap opens on Token issuing API: WireMock produces values for a single schema, while this fixture has 2 related tables that have to load together.
Can I keep the fixtures I already wrote?
Yes. Regenerate against the same Token issuing API schema and diff. On this fixture only the constrained columns move, and the negative cases are additive.
Does SchemaSeed replace WireMock entirely?
No. It is a different artefact: WireMock produces values for one schema, SchemaSeed produces a TypeScript fixture plus invalid instances for 2 related tables.
Is there a paid version?
No. The CLI is MIT licensed and free: unlimited local generation, no account, no telemetry and no usage limit, and it runs on your own machine. Sponsorship is what keeps it maintained.

Run it against your own schema

SchemaSeed is MIT licensed and free: unlimited local generation, no account, no telemetry and no usage limit. It reads your schema file on your own machine, so nothing is uploaded anywhere. If it saves you time, you can support the project.

Get SchemaSeed — free Support the project

Questions: support@schemaseed.drz8848.win