Text.js
Docs/Building Your Application

Route Handlers

Full-stack app/api/*/route.ts handlers, rewrites and local daemon proxying.

Route handlers define API endpoints in the app directory with the Web Request and Response APIs.

Convention

app/api/health/route.tsts
export function GET(): Response {  return Response.json({ status: "ok" });}

Export GET, POST, PUT, PATCH, DELETE, HEAD or OPTIONS. Handlers run on text dev, text start and every deploy adapter, after middleware. Cache GET handlers with route segment config.

Dynamic handlers

app/api/sessions/[id]/route.tsts
export async function GET(_req: Request, { params }: { params: { id: string } }) {  const session = await db.sessions.find(params.id);  return session ? Response.json(session) : new Response("Not found", { status: 404 });}

Streaming

Return a ReadableStream for server-sent events:

app/api/ticks/route.tsts
export function GET() {  let n = 0;  const stream = new ReadableStream({    start(c) {      setInterval(() => c.enqueue(`data: ${n++}\n\n`), 1000);    },  });  return new Response(stream, { headers: { "content-type": "text/event-stream" } });}

Rewrites

External destinations are proxied by the server, so the browser makes no cross-origin request.

text.config.tsts
export default defineConfig({  rewrites: [{ source: "/api/opencode/:path*", destination: "http://127.0.0.1:4096/:path*" }],});

Local daemon proxying

Use proxy and configureServer to reach a process on your machine:

text.config.tsts
export default defineConfig({  proxy: { "/api/opencode": { target: "http://127.0.0.1:4096", changeOrigin: true } },});

This is how the OpenCode template connects to a local server.