Update CDR

PUT

/cdrs/{callid}

Last modified:2026-09-27 16:23:09

OperationId:UpdateCDRRecord

Sets the disposition fields on one call detail record (CDR): notes, disposition, reason, pac, and time_disp. Requires Reseller or Super User scope, and a Reseller updates only calls in its territory.

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.

Request

Authorization

Path Params

Body Params application/json

Examples

Responses

🟢202

application/json

The change was published. It is applied when the service bus delivers it.

Bodyapplication/json

🟠400

🟠401Authentication Required

🟠403Forbidden

🟠404Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/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"
}'

Response Example

202 - Set disposition

Published, not yet applied.

{
    "code": 202,
    "message": "Accepted"
}

Modified at 2026-09-27 16:23:09

Read CDR

Read domain CDR