Empty response adding 9800 by Mac

Stephen Welsh · ‎08-22-2025

When adding a 9800 series device by Mac Address (POST https://webexapis.com/v1/devices) the response is a 204 (No Content) with no body and the device is added to Webex.

Request

POST /v1/devices HTTP/1.1
Authorization: Bearer XXX
Content-Type: application/json; charset=utf-8
Host: webexapis.com
Connection: close
User-Agent: RapidAPI/4.3.7 (Macintosh; OS X/15.5.0) GCDHTTPRequest
Content-Length: 136
{"mac":"0CD5D39E9XXX”,”model":"Cisco 9841","personId":"XXX”}

Response

HTTP/1.1 204 No Content
X-Content-Type-Options: nosniff
Trackingid: ROUTERGW_5dd38f20-615a-46ac-9772-8782a4f1ce75
Date: Fri, 22 Aug 2025 20:20:20 GMT
X-Envoy-Upstream-Service-Time: 1840
X-Content-Type-Options: nosniff
Vary: Origin
Client-Compatibility-Hint: Unknown
X-Normalized-Path: /csdm/api/v1/hydra/devices
Trackingid: ROUTERGW_5dd38f20-615a-46ac-9772-8782a4f1ce75
Server: istio-envoy
Connection: close

This is clearly an error with just the 9800, when I do the same request but for a 8800 (like the 8841) I get 200 status code and the following body:

{
  "id": "XXX",
  "callingDeviceId": "XXX",
  "webexDeviceId": null,
  "displayName": "Stephen Welsh",
  "personId": "XXX",
  "orgId": "XXX",
  "capabilities": [],
  "permissions": [],
  "product": "Cisco 8841",
  "type": "phone",
  "tags": [],
  "mac": "0CD5D39E9XXX",
  "sipUrls": [
    null
  ],
  "errorCodes": [],
  "connectionStatus": "unknown",
  "workspaceLocationId": "XXX",
  "locationId": "XXX",
  "managedBy": "CISCO",
  "devicePlatform": "cisco",
  "lifecycle": "UNKNOWN",
  "plannedMaintenance": "off"
}

Can this be reported as a bug? happy to provide more details if required.

Stephen

Stephen Welsh · ‎08-22-2025

I may have answered my own question, bit strange but according to this blog post PhoneOS devices (9800) are not fully added to Webex until they first register. From testing this includes querying for the device after being added it is not listed, this may impact the user experience if we cannot query if the device is already added (i.e. may appear like an error). This does make provisioning the 9800 via the Webex API more complex, in-particular handling edge cases.

Is this always going to be the case as it does make for in inferior developer and user experience working with the latest phone models compared to MPP devices?

Jeff Marshall · ‎08-25-2025

As of right now it doesn't appear that there would be any change to them being required to be registered before they show up in the devices API. However, you can submit a feature request for this through https://ciscocollabcustomer.ideas.aha.io with your detailed use case and your concerns as that goes to the product teams for review.