> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/the-basics/routing/routing-dsl/adding-data-to-a-route.md).

# Adding Data to a Route

Attach fixed RC and PRC values to matched routes with rc(), prc(), rcAppend(), and prcAppend().

Besides placeholders parsed from the URL itself, you can attach fixed values to the request collection whenever a route matches - useful for flags, defaults, or metadata your handler shouldn't have to guess at.

```javascript
* `rc( name, value, overwrite=true )`        - Add one `RC` value
* `rcAppend( map, overwrite=true )`          - Add multiple `RC` values from a struct
* `prc( name, value, overwrite=true )`       - Add one `PRC` value
* `prcAppend( map, overwrite=true )`         - Add multiple `PRC` values from a struct
```

```javascript
route( "/api/v1/users/:id" )
    .rcAppend( { secured : true } )
    .prcAppend( { name : "hello" } )
    .to( "api-v1:users.show" );
```

`rc` values land in the public request collection (`rc`); `prc` values land in the private collection (`prc`), which is only settable from inside your application - never from user input.


---

# 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://coldbox.ortusbooks.com/the-basics/routing/routing-dsl/adding-data-to-a-route.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.