Do I need REST or GraphQL for a dataset API?

Usually REST is the safer default for a dataset API.

Pick REST if:

• You want simple, predictable endpoints
• Your data model is fairly stable
• Most clients need full records or standard CRUD
• You care about easy caching, monitoring, and debugging
• You want faster implementation with fewer moving parts

Pick GraphQL if:

• Clients need different shapes of the same data
• You have many frontend consumers with varying needs
• You want to avoid over-fetching / under-fetching
• Your dataset is highly relational and users often query across entities
• You’re okay with added complexity in schema design, resolvers, and performance tuning

For a dataset API specifically:

If the API is mainly for:

• listing rows
• filtering/searching
• downloading records
• retrieving one item by ID

then REST is usually enough and often better.

If users need:

• custom projections
• nested related data
• interactive exploration
• one endpoint that can answer many query patterns

then GraphQL may be worth it.

Practical recommendation

For most dataset APIs:

1. Start with REST
2. Add query parameters for filtering, sorting, pagination, field selection
3. Consider GraphQL only if clients outgrow REST’s flexibility

If you want, I can also give you a decision checklist or a sample REST design for a dataset API.