How to get the typed search params from server routes?

[tonny008]

I tried below, but not working.

const searchSchema = z.object({
  id: z.number(),
})

export const Route = createFileRoute('/test')({
	validateSearch: searchSchema,
	server: {
		handlers: {
			GET: async ({ request }) => {
				const {id} = Route.useSearch();
				return Response.json({id});
			},
		},
	},
});

search params are not mentioned in the server routes docs.
https://tanstack.com/start/latest/docs/framework/react/guide/server-routes

currently the only option is fallback to URLSearchParams:

const id = +(new URL(request.url).searchParams.get('id') as string);

[agrovr]

Route.useSearch() is a React hook, so it only works while React is rendering under the router. A TanStack Start server-route handler currently receives request, params, and context; the route's validated search object is not injected into that handler.

Reuse the same schema in the handler and parse the request URL there:

import {
  createFileRoute,
  defaultParseSearch,
} from '@tanstack/react-router'
import { z } from 'zod'

const searchSchema = z.object({
  id: z.coerce.number().int(),
})

export const Route = createFileRoute('/test')({
  validateSearch: searchSchema,
  server: {
    handlers: {
      GET: async ({ request }) => {
        const url = new URL(request.url)
        const result = searchSchema.safeParse(
          defaultParseSearch(url.search),
        )

        if (!result.success) {
          return Response.json(
            {
              error: 'Invalid search parameters',
              issues: result.error.issues,
            },
            { status: 400 },
          )
        }

        return Response.json({ id: result.data.id })
      },
    },
  },
})

defaultParseSearch() is the router's normal JSON-first query parser, so this remains close to how TanStack Router parses client-side search values. z.coerce.number() also tolerates a plain string such as ?id=123 if the input was not JSON-decoded to a number first.

For a simple flat query, this is also valid:

const raw = Object.fromEntries(new URL(request.url).searchParams)
const result = searchSchema.safeParse(raw)

However, Object.fromEntries() collapses repeated query keys. defaultParseSearch() is a better match for the router's default serialization behavior. If your router uses a custom parseSearch implementation, call that same parser here instead of defaultParseSearch so client and server semantics stay identical.

So the short answer is: there is currently no server-handler equivalent of Route.useSearch() that automatically returns the typed/validated value; parse request.url and apply the shared schema at this boundary.

Docs: TanStack Start server routes · TanStack Router search params