# Redirect

The **\<Redirect>** verb transfers control of a call to the RCML at a different URL. All verbs after **\<Redirect>** are unreachable and ignored.

## Redirect Attributes

| Name       | Allowed Values | Default Value |
| ---------- | -------------- | ------------- |
| **method** | GET, POST      | POST          |

{% hint style="info" %}
&#x20;**Method.** The 'method' attribute takes the value 'GET' or 'POST'. This tells CallAPI whether to request the URL via HTTP GET or POST.
{% endhint %}

### Nesting

Example of how to use the \<Redirect> verb:

## Example

{% hint style="info" %}
For an example of how to use the  verb see below.
{% endhint %}

```markup
<Response>
    <Redirect>http://foobar.com/instructions</Redirect>
</Response>
```


---

# Agent Instructions: 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:

```
GET https://apidocs.api19.com/call-api-markup/api-call-markup-language/redirect.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.