Building Typesafe APIs with tRPC & TypeScript

When developing modern APIs, there a few options to choose from. REST is not a standard  but instead style. Trust is constantly broken between the API and client. gRPC and GraphQL provide standards but require complex tooling.

Achieving a consistency in data, as well as a great developer experience seemed impossible until now. tRPC exist to provide type safety end to end, ensuring the contract for the API boundary can be trusted by default. Join me in learning how to build typesafe APIs with tRPC and TypeScript and staying cutting edge with the tooling to do it.

tools learned

  • typescipt
  • trpc
  • create-t3-app


Brian Douglas

Co-founder & CEO @saucedopen

Brian Douglas is the founder and CEO of Open Sauced where he works on increasing the knowledge and insights of open-source communities. In the past he’s lead Developer Advocacy at GitHub by fostering a community of early adopters through content creation showcasing the newest Github features.

Brian has a passion for open-source and loves mentoring new contributors through Open Sauced, the platform that empowers the best developers to work in open-source.

Read more
Find Brian Douglas at:

From the same track


Bridging the Gap Between Developer Tools and No-Code Tools

The content you create should not be tied to the tool you use to create it. Software applications should, whenever possible, push for freeing their data, and make it available for other applications to use as well, without vendor lock-in.

Marie Schneegans

Co-founder @motifland

Michael Fester

Co-founder @motifland


Enhance: SSR for Web Components

Building web apps is often characterized as painful, complex, and time consuming. There are many tools, libraries, frontend frameworks, and opinions about how to fix that problem… but they come with a catch. The frontend ecosystem is fractured into incompatible niches.

Brian Leroux

Co-founder & CTO @Begin


Everyone Can Be a Full-Stack Engineer

Serverless infrastructure makes it easier than ever to eliminate the boundary between frontend and backend. When engineers own the entire stack, they can focus less on rebuilding the same infrastructure and more on what matters: the user experience.

Alex Cole

Software Engineer @convex_dev