nac-collector seems to be querying certain api endpoints with parameters that do not exist for that API.
For example, the following does not even have offset as a parameter via the OpenAPI spec:
/dna/intent/api/v1/business/sda/authentication-profile
/dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global/United States&offset=1
I have noticed when using a custom endpoint list, these issues seem to appear as well, but I figure to start addressing them with the standard nac-collector list first.
(nac-parity) mikekrau@MIKEKRAU-M-X149 nac-parity % uvx --from git+https://github.com/netascode/nac-collector.git nac-collector \
--solution CATALYSTCENTER \
--output var/catalystcenter-all-items.zip
Installed 49 packages in 65ms
⠸ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 0%[03/30/26 13:26:02] ERROR GET https://10.122.20.140/dna/intent/api/v1/device-detail?offset=1 returned an unexpected status code: 500
ERROR No valid response received for endpoint: /dna/intent/api/v1/device-detail?offset=1
⠋ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━╺━━━━━━━━━━━━━ 66%[03/30/26 13:26:03] ERROR GET https://10.122.20.140/dna/intent/api/v1/network-device/6313385b-55ca-4219-a00b-4a6e8437c561/dna/intent/api/v1/wirelessControllers/%v/primaryManagedApLocations?offset=1 returned an unexpected status code: 400
ERROR No valid response received for endpoint: /dna/intent/api/v1/network-device/6313385b-55ca-4219-a00b-4a6e8437c561/dna/intent/api/v1/wirelessControllers/%v/primaryManagedApLocations?offset=1
⠸ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━╺━━━━━━━━━━━━━ 66% ERROR Failed to decode JSON from response for endpoint: /intent/api/v1/wirelessProfiles?offset=1
ERROR GET https://10.122.20.140/dna/intent/api/v1/network-device/6313385b-55ca-4219-a00b-4a6e8437c561/dna/intent/api/v1/wirelessControllers/%v/secondaryManagedApLocations?offset=1 returned an unexpected status code: 400
ERROR No valid response received for endpoint: /dna/intent/api/v1/network-device/6313385b-55ca-4219-a00b-4a6e8437c561/dna/intent/api/v1/wirelessControllers/%v/secondaryManagedApLocations?offset=1
⠧ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╺━━━ 91%[03/30/26 13:26:06] ERROR GET https://10.122.20.140/dna/intent/api/v1/business/sda/virtualnetwork/ippool?offset=1 returned an unexpected status code: 400
ERROR No valid response received for endpoint: /dna/intent/api/v1/business/sda/virtualnetwork/ippool?offset=1
⠋ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╸━ 96%[03/30/26 13:26:08] ERROR GET https://10.122.20.140/dna/intent/api/v1/enterprise-ssid?offset=1 returned an unexpected status code: 404
ERROR No valid response received for endpoint: /dna/intent/api/v1/enterprise-ssid?offset=1
⠸ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╺ 98% ERROR GET https://10.122.20.140/dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global/United States&offset=1 returned an unexpected status code: 400
ERROR No valid response received for endpoint: /dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global/United States&offset=1
⠏ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╺ 98% ERROR GET https://10.122.20.140/dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global/United States/Michigan&offset=1 returned an unexpected status code: 400
ERROR No valid response received for endpoint: /dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global/United States/Michigan&offset=1
⠸ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╺ 98%[03/30/26 13:26:09] ERROR GET https://10.122.20.140/dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global/Chicago&offset=1 returned an unexpected status code: 400
⠴ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╺ 98% ERROR No valid response received for endpoint: /dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global/Chicago&offset=1
⠧ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╺ 98%[03/30/26 13:26:10] ERROR GET https://10.122.20.140/dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global/Chicago/Test-Bldg&offset=1 returned an unexpected status code: 400
ERROR No valid response received for endpoint: /dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global/Chicago/Test-Bldg&offset=1
⠴ Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╺ 98%[03/30/26 13:26:11] ERROR GET https://10.122.20.140/dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global&offset=1 returned an unexpected status code: 400
ERROR No valid response received for endpoint: /dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global&offset=1
Processing endpoints ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100%
(nac-parity) mikekrau@MIKEKRAU-M-X149 nac-parity %
nac-collector seems to be querying certain api endpoints with parameters that do not exist for that API.
For example, the following does not even have offset as a parameter via the OpenAPI spec:
/dna/intent/api/v1/business/sda/authentication-profile
/dna/intent/api/v1/business/sda/authentication-profile?siteNameHierarchy=Global/United States&offset=1
I have noticed when using a custom endpoint list, these issues seem to appear as well, but I figure to start addressing them with the standard nac-collector list first.