Update an alias's metadata
Updates an alias's metadata fields (name, description, enabled, metadata). Setting enabled to false on a platform-generated alias fronted by a widget connector is rejected with 409; disable the connector instead. To replace the routing policy, use PUT /v2/agent_aliases/{alias_key}/policy. Policies are atomic and do not support partial updates.
Path parameters
The unique key that identifies an alias. Alias keys are independent of agent keys. The same string can exist as both an alias key and an agent key in the same customer account. Calls to /v2/agent_aliases/{key}/... target the alias. Calls to /v2/agents/{key}/... target the agent.
Headers
The platform makes a best effort to complete the request in the specified seconds, or it times out.
The platform makes a best effort to complete the request in the specified milliseconds, or it times out.
Request body
Response
The updated alias.
Example response
{
"key": "support",
"name": "Customer Support",
"policy": {
"rules": [
{
"match": "(get('$.session.metadata.tenant') == 'us') and (get('$.session.metadata.tier') == 'gold')",
"targets": {
"partition_by": "get('$.session.metadata.user_id', '')"
}
}
]
}
}Changes
Changed in 1 of the 7 revisions of this API.1
- ○
added the non-success response with the status
response-non-success-status-added
- ○