Skip to main content
PUT
Create routing

Authorizations

Authorization
string
header
default:App
required

This is the most secure authorization type and the one with the most flexibility.

API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.

You can manage your API keys from GUI, or programmatically with dedicated API.

API key Authorization header example:

Body

application/json
expression
object
required

Query for logical validation of new messages. See Routing for more info.

queueId
string
required

Queue Id is a destination queue where the new message will be assigned to.

Maximum string length: 255
priority
enum<string>
default:NORMAL

Conversation priority.

Available options:
URGENT,
HIGH,
NORMAL,
LOW
enabled
boolean
default:true

Enabled is a boolean value (TRUE, FALSE), so the rule is engaged or avoided in the routing process. If not provided will be set to default.

name
string

Rule name, light description of expression logic.

Maximum string length: 255
routeOnlyDuringWorkingHours
boolean
default:false

When set to true, it indicates that the route should only be processed during designated working hours. Set up working hours

Response

OK

statusCode
enum<string>
Available options:
SUCCESS,
ERROR
message
string