cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1133
Views
0
Helpful
3
Replies

Cisco EOX API by date suddenly stops working

angelest
Level 3
Level 3

try to do a debug  and response is as below. Trying to get all EOL announcement for year 2025

https://apix.cisco.com/supporttools/eox/rest/5/EOXByDates/1/2025-01-01/2025-12-31?responseencoding=json

 

2025-11-24 13:00:06,391 - INFO - Successfully obtained access token
2025-11-24 13:00:06,391 - INFO - Testing EOXByDates for 2020 (2020-01-01 to 2020-12-31) with EO_SALE_DATE...
2025-11-24 13:00:07,359 - INFO - Status Code: 200
2025-11-24 13:00:07,360 - INFO - Response: {'EOXError': {'ErrorID': 'SSA_ERR_010', 'ErrorDescription': 'The eoxAttrib value is invalid. Please correct the eoxAttrib value and try again.'}}

  

2 Accepted Solutions

Accepted Solutions

Its working again.
eoxAttrib is not mandatory attribute. If no attribute provided it will provide all columns.

URI

https://apix.cisco.com/supporttools/eox/rest/5/EOXByDates/{pageIndex}/{startDate}/{endDate}

Thank you for your reply, I appreciate it.

View solution in original post

Awesome, i have seen this API to sort of flakey at times. odd behaviour on the error you shared, it appeared that the API was trying to enforced stricter parameter validation. 

Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

View solution in original post

3 Replies 3

@angelest try https://apix.cisco.com/supporttools/eox/rest/5/EOXByDates/1/2025-01-01/2025-12-31?responseencoding=json&eoxAttrib=EO_EXT_ANNOUNCE_DATE

 

I think you are missing the parameter called eoxAttrib to specify which date field the range should be filtered against.
Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

Its working again.
eoxAttrib is not mandatory attribute. If no attribute provided it will provide all columns.

URI

https://apix.cisco.com/supporttools/eox/rest/5/EOXByDates/{pageIndex}/{startDate}/{endDate}

Thank you for your reply, I appreciate it.

Awesome, i have seen this API to sort of flakey at times. odd behaviour on the error you shared, it appeared that the API was trying to enforced stricter parameter validation. 

Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io