Simultaneous use of RPC and OpenAPI handlers

[rhinodavid]

First off, I am SO excited to see this project. I had been trying to work around a bunch of issues with tRPC and this solves every single one and more.

I'm looking for an example of a server that uses both the RPCHandler and the OpenAPIHandler. I see in the creating a client docs that it looks like the rpc handler is mounted on /rpc, and I'm assuming in this case the OpenAPI hander is mounted at /. I'm sure there are hacks to manipulate the request, but I'm wondering if there's a clean way to set up the server.

Anyway awesome work. This is going to blow up.

[dosubot[bot]]

There isn't a single-file example in the repo that shows both RPCHandler and OpenAPIHandler in one server, but the playgrounds for frameworks like Next.js and SvelteKit show the idiomatic pattern: mount RPCHandler at /rpc and OpenAPIHandler at /api. Each handler is set up in its own route file, and both can coexist cleanly this way—no hacks needed. You can see this pattern in the Next.js playground for RPCHandler and OpenAPIHandler.

If you want OpenAPIHandler at / instead of /api, you can just change the prefix in the handler config and route file. The project doesn't recommend against this, but /api is the default in the playgrounds. This setup is clean, maintainable, and lets you serve both RPC and OpenAPI endpoints side by side.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[rhinodavid]

Thanks @dosu -- I also just found one here: https://github.com/unnoq/orpc/blob/main/playgrounds/contract-first/src/main.ts#L70

[dosubot[bot]]

Great find! That example in contract-first/main.ts does exactly what you’re after—it sets up both OpenAPIHandler (at /api) and RPCHandler (at /rpc) in the same server, each with its own clean prefix and no hacks or request manipulation. The server tries OpenAPI first, then RPC, and falls back to 404 if neither matches. If you want OpenAPI at the root instead of /api, you can just change the prefix in the handler config—otherwise, this pattern is fully supported and idiomatic for orpc. Here’s the relevant code for reference: contract-first/src/main.ts.

Let me know if you want to dig into any part of the setup or have other questions!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}