The Death of REST APIs (Or Not) — 2026 Reality Check
Every year someone declares REST dead. GraphQL was supposed to kill it. Then tRPC. Then Server Components. REST is still here. But the landscape HAS changed. Here's the honest assessment.
What's Changed
Server Components Eliminated Many API Calls
In Next.js with React Server Components:
// Before: Client → API → Database
// app/page.tsx (client component)
const [users, setUsers] = useState([])
useEffect(() => {
fetch('/api/users').then(r => r.json()).then(setUsers)
}, [])
// After: Server Component → Database (no API!)
// app/page.tsx (server component)
const users = await db.select().from(usersTable)
return <UserList users={users} />
No API route needed. Server Components fetch data directly. For many pages, the "API" disappeared.
tRPC Made Internal APIs Invisible
// No REST endpoint defined anywhere
const users = trpc.user.list.useQuery()
// Fully typed, no URL strings, no fetch calls
tRPC replaced internal REST APIs with typed function calls. The API still exists (HTTP under the hood) but developers don't think about it.
GraphQL Found Its Niche
GraphQL didn't kill REST, but it dominates in specific areas:
- Apps with multiple clients (web, mobile, TV)
- Complex data relationships (social networks, e-commerce)
- Companies with separate frontend/backend teams
What Hasn't Changed
Public APIs Are Still REST
Every major API in 2026 is REST:
- Stripe: REST
- GitHub: REST (and GraphQL)
- Twilio: REST
- AWS: REST
- Shopify: REST (and GraphQL)
- OpenAI: REST
Why? REST works with every programming language. No special client needed. HTTP caching works. Everyone understands it.
Microservices Still Use REST
Service-to-service communication:
Auth Service ←REST→ User Service ←REST→ Billing Service
REST (or gRPC) for microservices. Not GraphQL. Not tRPC.
Mobile APIs Are Mostly REST
React Native apps still call REST APIs. Mobile doesn't get Server Components.
The 2026 API Landscape
| Use Case | Best Choice | Why |
|---|---|---|
| Public API | REST | Universal compatibility |
| Internal (full-stack TS) | tRPC | Type safety, zero overhead |
| Internal (multi-client) | GraphQL | Flexible queries |
| Server → Server | REST or gRPC | Simple, performant |
| Server Components | No API (direct DB) | Eliminates the need |
| Mobile → Backend | REST or GraphQL | Broad client support |
| Real-time | WebSockets/SSE | Not HTTP request/response |
What Actually Died
1. REST-for-Everything Mentality
"Every endpoint must be RESTful with proper HTTP methods and status codes." This dogma relaxed. Practical choices replaced purity.
2. Internal REST APIs in Full-Stack Apps
When one TypeScript team owns client and server, tRPC or Server Components replaced internal REST endpoints.
3. Over-Fetching Tolerance
REST's fixed response shapes were fine when bandwidth was the bottleneck. Now clients expect efficient data fetching (GraphQL) or server-side rendering (no fetch at all).
4. API Documentation as an Afterthought
OpenAPI/Swagger became standard. APIs without docs are unacceptable. Type-safe alternatives (tRPC) eliminated the need for separate docs entirely.
What's Actually Growing
Server Actions (Next.js)
'use server'
export async function createUser(formData: FormData) {
const name = formData.get('name')
await db.insert(users).values({ name })
revalidatePath('/users')
}
// In component
<form action={createUser}>
<input name="name" />
<button type="submit">Create</button>
</form>
No API route. No fetch call. Server Actions handle mutations directly.
Edge APIs
APIs running at the edge (Cloudflare Workers, Vercel Edge Functions):
export default {
async fetch(request: Request) {
return Response.json({ hello: 'from the edge' })
}
}
Still REST-shaped, but running in 300+ locations worldwide.
AI-Powered APIs
Every SaaS is adding AI endpoints. Still REST:
POST /api/ai/generate
POST /api/ai/summarize
POST /api/ai/classify
The Prediction
2026-2028:
- REST remains dominant for public APIs
- Server Components + Server Actions reduce internal API surface by 50%
- tRPC becomes standard for full-stack TypeScript internal APIs
- GraphQL holds steady in its niche (multi-client, complex data)
- gRPC grows for microservice communication
REST won't die. It'll become less visible in full-stack apps (hidden behind abstractions) while remaining the standard for public and cross-service communication.
FAQ
Should I still learn REST?
Absolutely. REST is the foundation. Even tRPC and Server Actions use HTTP under the hood. Understanding REST is non-negotiable.
Is GraphQL worth learning in 2026?
If you're building apps with multiple clients (web, mobile, third-party), yes. For single-client full-stack apps, tRPC is simpler.
Should new projects use REST?
For public APIs: yes. For internal full-stack TypeScript: consider tRPC or Server Components. For everything else: REST is a safe default.
Will AI APIs change the landscape?
AI APIs are streaming-heavy (SSE for token-by-token responses). This pushes beyond traditional REST request/response but the base protocol is still HTTP.
Bottom Line
REST isn't dying — it's evolving. In 2026, REST is still the standard for public APIs and cross-service communication. But for internal full-stack TypeScript apps, tRPC and Server Components have largely replaced explicit REST endpoints. Learn REST, use tRPC for internal APIs, and choose GraphQL when you need flexible queries across multiple clients.