tRPC

tRPC is an end-to-end typed RPC layer, very widespread on the TypeScript side. Restorm exposes it as a request type in its own right, which saves you assembling the envelope the server expects by hand.

Right-click in the tree ▸ Add ▸ tRPC request.

Configuration

Field	Role
URL	The tRPC router’s base URL; the procedure path is appended to it
Procedure	The procedure’s dotted path, for example user.get
Type	query or mutation
Input	The procedure’s input, in JSON — {{variables}} work in it
Headers	Additional HTTP headers

What Restorm does for you

• a query goes out as a GET with the input serialised into the ?input= parameter;
• a mutation goes out as a POST with the body envelope tRPC v10 expects.

You therefore only write the procedure and its input.

Importing a tRPC schema

If your server exposes its schema (typically at <base>/.trpc/_schema), File ▸ Import creates one request per procedure, with its type and a sample input. See Importing tRPC.

Limitations

tRPC has no standardised introspection mechanism. The import only understands the documented shape of the schema, with no fallback heuristic, and does not attempt to reproduce full type fidelity. Procedures whose type is not recognised are skipped.

Code snippets

Five targets: cURL, JavaScript (Fetch), TypeScript (@trpc/client), Python (requests) and Go.