> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/api-flow/api-publishing/develop/multiple-responses-using-conditional-route.md).

# Multiple Responses using Conditional Route

### Video

{% embed url="<https://www.youtube.com/watch?index=4&list=PLmyM3TZtVUyJSFX7EYo811ncfDbNQVyVM&v=gd4o7FMxLJ8>" %}

An API flow can be conditioned to return a different response as per the designed flow. The server could return a successful response for a valid request or return a missing parameter response for an incomplete request.

To define an API with multiple responses, we have mapped two *Response* objects through a *Route Transformation* object conditioned on the request received. The *Route* conditions should be defined to take care of routing all the incoming data to either of the two responses at a time, avoiding any unexpected responses due to race conditions.

![](/files/kwrOL1vGBdOoZLCOhZuM)

Since no data is flowing for a ‘No Content’ response, such responses can be controlled using *Anchor Maps.* These are mapped with the *Route Transformation* outgoing node for the respective rule.

To create an anchor map, press the icon on the API flow toolbar and create a map from the UnderProcess rule node of the *Route Transformation* to the ‘Resp\_200\_02’ Response object.

![](/files/avRBy6PAiOUdyxSPn389)

This concludes the working of multiple responses in an API flow.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.astera.com/api-flow/api-publishing/develop/multiple-responses-using-conditional-route.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
