Startup
<1sOpen Source Mock API Runtime
Build frontend flows before backend delivery.
FexAPI gives your team a schema-first local API with real data shape, clear watch feedback, and no artifact clutter.
Supported Methods
GET POST PUT PATCH DELETERecord Count Clamp
1-50fexapi-session
1. Bootstrap
$ fexapi init
? What port? (default: 4000) 4000
? Enable CORS? Yes
ok Created fexapi/schema.fexapi
ok Created fexapi.config.js
2. Compile
$ fexapi generate
ok Generate complete (changed)
3. Live Watch
$ fexapi dev --watch --log
info [watch] change detected (schema.fexapi changed)
info [watch] regenerating generated.api.json from schema changes...
ok [watch] server reloaded
Tip: keep this terminal open while editing schema.fexapi to watch live regeneration and instant server reloads.
Route Support
GETPOSTPUTPATCHDELETE
Why teams choose FexAPI
Focused mock infrastructure without fake complexity.
Schema to API
Define endpoints in schema.fexapi and ship a deterministic generated.api.json every cycle.
Live Watch Reload
Use fexapi dev --watch and changes flow through generation then into the running mock server.
Config That Stays Simple
Tune host, port, CORS, and logging from fexapi.config.js without framework lock-in.
Frontend Team Velocity
Unblock screens, loading states, and edge-case flows before backend delivery is complete.
Workflow
Step 1
Init
Scaffold clean config and schema defaults with fexapi init.
Step 2
Generate
Compile schema into fexapi/generated.api.json.
Step 3
Serve or Watch
Run fexapi serve or fexapi dev --watch for fast iteration.
Ready To Ship Faster
Put a stable local API in front of every feature branch.
Keep your frontend release cadence moving while backend contracts evolve. FexAPI keeps schema edits and mock responses synchronized.