Command a small fleet: crew rosters, warp-speed changes with physics-based validation, a breached warp core that refuses orders, and a tribble endpoint that doubles on every GET — a read that mutates, which your test suite should absolutely complain about.
The Starfleet API runs ships and crews under warp-factor limits, and breeds tribbles that multiply exponentially on every read of their population. That growing number is the point: it is the catalog's only endpoint whose response changes on its own between two identical requests, which is exactly what breaks a naive snapshot test.
Base URL: https://funapi.dev/api/starfleet/v1 · 10 endpoints · OpenAPI 3.1 spec and Postman collection available. New here? Read the getting started guide.
the fleet, mostly functional
GET /starfleet/v1/ships — List ships, filter by class or statusGET /starfleet/v1/ships/{id} — Get one shipPOST /starfleet/v1/ships — Commission a new ship (requires Bearer auth)PUT /starfleet/v1/ships/{id}/warp — Set warp factor (physics says no above 9.9) (requires Bearer auth)rosters and redshirts
GET /starfleet/v1/crew — List crew, filter by species or shipGET /starfleet/v1/crew/{id} — Get one crew memberPOST /starfleet/v1/crew — Enlist a crew member (requires Bearer auth)DELETE /starfleet/v1/crew/{id} — Discharge a crew member (admin only) (requires Bearer auth)do NOT keep GETting
GET /starfleet/v1/tribbles — Count tribbles — doubles on EVERY readPOST /starfleet/v1/tribbles/purge — Beam the tribbles away (admin only) (requires Bearer auth)