expo-api-routes

Create secure server-side API endpoints for Expo Router applications.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/sc30gsw/jikan-log --skill expo-api-routes-sc30gsw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-api-routes
Source: https://github.com/sc30gsw/jikan-log/tree/main/.agents/skills/expo-api-routes
Command: npx skills add https://github.com/sc30gsw/jikan-log --skill expo-api-routes-sc30gsw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the need to manually configure server‑side endpoints, letting developers safely expose secrets, perform database actions, and proxy third‑party APIs from within an Expo Router project.

Core Features & Use Cases

  • Server‑side Secrets: Keep API keys and credentials hidden from the client.
  • Database Operations: Execute queries directly from API routes without exposing logic.
  • Third‑Party Proxies: Safely call external services like OpenAI or Stripe.
  • EAS Hosting Deployment: Deploy routes as Cloudflare Workers with proper environment variable handling.
  • CORS and Error Handling: Built‑in patterns for cross‑origin requests and robust error responses.

Quick Start

Create a file named hello+api.ts in the app/api directory that returns a JSON greeting.

Frequently Asked Questions about expo-api-routes

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

FAQPage Schema
How do I create secure server-side API routes in an Expo Router application?

You can build secure API routes in Expo Router by creating files like `hello+api.ts` in the `app/api` directory. This approach handles server-side secrets, database operations, and third-party API proxies without exposing logic to the client.

How do I hide API keys and secrets in Expo EAS Hosting?

To hide API keys and secrets in Expo EAS Hosting, use server-side API routes that leverage environment variables. This keeps credentials secure on the server using the Cloudflare Workers runtime, preventing client-side exposure.

Can I use Node.js filesystem access in Expo API routes?

No, you cannot use Node.js filesystem access in Expo API routes. The server-side endpoints operate on the Cloudflare Workers runtime, which leververages standard Web APIs and environment variables instead of Node.js modules.

Does Expo EAS Hosting support proxying external services like Stripe or OpenAI?

Yes, Expo EAS Hosting supports proxying external services like Stripe or OpenAI. You can safely call these third-party APIs from server-side API routes, ensuring sensitive credentials remain hidden on the server within the Cloudflare Workers runtime.

How do I handle CORS and errors in Expo serverless API endpoints?

To handle CORS and errors in Expo serverless API endpoints, use built-in patterns for cross-origin requests and robust error responses. These are directly available when creating API routes for EAS Hosting deployments.

Do I need a separate backend framework to run database operations in Expo?

No, you do not need a separate backend framework to run database operations in Expo. You can execute database queries directly from server-side API routes within Expo Router, securely deployed as Cloudflare Workers.