You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ve received some information from our peers regarding the upcoming deprecation of the api.reposify.com/v2 endpoints. Currently, I'm using these endpoints to retrieve footprints and services for each footprint.
Could you please confirm if this API is indeed being deprecated? If so, what is the recommended best practice for pulling vulnerabilities for external assets? So far, I haven't found a suitable method for doing this.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey Guys,
I’ve received some information from our peers regarding the upcoming deprecation of the api.reposify.com/v2 endpoints. Currently, I'm using these endpoints to retrieve footprints and services for each footprint.
From what I’ve been informed, the new recommended approach is to use https://api.crowdstrike.com/fem/queries/external-assets/v1 instead of https://api.reposify.com/v2/company/paramount.com/footprints.
Could you please confirm if this API is indeed being deprecated? If so, what is the recommended best practice for pulling vulnerabilities for external assets? So far, I haven't found a suitable method for doing this.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions