ladsweb api-v2 openapi content empty

[tadejong]

We are using a Python script to routinely find and download VIIRS level 1 data (V??02MOD and V??03MOD specifically) from LAADS DAAC. We use api-v2 as specified at https://ladsweb.modaps.eosdis.nasa.gov/tools-and-services/api-v2/specs/content to find which files to download and subsequently use wget with a auth token to download.
This has worked nicely for several months. However, since 2025-04-23 05:00 (CEST), this hasn't produced valid output anymore. Looking in the logs, the run on 23rd got "504 Gateway Timeout"s. Since (at least) 2025-04-24 05:00, the API is returning results with empty content, even though it seems aware that there is content, as it is returning multiple pages.

An example query we try is: 'https://ladsweb.modaps.eosdis.nasa.gov/api/v2/content/details/?products=VNP03MOD&temporalRanges=2025-04-10+07%3A52..2025-04-11+09%3A32&illuminations=D&regions=[BBOX]W72.66+N23.01+E72.66+S23.01'
(But also the link from the api spec (https://ladsweb.modaps.eosdis.nasa.gov/api/v2/content/details?products=VNP14&temporalRanges=2019-10-23..2019-11-06&regions=[BBOX]W-125%20N40%20E-119.6%20S36.5) returns an empty list)

Is this the right place to ask about this? Or is there a better place to contact about this?

[tadejong]

Just to add, I notice that the same api for NRT3 at https://nrt3.modaps.eosdis.nasa.gov/api/v2/ is still giving responses as expected.

[LAADS_UserServices_M]

Seems like you are missing version information in the request. So, try adding collection version information (like &archiveSets=5200) to the request. For example your requests would be like:
https://ladsweb.modaps.eosdis.nasa.gov/api/v2/content/details?products=VNP14&archiveSets=5200&temporalRanges=2019-10-23..2019-11-06&regions=[BBOX]W-125%20N40%20E-119.6%20S36.5
And
https://ladsweb.modaps.eosdis.nasa.gov/api/v2/content/details/?products=VNP03MOD&archiveSets=5200&temporalRanges=2025-04-10+07%3A52..2025-04-11+09%3A32&illuminations=D&regions=[BBOX]W72.66+N23.01+E72.66+S23.01
For more information consult API-V2 user guide at:
https://ladsweb.modaps.eosdis.nasa.gov/tools-and-services/#api-v2

[tadejong]

Thanks for the reply. If I include the relevant archiveSets I do get a valid response now, which resolves my problem for now.

However, I might be overlooking something, but from the API-V2 specification it is totally unclear to me that some constraints parameters are apparently mandatory instead of optional?
Even the example given for archives on https://ladsweb.modaps.eosdis.nasa.gov/tools-and-services/api-v2/specs/content as you linked itself does not include an archiveSets parameter and does not (currently) yield a valid response.
If this is indeed a recent change, it might be good to update the documentation.

[LAADSx_UserServices_M]

We will look into it.

[smartse]

I also ran into this problem and it would be helpful if it could be explained where we are supposed to find the &archiveSets= number. In my case I did track it down by manually browsing through https://ladsweb.modaps.eosdis.nasa.gov/api/v2/content/archives/allData/ until I found the relevant product. It is odd that this is now required though as it seems superfluous to &product= and as with the OP, it definitely worked without it. Adding some information to requests without &archiveSets= to alert users to the problem would also be helpful.

[LAADS_UserServices_M]

You can use the following call to find ArchiveSets:
https://ladsweb.modaps.eosdis.nasa.gov/api/v2/measurements/archiveSets
Find details:
https://ladsweb.modaps.eosdis.nasa.gov/tools-and-services/api-v2/specs/content#details