Dashier · crud api generator

Generate CRUD APIs from a defined data source

Dashier creates per-source REST routes for list, create, read, update, and delete operations from the fields you define, with request validation and configurable access policies.

See how it works Pricing

The problem this approach addresses

Writing CRUD routes one collection at a time means repeatedly handling input validation, pagination, authorization, response shapes, and admin forms. If those pieces are implemented separately, a field change can update one part and leave another stale.

How Dashier works

1Define a source slug and typed fields.
2Use the collection route for list/create and append a record ID for read/update/delete.
3Choose API exposure and Public, Authenticated, or Role access per method.
4Send an API key with the appropriate read/write/admin scope, or deliberately use a public route.

A concrete example

GET /api/v1/members?page=1&per_page=20
POST /api/v1/members
GET /api/v1/members/{id}
PUT /api/v1/members/{id}
DELETE /api/v1/members/{id}

Illustrative model and route; configure it for your own project and access requirements.

Common use cases

Read paginated operational lists
Submit validated records from a backend
Update a record from a server workflow
Connect multiple frontend frameworks through HTTP

Why consider Dashier?

Use generated CRUD routes when a source maps cleanly to records and standard data-management operations. Test negative authorization and validation cases as part of integration.

Know the boundaries

Generated CRUD is not a general workflow engine. Business invariants that span multiple records or services must still be enforced in the application or another dedicated service.

Make the administrative layer part of the data design

Start with the model, review the permission boundary, and integrate the API where it belongs in your application.

Integration guide All features