Skip to main content
Add, overwrite or remove custom properties on an already-existing call. Use this for data that becomes available after the call was created, e.g. an outcome your system validates a few minutes later. Merge semantics: a value adds or overwrites the property, null removes it, and properties left out are untouched. The patch is applied whole or not at all: a property Roark sets itself, or a value whose type differs from the type the project already stores that property as, rejects the request with a 400 and nothing is written. A 409 means another request created one of the properties with a different value type at the same moment; nothing was written. Optionally pass metrics to (re)score metrics over the updated properties, which triggers a billed metric collection job and requires the metric:create permission.
Calls PATCH /v1/call/{callId}/properties

​
Arguments

​
string
required
The call-id.

​
Options

​
object
required
Properties to change on the call. A string, number or boolean value adds the property or overwrites it; null removes it. Properties left out are untouched. Keys are stored in snake_case, as on POST /v1/call. A property keeps the value type it was first stored with in the project, so a value of another type is rejected. Properties Roark sets itself (direction, duration_seconds, agent_id, …) can’t be changed. Max 100 per request.
​
array
Optional. Metric definitions to (re)score on this call once the properties are written, e.g. metrics that read the call’s properties. Triggers a metric collection job (billed, credit-gated) and requires the ‘metric:create’ permission. Omit to update properties without scoring. Max 20.

​
Example

Every command also takes the global options and sets one of the exit codes.