Add endpoint context API

src/pages/en/core-concepts/endpoints.md

@@ -11,7 +11,7 @@ In statically-generated sites, your custom endpoints are called at build time to
 ## Static File Endpoints
 To create a custom endpoint, add a `.js` or `.ts` file to the `/pages` directory. The `.js` or `.ts` extension will be removed during the build process, so the name of the file should include the extension of the data you want to create. For example, `src/pages/data.json.ts` will build a `/data.json` endpoint.
 
-Endpoints export a `get` function (optionally `async`) that receives an object with two properties (`params` and `request`) as its only argument. It returns an object with a `body`, and Astro will call this at build time and use the contents of the body to generate the file.
+Endpoints export a `get` function (optionally `async`) that receives a [context object](/en/reference/api-reference/#endpoint-context) with properties similar to the `Astro` global. It returns an object with a `body`, and Astro will call this at build time and use the contents of the body to generate the file.
 
 ```js
 // Example: src/pages/builtwith.json.ts
@@ -93,7 +93,7 @@ export const get: APIRoute = ({ params, request }) => {
 ```
 
 ## Server Endpoints (API Routes)
-Everything described in the static file endpoints section can also be used in SSR mode: files can export a `get` function which receives an object with `params` and `request` properties.
+Everything described in the static file endpoints section can also be used in SSR mode: files can export a `get` function which receives a [context object](/en/reference/api-reference/#endpoint-context) with properties similar to the `Astro` global.
 
 But, unlike in `static` mode, when you configure `server` mode, the endpoints will be built when they are requested. This unlocks new features that are unavailable at build time, and allows you to build API routes that listen for requests and securely execute code on the server at runtime.
 
@@ -190,12 +190,12 @@ export const post: APIRoute = async ({ request }) => {
 ```
 
 ### Redirects
-Since `Astro.redirect` is not available in API Routes you can use [`Response.redirect`](https://developer.mozilla.org/en-US/docs/Web/API/Response/redirect) to redirect:
+The endpoint context exports a `redirect()` utility similar to `Astro.redirect`:
 
 ```js title="src/pages/links/[id].js" {14}
 import { getLinkUrl } from '../db';
 
-export async function get({ params }) {
+export async function get({ params, redirect }) {
   const { id } = params;
   const link = await getLinkUrl(id);
 
@@ -206,7 +206,7 @@ export async function get({ params }) {
     });
   }
 
-  return Response.redirect(link, 307);
+  return redirect(link, 307);
 }
 ```
 

src/pages/en/reference/api-reference.md

@@ -357,6 +357,86 @@ And would render HTML like this:
 </ul>
 ```
 
+## Endpoint Context
+
+When creating an endpoint function, it receives the context as the first parameter. It mirrors many of the `Astro` global properties.
+
+### context.request
+
+A standard [Request](https://developer.mozilla.org/en-US/docs/Web/API/Request) object. It can be used to get the `url`, `headers`, `method`, and even body of the request.
+
+```ts
+export function get({ request }) {
+  return {
+    body: `Hello ${request.url}`
+  }
+}
+```
+
+See also: [Astro.request](#astrorequest)
+
+### context.cookies
+
+`context.cookies` contains utilities for reading and manipulating cookies.
+
+See also: [Astro.cookies](#astrocookies)
+
+### context.url
+
+A [URL](https://developer.mozilla.org/en-US/docs/Web/API/URL) object constructed from the current `context.request.url` URL string value.
+
+See also: [Astro.url](#astrourl)
+
+### context.clientAddress
+
+Specifies the [IP address](https://en.wikipedia.org/wiki/IP_address) of the request.
+
+```ts
+export function get({ clientAddress }) {
+  return {
+    body: `Your IP address is: ${clientAddress}`
+  }
+}
+```
+
+See also: [Astro.clientAddress](#astroclientaddress)
+
+
+### context.site
+
+`context.site` returns a `URL` made from `site` in your Astro config. If undefined, this will return a URL generated from `localhost`.
+
+See also: [Astro.site](#astrosite)
+
+### context.generator
+
+`context.generator` is a convenient way to add a [`<meta name="generator">`](https://html.spec.whatwg.org/multipage/semantics.html#meta-generator) tag with your current version of Astro. It follows the format `"Astro v1.x.x"`.
+
+```ts
+export function get({ generator }) {
+  return new Redponse(JSON.stringify({
+    generator,
+    id: '1'
+  }), {
+    status: 200
+  });
+}
+```
+
+See also: [Astro.generator](#astrogenerator)
+
+### context.redirect()
+
+`context.redirect()` returns a [Response](https://developer.mozilla.org/en-US/docs/Web/API/Response) object that allows you to redirect to another page.
+
+```ts
+export function get({ redirect }) {
+  return redirect('/login', 302);
+}
+```
+
+See also: [Astro.redirect](/en/guides/server-side-rendering/#astroredirect)
+
 ## `getStaticPaths()`
 
 If a page uses dynamic params in the filename, that component will need to export a `getStaticPaths()` function.
@@ -379,6 +459,8 @@ export async function getStaticPaths() {
 
 The `getStaticPaths()` function should return an array of objects to determine which paths will be pre-rendered by Astro.
 
+It can also be used in [static file endpoints](/en/core-concepts/endpoints/#static-file-endpoints) and [server endpoints](/en/core-concepts/endpoints/#server-endpoints-api-routes) in `server` mode.
+
 :::caution
 The `getStaticPaths()` function executes in its own isolated scope once, before any page loads. Therefore you can't reference anything from its parent scope, other than file imports. The compiler will warn if you break this requirement.
 :::