In the API, the user should be able to use a more RESTful method for navigating to a particular resource by providing the ID in the path, rather than as a search parameter.
This currently provides some output, but it appears to have a lot of HTML from the content details page, and would need some coding to match the expected API response.
In the API, the user should be able to use a more RESTful method for navigating to a particular resource by providing the ID in the path, rather than as a search parameter.
For example, https://catalog.archives.gov/api/v1/id/485 should work just as well as https://catalog.archives.gov/api/v1/?naIds=485
This currently provides some output, but it appears to have a lot of HTML from the content details page, and would need some coding to match the expected API response.