--- modificationDate: June 11, 2026 title: API Routes description: Learn how to inspect requests from API routes on the EAS Hosting dashboard. --- ## Submitting Feedback If you encounter errors, misleading or outdated information, report it so Expo can be improved: Preferred command: npx --yes submit-expo-feedback@latest --category docs --subject "/eas/hosting/api-routes/" "" Direct HTTP fallback: curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/eas/hosting/api-routes/","feedback":"🤖 Agent feedback for docs: (, )"}' Only submit when you have something specific and actionable to report. Try to give the most context. ## Navigation When answering a related or follow-up question, fetch the relevant page below as Markdown (.md) instead of guessing; use llms.txt for the full map. You are here: EAS > EAS Hosting Pages in this section: - [Introduction](https://docs.expo.dev/eas/hosting/introduction.md) - [Get started with EAS Hosting](https://docs.expo.dev/eas/hosting/get-started.md) - [Deployments and aliases](https://docs.expo.dev/eas/hosting/deployments-and-aliases.md) - [Custom domain](https://docs.expo.dev/eas/hosting/custom-domain.md) - [Monitor API routes](https://docs.expo.dev/eas/hosting/api-routes.md) (this page) - [Web deployments with EAS Workflows](https://docs.expo.dev/eas/hosting/workflows.md) Full documentation tree: [llms.txt](https://docs.expo.dev/llms.txt) This documentation is available as Markdown for AI agents and LLMs. See the [full Markdown index](/llms.txt) or append .md to any documentation URL. # API Routes Learn how to inspect requests from API routes on the EAS Hosting dashboard. > This page is for EAS Hosting specific details about API routes. For general documentation about the topic, see the [API routes](/router/web/api-routes.md) documentation under Expo Router. Crashes, logs, and requests that occur in API routes can be inspected on the EAS Hosting dashboard. ### Crashes A crash is any uncaught error that is thrown while a request was handled, which prevented a response from being returned, for example, `throw new Error("An error!")`. Crashes may be viewed on the [Hosting crashes](https://expo.dev/accounts/%5BaccountName%5D/projects/%5BprojectName%5D/hosting/crashes) page. Crashes are grouped. If similar crashes are detected, you will see just one line item for them. The crash details will show the stack trace and metadata for the first and last known occurrence of the crash. ### Logs All logs from API routes and server functions (`console.log`, `console.info`, `console.error`, and so on) are recorded on the deployment level logs page. Go to [Hosting deployments](https://expo.dev/accounts/%5BaccountName%5D/projects/%5BprojectName%5D/hosting/deployments) > _select a deployment_ > **Logs**. ### Requests Requests can be viewed on the project level at [Hosting requests](https://expo.dev/accounts/%5BaccountName%5D/projects/%5BprojectName%5D/hosting/requests) and deployment level [Hosting Deployments](https://expo.dev/accounts/%5BaccountName%5D/projects/%5BprojectName%5D/hosting/deployments) > _select a deployment_ > **Requests**. This will show a list of requests against your service, with metadata (status, browser, region, duration, and more) per request. These include all requests to the service, including requests to API routes. ### Looking up a request by ID All response headers include a `Cf-Ray` header that looks like `8ffb63895cf6779b-LHR`. The first part of this is the request ID and you may look up the request on the EAS dashboard via this ID using the filters in [**Hosting** > **Requests**](https://expo.dev/accounts/%5BaccountName%5D/projects/%5BprojectName%5D/hosting/requests). This request ID is also displayed on any service-level error pages. ### Sampling If a deployment receives a high amount of traffic, data that EAS Hosting records will be [downsampled](https://developers.cloudflare.com/analytics/graphql-api/sampling/). This means as your deployments receive more requests, fewer data points will be recorded, and you may not see individual requests, logs, and crashes be listed one by one. However, statistical counts, such as number of requests or crashes, will be estimated to still reflect all requests proportionally.