> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/configuration/paths.md).

# Paths

Configure path-based API routing in the Serverless API Gateway. Define methods, endpoints, auth, mappings, and server integrations per route.

The paths section is an array of objects where each object represents an API endpoint configuration.

* `method`: HTTP method (GET, POST, etc.).
* `path`: URL path of the API endpoint.
* `integration`: Server integration settings.
  * `http` and `http_proxy` are both accepted for HTTP proxy integrations.
* `auth`: Indicates if the path requires authentication.
* `mapping`: Defines mappings for headers and query parameters.
* `variables`: Sets variables used in the endpoint.
* `response`: Specifies the response structure for the endpoint.

### See Also

* [Add and Remove Prefix](/configuration/add-and-remove-prefix.md) -- manipulate URL prefixes when proxying requests to upstream servers.
* [Servers](/configuration/servers.md) -- define the upstream servers referenced in path `integration` settings.
* [Variable Mapping](/configuration/variable-mapping.md) -- transform request headers and query parameters using dynamic templates.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.serverlessapigateway.com/configuration/paths.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.