expo-api-routes

Create secure server-side API routes for Expo Router and EAS Hosting.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/nawab69/pouch-monorepo --skill expo-api-routes-nawab69
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-api-routes
Source: https://github.com/nawab69/pouch-monorepo/tree/main/apps/mobile/.agents/skills/expo-api-routes
Command: npx skills add https://github.com/nawab69/pouch-monorepo --skill expo-api-routes-nawab69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide secure server-side endpoints for Expo Router and EAS Hosting to keep API keys and other secrets off the client, perform protected database operations, proxy third-party APIs, validate input, receive webhooks, and offload heavy computation from mobile devices.

Core Features & Use Cases

  • Server-side secrets — Safely use environment variables for API keys and credentials without exposing them to the client.
  • HTTP method handlers & dynamic routes — Implement GET, POST, PUT, DELETE and parameterized routes for RESTful endpoints.
  • Proxying & webhooks — Hide third-party API keys when calling external services and receive webhook callbacks securely.
  • Runtime-aware deployment — Guidance for deploying to EAS Hosting on Cloudflare Workers with considerations for limited Node APIs, timeouts, and available Web APIs.
  • Developer workflows — Local testing, CORS configuration for web clients, error handling patterns, and recommended database options for edge environments.

Quick Start

Start the development server and call the /api/hello endpoint to verify API route behavior and environment variable handling.

Frequently Asked Questions about expo-api-routes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I hide API keys in Expo Router using server-side API routes?

To hide API keys in Expo Router, use server-side API routes to securely access environment variables. This keeps credentials off the mobile client while enabling protected database operations and third-party API proxying.

Can I use Expo API routes with EAS Hosting on Cloudflare Workers?

Yes, you can deploy Expo API routes to EAS Hosting on Cloudflare Workers. The implementation provides runtime-aware guidance for handling limited Node APIs, execution timeouts, and available Web APIs within the edge environment.

How do I handle CORS and HTTP methods in Expo API routes?

Handle CORS and HTTP methods in Expo API routes by configuring standard GET, POST, PUT, and DELETE handlers with built-in CORS support. This enables RESTful endpoints and dynamic parameterized routes for web clients.

How do I receive webhooks and proxy third-party APIs in an Expo backend?

Receive webhooks and proxy third-party APIs in an Expo backend by configuring server-side routes to intercept external callbacks and forward requests. This securely hides third-party API keys during server-side validation and proxying.

What are the limitations of using Cloudflare Workers runtime for Expo API routes?

Limitations of using Cloudflare Workers for Expo API routes include restricted Node APIs, execution timeouts, and dependency on available Web APIs. The implementation provides runtime-aware guidance to navigate these edge environment constraints.