> For the complete documentation index, see [llms.txt](https://docs.zingy.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingy.ai/app-editor/page-flow/toolbox-blocks/http-post.md).

# HTTP Post

{% hint style="info" %}
**Block Information**

Available in: Page Flow and Cloud Flow

Toolbox Category: HTTP/REST

Block Type: [Regular](/app-editor/page-flow/block-anatomy.md#regular-block)
{% endhint %}

The **`HTTP Post`** block is used to send a [HTTP Post request](https://en.wikipedia.org/wiki/POST_\(HTTP\)) from your page or form to a specified URL.

<div align="left"><figure><img src="https://3401585094-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmnBepgycwgisXr9ya1N4%2Fuploads%2Fz3pt3GKtQT9zmq4lqkOy%2Fimage.png?alt=media&amp;token=c0b48a0c-1d8a-4012-97fe-b4d8035a4377" alt="" width="383"><figcaption><p>HTTP Post block</p></figcaption></figure></div>

{% hint style="danger" %}
NOTE:

Create a [API Call](/app-editor/connections/services/api-call.md) [Connection](/app-editor/connections.md) and use the [Execute API Call](/app-editor/page-flow/toolbox-blocks/execute-api-call.md) block instead, if any of the following apply:

* Sensitive or secret information needs to be sent in the *Data* value parameter.
* The server you want to communicate with requires setting specific HTTP headers and or use authentication.
  {% endhint %}

The block consists of the following (from top to bottom):

* *URL:* [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts a [*text*](/app-editor/page-flow/references/value-types.md) value representing the URL where you want the request to be sent.
* *Data*: Optional [Value Parameter](/app-editor/page-flow/block-anatomy.md#value-parameters) that accepts an [object](/app-editor/page-flow/references/value-types.md) value representing the data to be sent.
* *Success Tasks*: a [Flow Parameter](/app-editor/page-flow/block-anatomy.md#flow-parameters) where you connect blocks that specify what you want done when the operation completes successfully. The [HTTP Data](/app-editor/page-flow/toolbox-blocks/http-data.md) block can be used to access the output (if any).
* *Fail Tasks*: a [Flow Parameter](/app-editor/page-flow/block-anatomy.md#flow-parameters) where you connect blocks that specify what you want done when the operation reports an error. The [HTTP Error](/app-editor/page-flow/toolbox-blocks/http-error.md) block can be used to access the error information.


---

# 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://docs.zingy.ai/app-editor/page-flow/toolbox-blocks/http-post.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.