> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: About HTTP Endpoints

## Article: About HTTP Endpoints

## Article Link: https://dev.wix.com/docs/wix-cli/guides/development/http-endpoints/about-http-endpoints.md

## Article Content:

# About HTTP Endpoints

Wix CLI projects support HTTP endpoints, which you use to build backend APIs for handling HTTP requests and coordinating frontend and backend logic. HTTP endpoints can serve any kind of data.

> **Note:** HTTP endpoints replace [HTTP functions](https://dev.wix.com/docs/wix-cli/legacy/wix-cli-for-apps/supported-extensions/backend-extensions/api/http-functions/add-http-function-extensions-with-the-cli.md) from the legacy Wix CLI for Apps. See the [Migration Guide](https://dev.wix.com/docs/wix-cli/guides/development/http-endpoints/migration-guide.md).

## File-based routing

The location of an endpoint file in your project determines its URL. Place a file at `src/pages/api/<name>.ts`, and it's exposed at `/api/<name>`. For example, `src/pages/api/users.ts` becomes the route `/api/users`.

Endpoints are auto-discovered from the filesystem, so they aren't registered in [`src/extensions.ts`](https://dev.wix.com/docs/wix-cli/guides/extensions/about-the-extensions-ts-file.md) and aren't generated by `npm run generate`.

## HTTP method handlers

Each endpoint file exports one or more HTTP method handlers, such as `GET` or `POST`. A handler receives the standard web `Request` and returns a standard `Response`, so you can return any content type, including JSON, plain text, images, and RSS feeds.

Handlers use the `APIRoute` type from `astro`, the underlying framework that powers HTTP endpoints.

## Server-side runtime

Endpoints run on the server, not in the browser. This means you can:

- Read [environment variables](https://dev.wix.com/docs/wix-cli/guides/development/environment-variables/about-environment-variables.md), including secret server variables that aren't exposed to the client.
- Call external services without exposing credentials in your frontend bundle.

## Calling endpoints from frontend extensions

Frontend extensions, like dashboard pages and site widgets, call endpoints using `httpClient.fetchWithAuth()` from `@wix/essentials`. This attaches the current user's access token to the request as an `Authorization` header, which the endpoint can then use to make [elevated SDK calls](https://dev.wix.com/docs/wix-cli/guides/about-the-wix-cli.md) for operations the user can't perform directly.

For the full pattern, see [Add HTTP Endpoints to Your Project](https://dev.wix.com/docs/wix-cli/guides/development/http-endpoints/add-http-endpoints-to-your-project.md).

## Use cases

Use HTTP endpoints when you need to:

- Integrate with external APIs or services that require HTTP requests.
- Handle complex form submissions or file uploads.
- Serve dynamic content like images, RSS feeds, or personalized data.
- Build REST APIs with multiple HTTP methods.
- Access runtime data or server-side databases.

## See also

- [Add HTTP Endpoints to Your Project](https://dev.wix.com/docs/wix-cli/guides/development/http-endpoints/add-http-endpoints-to-your-project.md)
- [Elevate API Call Permissions](https://dev.wix.com/docs/wix-cli/guides/about-the-wix-cli.md)
- [About Environment Variables](https://dev.wix.com/docs/wix-cli/guides/development/environment-variables/about-environment-variables.md)
- [Migration Guide](https://dev.wix.com/docs/wix-cli/guides/development/http-endpoints/migration-guide.md)