Update user CDR

Sets the disposition fields on one call detail record (CDR) of a user: notes, disposition, reason, pac, and time_disp. Requires Basic User scope for your own calls, or a scope that covers the user: Site Manager for its site, Office Manager, Call Center Supervisor, or Route Manager for its domain, Reseller, or Super User.

The path's {callid} picks the record. The record must be from this month or last month, and within your scope. Send only the fields to change; the other fields of the record are never written. call-disposition-submitted-datetime takes RFC 3339 or Unix seconds and is stored as Unix seconds. The v1 names (notes, disposition, reason, pac, time_disp) are accepted as the same fields.

A 202 means the change was published over the service bus (SBUS), not that it is applied: read the record back to see it. A body with none of the five fields returns 400, and so does a body call-parent-cdr-id that differs from the path. A record that is not found, or not within your scope, returns 404.

Responses

🟠400

application/json

The body has none of the five fields, call-parent-cdr-id in the body differs from the path, call-disposition-submitted-datetime is neither RFC 3339 nor Unix seconds, or the service bus did not take the change. The message says which. Correct the body, or retry later for the service bus.

Bodyapplication/json

🟠401Authentication Required

🟠403Forbidden

🟠404Not Found

🟢202Accepted

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/domains//users//cdrs/1780021234567' \ --header 'Content-Type: application/json' \ --data '{ "call-disposition": "Sale", "call-disposition-reason": "New order", "call-disposition-notes": "Ordered two handsets.", "call-account-code": "4410", "call-disposition-submitted-datetime": "2026-09-01T14:36:00+00:00" }'

Request

Responses