08-05-2025 05:27 AM
Hi Cisco Community,
I’m using the Cisco EoX API as part of an automated script to retrieve End of Life and End of Support information for our network devices based on their serial numbers.
The script was working perfectly until recently — I was able to fetch EoX data without any issues. However, in the past few days, I’ve started encountering the following response for all devices in the dataset (300+ entries):
Output : No EoX data found for [device]
The token generation works fine, and the API calls are executing successfully. But no data is returned even for devices that I know are valid and previously returned correct results.
To cross-verify, I checked a few of these devices manually using the Cisco SNTC Device Coverage Checker. For example, one of the models — C9300-48UXM-A — shows coverage until 2033 and no EoX announced yet (see attached screenshots).
Any help or clarification would be greatly appreciated.
Thanks
08-05-2025 06:21 AM
The C9300-48UXM-A has no announced end of life, so the response from the API is:
08-06-2025 10:44 PM - edited 08-06-2025 10:47 PM
Hi,
Just wanted to confirm that I’m experiencing the exact same issue with the Cisco EoX API.
My script has been working fine until recently, but over the past few days, every serial number lookup fails — even ones that previously returned valid EoX data. The API requests go through successfully and the token is valid, but the response contains either no data or this error:
EOX information does not exist for the following product ID(s): [serial]
To rule out issues on my side, I re-tested known working serials and confirmed the issue persists. This appears to be a backend issue.
I’ve sent an email to the Cisco API support team to report the problem and will update here if I get a response.
08-07-2025 07:17 AM
09-05-2025 01:50 AM - edited 09-05-2025 02:01 AM
I do not know, how your script works. But to check that the issue is not on your side, you should query the API directly e.g. with CURL or Postmann.
I do get a response from the API for the SN you mention. Perhaps you do not evaluate the complete response.
This is the request:
https://apix.cisco.com/supporttools/eox/rest/5/EOXBySerialNumber/1/FJC270110N4?responseencoding=json
This is the response from the API:
{
"PaginationResponseRecord": {
"PageIndex": 1,
"LastIndex": 1,
"TotalRecords": 1,
"PageRecords": 1
},
"EOXRecord": [
{
"EOLProductID": "",
"ProductIDDescription": "",
"ProductBulletinNumber": "",
"LinkToProductBulletinURL": "",
"EOXExternalAnnouncementDate": {
"value": "",
"dateFormat": null
},
"EndOfSaleDate": {
"value": "",
"dateFormat": null
},
"EndOfSWMaintenanceReleases": {
"value": "",
"dateFormat": null
},
"EndOfRoutineFailureAnalysisDate": {
"value": "",
"dateFormat": null
},
"EndOfServiceContractRenewal": {
"value": "",
"dateFormat": null
},
"LastDateOfSupport": {
"value": "",
"dateFormat": null
},
"EndOfSvcAttachDate": {
"value": "",
"dateFormat": null
},
"UpdatedTimeStamp": {
"value": "",
"dateFormat": null
},
"EOXError": {
"ErrorID": "SSA_ERR_026",
"ErrorDescription": "EOX information does not exist for the following product ID(s): C9300-48UXM-A",
"ErrorDataType": "PRODUCT_ID",
"ErrorDataValue": "C9300-48UXM-A"
},
"EOXMigrationDetails": {
"PIDActiveFlag": "",
"MigrationInformation": "",
"MigrationOption": "",
"MigrationProductId": "",
"MigrationProductName": "",
"MigrationStrategy": "",
"MigrationProductInfoURL": ""
},
"EOXInputType": "ShowEOXBySerialNumber",
"EOXInputValue": "FJC270110N4"
}
]
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide