Skip to main content
POST
Create Assignment Rule

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

team_id
string
required

Body

application/json

Create carries its own fields rather than the AssignmentRule model, so the fields a caller cannot set are absent rather than merely documented as read-only.

display_order is one of them. A new rule is always appended after the team's current last, which is the safe end: the first matching rule wins, so a rule that lands last cannot pre-empt the routing a team already has. Placing it somewhere else is a second call, and needs a read first anyway -- the values are sparse, so "between these two rules" means knowing what both of them are.

conditions
AssignmentRuleConditionGroup · object[]

When the rule applies. Empty matches every ticket.

actions
AssignmentRuleAction · object[]

At least one is required, which is also what rejects an empty body.

displayOrder
integer<int32> | null

Absent appends the rule after the team's last one, which is the safe end: the first matching rule wins, so a rule landing last cannot pre-empt existing routing. Values are not renumbered around a write, so a value given here may tie with an existing rule, in which case created_at decides which of the two is evaluated first.

Response

200 - application/json

Success

data
data · object