start-core/server-routes

Server API routes in TanStack Start are defined by using the server property on createFileRoute within the src/routes directory. This allows you to expose GET, POST, PUT, and DELETE HTTP handlers directly next to your app's UI components.

Yes, per-route middleware is supported on server routes in TanStack Start. You can apply middleware to specific handlers to intercept requests, parse payloads, and manage context before the primary GET or POST logic executes.

The best way to structure backend API endpoints is co-locating them with UI routes using createFileRoute. This cohesive routing model parameterizes requests and handles responses seamlessly, enabling robust SSR and data fetching patterns.

TanStack Start supports raw HTTP request handling for methods like PUT and DELETE through the server property on createFileRoute. It provides request parsing and response helpers to manage these raw interactions effectively.

Organizing server-side API endpoints next to app routes creates a cohesive routing model that simplifies parameter and context handling. This co-location enables unified data fetching and SSR patterns without splitting backend logic into a separate folder.