...
This function retrieves all routing applications from a client account a daemon process, waiting (for a maximum of 10 seconds) for the result of running the application.
URL
Translations Ignore | ||
---|---|---|
|
...
Translations Ignore | |||||
---|---|---|---|---|---|
|
Run a Routing Application as a Daemon Process
This function runs a routing application as a daemon (background) process in a client account waiting (for a maximum of 10 seconds) for the result of running the application.
URL
Translations Ignore | ||
---|---|---|
|
Parameters
Parameter | Where | Type | Data |
---|---|---|---|
routingApplicationsID | URL | Integer | The ID of the routing application to run. |
Data
Data can be passed as content type application/json to the routing application. This will be parsed into variables which will be available in the routing application using the usual $ notation.
The variables will be named with the dotted notation, each additional level in the json structure will result in an additional dot in the variable name.
Example:
Code Block |
---|
{ "myVar1" : "123", "myStruct1": { "field1" : "value1", "field2" : 2 } } |
Will result in the following variables being declared:
Code Block |
---|
$myVar1 = "123"
$myStruct1.field1 = "value1"
$myStruct1.field2 = "2" |
Info |
---|
Note, all variables in the jtel routing engine are treated as strings, though in most cases they can be used as numeric values. |
Responses
If the request is performed, 200 OK is returned. See Return Codes for further possible status codes.
Returned Data (200 OK)
The routing result object in the IVR is used to return data from the application.
The format and content of the data returned is up to the application programmer, and can be specified freely in the object parameters: