# Quickstart

> Learn how to quickly get started and setup tRPC

## Installation

tRPC is split between several packages, so you can install only what you need. Make sure to install the packages you want in the proper sections of your codebase. For this quickstart guide we'll keep it simple and use the vanilla client only. For framework guides, check out [usage with React](https://trpc.io/docs/client/tanstack-react-query/setup.md) and [usage with Next.js](https://trpc.io/docs/client/nextjs.md).

> [!NOTE] Requirements
> - tRPC requires TypeScript >=5.7.2
> - We strongly recommend using `"strict": true` in your `tsconfig.json` as we don't officially support non-strict mode.


Start off by installing the `@trpc/server` and `@trpc/client` packages:

```package-install
@trpc/server @trpc/client
```

## Your first tRPC API

Let's walk through the steps of building a typesafe API with tRPC. To start, this API will contain three endpoints with these TypeScript signatures:

```ts
type User = { id: string; name: string; };

userList: () => User[];
userById: (id: string) => User;
userCreate: (data: { name: string }) => User;
```

Here's the file structure we'll be building. We recommend separating tRPC initialization, router definition, and server setup into distinct files to prevent cyclic dependencies:

```
.
├── server/
│   ├── trpc.ts        # tRPC instantiation & setup
│   ├── appRouter.ts   # Your API logic and type export
│   └── index.ts       # HTTP server
└── client/
    └── index.ts       # tRPC client
```

### 1. Create a router instance

First, let's initialize the tRPC backend. It's good convention to do this in a separate file and export reusable helper functions instead of the entire tRPC object. 

```ts title="server/trpc.ts"
import { initTRPC } from '@trpc/server';

/**
 * Initialization of tRPC backend
 * Should be done only once per backend!
 */
const t = initTRPC.create();

/**
 * Export reusable router and procedure helpers
 * that can be used throughout the router
 */
export const router = t.router;
export const publicProcedure = t.procedure;
```

Next, we'll initialize our main router instance, commonly referred to as `appRouter`, to which we'll later add procedures. Lastly, we need to export the type of the router which we'll later use on the client side.

```ts title="server/appRouter.ts"
import { router } from './trpc';

export const appRouter = router({
  // ...
});

export type AppRouter = typeof appRouter;
```

### 2. Add a query procedure

Use `publicProcedure.query()` to add a query procedure to the router.

The following creates a query procedure called `userList` that returns a list of users:

```ts title="server/appRouter.ts"
import { publicProcedure, router } from './trpc';

export const appRouter = router({
  userList: publicProcedure
    .query(async () => {
      const users: User[] = [{ id: '1', name: 'Katt' }];

      return users;
    }),
});

export type AppRouter = typeof appRouter;
```

### 3. Using input parser to validate procedure inputs

To implement the `userById` procedure, we need to accept input from the client. tRPC lets you define [input parsers](https://trpc.io/docs/server/validators.md) to validate and parse the input. You can define your own input parser or use a validation library of your choice, like [zod](https://zod.dev), [yup](https://github.com/jquense/yup), or [superstruct](https://docs.superstructjs.org/).

You define your input parser on `publicProcedure.input()`, which can then be accessed on the resolver function as shown below:

<div class="code-tabs" data-tabs="tabs-vanilla-zod-yup-valibot">
<div data-tab="Vanilla">

The input parser should be a function that validates and casts the input of this procedure. It should return a strongly typed value when the input is valid or throw an error if the input is invalid.

<br />

> [!NOTE] Info
> Throughout the remainder of this documentation, we will use `zod` as our validation library.


```ts title="server/appRouter.ts"
import { publicProcedure, router } from './trpc';

export const appRouter = router({
  // ...
  userById: publicProcedure
    // The input is unknown at this time. A client could have sent
    // us anything so we won't assume a certain data type.
    .input((val: unknown) => {
      // If the value is of type string, return it.
      // It will now be inferred as a string.
      if (typeof val === 'string') return val;

      // Uh oh, looks like that input wasn't a string.
      // We will throw an error instead of running the procedure.
      throw new Error(`Invalid input: ${typeof val}`);
    })
    .query(async (opts) => {
      const { input } = opts;
      // const input: string
      const user: User = { id: input, name: 'Katt' };

      return user;
    }),
});

export type AppRouter = typeof appRouter;
```

</div>
<div data-tab="Zod" data-active>

The input parser can be any <code>ZodType</code>, e.g. <code>z.string()</code> or <code>z.object({})</code>.

<br />

```ts title="server/appRouter.ts"
import { publicProcedure, router } from './trpc';
import { z } from 'zod';

export const appRouter = router({
  // ...
  userById: publicProcedure
    .input(z.string())
    .query(async (opts) => {
      const { input } = opts;
      // const input: string
      const user: User = { id: input, name: 'Katt' };

      return user;
    }),
});

export type AppRouter = typeof appRouter;
```

</div>
<div data-tab="Yup">

The input parser can be any <code>YupSchema</code>, e.g. <code>yup.string()</code> or <code>yup.object({})</code>.

<br />

> [!NOTE] Info
> Throughout the remainder of this documentation, we will use `zod` as our validation library.


```ts title="server/appRouter.ts"
import { publicProcedure, router } from './trpc';
import * as yup from 'yup';

export const appRouter = router({
  // ...
  userById: publicProcedure
    .input(yup.string().required())
    .query(async (opts) => {
      const { input } = opts;
      // const input: string
      const user: User = { id: input, name: 'Katt' };
 
      return user;
    }),
});

export type AppRouter = typeof appRouter;
```

</div>
<div data-tab="Valibot">

The input parser can be any Valibot schema, e.g. <code>v.string()</code> or <code>v.object({})</code>.

<br />

> [!NOTE] Info
> Throughout the remainder of this documentation, we will use `zod` as our validation library.


```ts title="server/appRouter.ts"
import { publicProcedure, router } from './trpc';
import * as v from 'valibot';

export const appRouter = router({
  // ...
  userById: publicProcedure
    .input(v.string())
    .query(async (opts) => {
      const { input } = opts;
      // const input: string
      const user: User = { id: input, name: 'Katt' };

      return user;
    }),
});

export type AppRouter = typeof appRouter;
```

</div>
</div>

### 4. Adding a mutation procedure

Similar to GraphQL, tRPC makes a distinction between Query and Mutation procedures.

The distinction between a Query and a Mutation is primarily semantic. Queries use HTTP GET and are intended for read operations, while Mutations use HTTP POST and are intended for operations that cause side effects.

Let's add a `userCreate` mutation by adding it as a new property on our router object:

```ts title="server/appRouter.ts"
import { publicProcedure, router } from './trpc';

export const appRouter = router({
  // ...
  userCreate: publicProcedure
    .input(z.object({ name: z.string() }))
    .mutation(async (opts) => {
      const { input } = opts;
      // const input: {
      //     name: string;
      // }
      // Create the user in your DB
      const user: User = { id: '1', ...input };

      return user;
    }),
});

export type AppRouter = typeof appRouter;
```

## Serving the API

Now that we have defined our router, we can serve it. tRPC has first-class [adapters](https://trpc.io/docs/server/adapters.md) for many popular web servers. To keep it simple, we'll use the [`standalone`](https://trpc.io/docs/server/adapters/standalone.md) Node.js adapter here.

```ts title="server/index.ts"
import { createHTTPServer } from '@trpc/server/adapters/standalone';
import { appRouter } from './appRouter';

const server = createHTTPServer({
  router: appRouter,
});

server.listen(3000);
```

<details>
<summary>See the full backend code</summary>

```ts title="server/trpc.ts"
import { initTRPC } from '@trpc/server';

const t = initTRPC.create();

export const router = t.router;
export const publicProcedure = t.procedure;
```

<br/>

```ts title="server/appRouter.ts"
import { z } from "zod";
import { publicProcedure, router } from "./trpc";

type User = { id: string; name: string };

export const appRouter = router({
  userList: publicProcedure
    .query(async () => {
      const users: User[] = [{ id: '1', name: 'Katt' }];
      return users;
    }),
  userById: publicProcedure
    .input(z.string())
    .query(async (opts) => {
      const { input } = opts;
      const user: User = { id: input, name: 'Katt' };
      return user;
    }),
  userCreate: publicProcedure
    .input(z.object({ name: z.string() }))
    .mutation(async (opts) => {
      const { input } = opts;
      const user: User = { id: '1', ...input };
      return user;
    }),
});

export type AppRouter = typeof appRouter;
```

<br/>

```ts title="server/index.ts"
import { createHTTPServer } from "@trpc/server/adapters/standalone";
import { appRouter } from "./appRouter";

const server = createHTTPServer({
  router: appRouter,
});

server.listen(3000);
```

</details>

## Using your new backend on the client

Let's now move to the client-side code and embrace the power of end-to-end typesafety. When we import the `AppRouter` type for the client to use, we have achieved full typesafety for our system without leaking any implementation details to the client.

### 1. Setup the tRPC Client

```ts title="client/index.ts"
import { createTRPCClient, httpBatchLink } from '@trpc/client';
import type { AppRouter } from '../server/appRouter';
//     👆 **type-only** imports are stripped at build time

// Pass AppRouter as a type parameter. 👇 This lets `trpc` know
// what procedures are available on the server and their input/output types.
const trpc = createTRPCClient<AppRouter>({
  links: [
    httpBatchLink({
      url: 'http://localhost:3000',
    }),
  ],
});
```

Links in tRPC are similar to links in GraphQL, they let us control the data flow to the server. In the example above, we use the [httpBatchLink](https://trpc.io/docs/client/links/httpBatchLink.md), which automatically batches up multiple calls into a single HTTP request. For more in-depth usage of links, see the [links documentation](https://trpc.io/docs/client/links.md).

### 2. Type Inference & Autocomplete

You now have access to your API procedures on the `trpc` object. Try it out!

```ts title="client/index.ts"
// Inferred types
const user = await trpc.userById.query('1');
// const user: User

const createdUser = await trpc.userCreate.mutate({ name: 'Katt' });
// const createdUser: User
```

You can also use your autocomplete to explore the API on your client

```ts title="client/index.ts"
trpc.u;
```

## Next steps

| What's next? | Description |
|---|---|
| [Example Apps](https://trpc.io/docs/example-apps.md) | Explore tRPC in your chosen framework |
| [TanStack React Query](https://trpc.io/docs/client/tanstack-react-query/setup.md) | Recommended React integration via `@trpc/tanstack-react-query` |
| [Next.js](https://trpc.io/docs/client/nextjs.md) | Usage with Next.js |
| [Server Adapters](https://trpc.io/docs/server/adapters.md) | Express, Fastify, and more |
| [Transformers](https://trpc.io/docs/server/data-transformers.md#using-superjson) | Use superjson to retain complex types like `Date` |