> For the complete documentation index, see [llms.txt](https://dev.ubidots.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ubidots.com/ubifunctions/advanced/async-execution.md).

# Async execution

You can invoke a function through its HTTPS endpoint without waiting for a response. To do this, add the `?_blocking=false` parameter to the URL:

{% tabs %}
{% tab title="Request URL" %}

```
https://parse.ubidots.com/prv/username/my-function?_blocking=false
```

{% endtab %}

{% tab title="Async Function Response" %}

```
HTTP/1.1 202 Accepted
Content-Type: application/json

{"activationId":"653ca08ce2104290bca08ce21002909c"}
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
👍 **Particle Webhooks**

Use **async execution** when sending data to a UbiFunction from external platforms such as [Particle.io](https://particle.io/) or LoRaWAN network servers. This helps prevent failed or timed-out requests, which can affect server ratings.

For example, Particle skips webhook attempts after too many timeouts or 4xx/5xx HTTP status codes. That can lead to data loss in your IoT application. [Learn more](https://docs.particle.io/reference/device-cloud/webhooks/#limits) about Particle's API limits and policy.
{% endhint %}

### Reference

| URL Parameter  | Values                                                                                                                                                                                                                                                                                                                                                                           | Mandatory |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- |
| **\_blocking** | <p><strong>Not specified,</strong> or "<strong>False":</strong><br></p><ul><li><strong>Not specified</strong>: By default, the function returns a response only after execution finishes.</li><li><strong>False</strong>: The function immediately returns a <code>202 Accepted</code> response with a JSON body that includes the function <code>activationId</code>.</li></ul> | No        |


---

# 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://dev.ubidots.com/ubifunctions/advanced/async-execution.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.