> For the complete documentation index, see [llms.txt](https://docs.overthereality.ai/over-sdk-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overthereality.ai/over-sdk-manual/sdk-coding-nodes/over-nodes/web-request.md).

# Web Request

The **WebRequest** node provides a streamlined and user-friendly way to perform **REST API calls** directly from your Unity project. This node simplifies the process of sending HTTP requests (such as GET, POST, PUT, or DELETE) and handling responses, making it an essential tool for integrating external services, fetching data, or interacting with APIs.

**Inputs**

* **URL (String)** : The endpoint URL of the API you want to call. Ensure the URL is properly formatted (e.g., `https://api.example.com/endpoint`).
* **Method (String)** : The HTTP method to use for the request (e.g., `GET`, `POST`, `PUT`, `DELETE`).
* **Headers (Dictionary)** : Optional headers to include in the request, such as authentication tokens or content types.
* **Body (String)** : Optional payload to send with the request, typically used for `POST` or `PUT` requests. The body can be formatted as JSON, XML, or other supported formats.

**Outputs**

* **Success (Boolean)** : Indicates whether the request was successful (`true`) or failed (`false`). This is useful for quickly determining if the API call completed without errors.
* **Text (String)** : The raw response received from the API, typically in JSON, XML, or plain text format. If the response is in JSON format, you can parse it into a structured object using **Newtonsoft.Json** , a powerful and widely-used JSON library.

<figure><img src="/files/8V6TXZKNqApIJbnEli4D" alt=""><figcaption></figcaption></figure>


---

# 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.overthereality.ai/over-sdk-manual/sdk-coding-nodes/over-nodes/web-request.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.