List device model overrides

GET

/phones/models/{brand}/{model}/overrides

Last modified:2026-09-25 06:33:33

OperationId:ListDeviceModelOverrides

device_models.overrides is a key="value" blob in exactly the format of the domain provisioning defaults, and this resource serves it the same way: one object per option, validated against NDP's parser, so a value the API accepts is one NDP will read. The whole column is still on DeviceModelRow as device-models-overrides-blob and still writable through PUT /phones/models/{brand}/{model} (which now lints it the same way). A model override is ONE column of ONE row: there is no default-server axis and no synchronous / -applied report. {brand} is vendor-cased (Polycom), as on /phones/models, not the lowercase /brand-defaults slug. 404 when the model does not exist. One object per option, in the order NDP evaluates them. Readable by any scope that can read /phones/models. ?option-name= addresses one option whose name the path cannot carry (it contains /, or is literally raw).

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Query Params

Responses

🟢200OK

application/json

Options

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/phones/models///overrides?option-name=undefined&sort=undefined&limit=undefined&start=undefined' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Example 1

[
    {
        "device-models-brand": "string",
        "device-models-model": "string",
        "option-name": "string",
        "option-value": "string"
    }
]

Modified at 2026-09-25 06:33:33

Delete a device model

Add a device model override