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:
Request URL
Async Function Response
https://parse.ubidots.com/prv/username/my-function?_blocking=false
HTTP/1.1 202 Accepted
Content-Type: application/json
​
{"activationId":"653ca08ce2104290bca08ce21002909c"}
👍 Particle Webhooks
It is a good idea to use async execution when sending data to an UbiFunction from external platforms like Particle.io or LoRaWAN Network Servers. This prevents failed or timed-out requests, which could affect server rating. 
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 about Particle's API Limits and Policy.
Reference
URL Parameter
Values
Mandatory
_blocking
Not specified, or "False":

Not specified: By default the function will return a response only after finalizing the execution.
False: The function will immediately return a "202 Accepted" response, with a JSON body including the activationID of the function.
No

CORS Policy

DaaS (Decoder as a Service)

Last modified 1yr ago

URL Parameter	Values	Mandatory
_blocking	Not specified, or "False": Not specified: By default the function will return a response only after finalizing the execution. False: The function will immediately return a "202 Accepted" response, with a JSON body including the activationID of the function.	No