> For the complete documentation index, see [llms.txt](https://docs.cloud.hoverfly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloud.hoverfly.io/create-simulations/building-a-json-response.md).

# Building a JSON Response

Hoverfly Cloud uses {{handlebars syntax}} to provide template scripting with which you can build out a JSON response. Typically, this would involve relying on some data that arrives as part of the request, either as a JSON payload itself, or as part of the path, query parameter, or header.

Templating can be used to perform validation, logic, arithmetic and to generate synthetic data to be used in constructing the body of your response, amongst many other powerful capabilities.

This brief section will discuss the basics of using Hoverfly's templating to generate a JSON response.

You can read more about the other templating features [here](/create-simulations/using-templating-in-simulations.md).


---

# 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://docs.cloud.hoverfly.io/create-simulations/building-a-json-response.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.