Alternative · target: postman mock data alternative

Postman Alternative for Subscription billing API Seed Data

User wants mock data without keeping the Postman desktop app and collection format in the loop.

Direct answer

SchemaSeed reads the Subscription billing API schema and writes loadable rows; Postman keeps requests and responses in one collection and emits no 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 Postman is usually sufficient.

The same Subscription billing API schema run through Postman yields a JSON document whose subscriptions.plan_code 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: 1 Stack Overflow questions, 2 Hacker News stories, @scalar/postman-to-openapi at 1,641,813 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 — Subscription billing

Postman 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 Subscription billing API fixture is one table with no cross-table references, the honest answer is that Postman 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. Postman reads one schema and produces one document; it has no second schema to read, so it cannot know that subscriptions.plan_code must point at a row in plans. 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 Subscription billing 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 Subscription billing API the diff is usually small: 3 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 Postman. 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 Postman on the Subscription billing 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.
CriterionSchemaSeedPostmanWhat decided it
Reads a multi-file OpenAPI documentyespartialboth resolve local $ref chains
Honours NOT NULLyespartialboth read the required array
Honours enum, range and length declarationsyespartialthe fixture declares plans.price_cents with "price_cents" >= 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 membersyespartialthe enum array is copied verbatim
Produces SQL, not just JSONyesnooutput format is the difference
Resolves foreign keys across schemasyesnothe fixture has subscriptions.plan_code pointing at plans, and the second tool never reads that table
Emits deliberately invalid instancesyesnonegative cases are a separate output
Same seed produces the same bytesyespartialboth are seedable
Real constraint failures for the Subscription billing 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 fieldplans.price_cents23502not_null_violationNOT NULL constraint failed: plans.price_cents
Out-of-contract valueplans.price_cents23514check_violationCHECK constraint failed: plans_price_cents_check
Dangling foreign keysubscriptions.plan_code23503foreign_key_violationFOREIGN KEY constraint failed
The four checks that decide whether a schema tool is enough for Subscription billing APIApplied to Subscription billing API.
CheckResult on this fixtureConsequence
More than one table references anotheryes — subscriptions → plansthe 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
alt_billing.openapi.yaml

npx --yes @wenlu8848/schemaseed validate --input ./alt_billing.openapi.yaml

Download alt_billing.openapi.yaml

openapi: "3.0.3"
info:
  title: "Subscription billing API"
  version: "1.0.0"
  description: "The plan code is a natural primary key, so the generator has to reuse the same code across subscriptions and invoices. A subscription in the past_due state still has a renews_at timestamp in the future, which surprises people. The invoice amount is constrained to be non-negative and the paid flag is an integer. This three-table shape is the smallest one where a single-schema generator starts producing dangling references."
paths: {}
x-domain-id: "alt_billing"
x-dialect: "postgres"
components:
  schemas:
    plans:
      type: "object"
      x-primary-key: "code"
      required: ["code", "price_cents", "interval"]
      properties:
        code:
          type: "string"
        price_cents:
          type: "integer"
          minimum: 0
        interval:
          type: "string"
          enum: ["month", "year"]
    subscriptions:
      type: "object"
      x-primary-key: "id"
      required: ["id", "plan_code", "status", "renews_at"]
      properties:
        id:
          type: "string"
          format: "uuid"
        plan_code:
          $ref: "#/components/schemas/plans"
        status:
          type: "string"
          enum: ["trialing", "active", "past_due", "canceled"]
        renews_at:
          type: "string"
          format: "date-time"
    invoices:
      type: "object"
      x-primary-key: "id"
      required: ["id", "subscription_id", "amount_cents", "paid"]
      properties:
        id:
          type: "string"
          format: "uuid"
        subscription_id:
          $ref: "#/components/schemas/subscriptions"
        amount_cents:
          type: "integer"
          minimum: 0
        paid:
          type: "integer"
          minimum: 0
          maximum: 1

Frequently asked questions

Is Postman still worth using?
For one flat schema, yes. The gap opens on Subscription billing API: Postman produces values for a single schema, while this fixture has 3 related tables that have to load together.
Can I keep the fixtures I already wrote?
Yes. Regenerate against the same Subscription billing API schema and diff. On this fixture only the constrained columns move, and the negative cases are additive.
Does SchemaSeed replace Postman entirely?
No. It is a different artefact: Postman produces values for one schema, SchemaSeed produces JSON fixture files plus invalid instances for 3 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