Astro

Mount the Files gateway in an Astro endpoint. createRouteHandler returns { GET, POST, PUT } over the Web Request Astro hands each route - runs on Node and edge adapters.

files-sdk/astro mounts a createFilesRouter in an Astro endpoint. Astro hands each route a Web Request on context.request and wants named per-method exports, so — like files-sdk/next — createRouteHandler returns { GET, POST, PUT }: GET serves downloads, POST the JSON verbs, and PUT the upload byte path. The handlers are Web-native, so the route runs on Node and edge adapters alike.

src/pages/api/files.ts

import { createFiles } from "files-sdk";
import { s3 } from "files-sdk/s3";
import { createFilesRouter } from "files-sdk/api";
import { createRouteHandler } from "files-sdk/astro";

const router = createFilesRouter({
  files: createFiles({ adapter: s3({ bucket: "uploads" }) }),
  allowedOrigins: ["https://app.example.com"],
  authorize: async ({ req }) => {
    /* throw to deny, or return a per-user constraint — see /ui/server/authorization */
  },
});

export const prerender = false;
export const { GET, POST, PUT } = createRouteHandler(router);

The endpoint must run per-request, not at build time. Set export const prerender = false on the route (or output: "server" in astro.config.mjs) and install an SSR adapter (@astrojs/node, @astrojs/vercel, …) — otherwise Astro tries to prerender it and the upload/download paths never reach a server.

See the gateway options for the full configuration and the authorize model for locking it down.