# Async Execution

It is possible to invoke a function through its HTTPS Endpoint without having to wait for a response. To do this, simply 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**

It is a good idea to use **async execution** when sending data to an UbiFunction from external platforms like [Particle.io](https://particle.io/) or LoRaWAN Network Servers. This prevents failed or timed-out requests, which could affect server rating.&#x20;

For instance, Particle skips webhook attempts when too many time-outs or 4xx / 5xx HTTP status codes occur, which could translate into data loss for 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 will return a response only after finalizing the execution.</li><li><strong>False</strong>: The function will immediately return a "202 Accepted" response, with a JSON body including the activationID of the function.</li></ul> | No        |
