❌ Invalid Object Response for Certain Object IDs

[ZOUHAIRFGRA]

Title:

❌ Invalid Object Response for Certain Object IDs

Description:

When requesting certain objects from the API, the response returns { "message": "Not a valid object" } instead of proper metadata. For example, object ID 855340 does not return a valid response.

Steps to Reproduce:

1. Fetch object details from the API:

   GET https://collectionapi.metmuseum.org/public/collection/v1/objects/855340
   

2. The response is:

   {
     "message": "Not a valid object"
   }

Expected Behavior:

• The API should return either:
  • A proper object response, if the object exists.
  • A structured error message with details explaining why the object is missing (e.g., removed, not public, etc.).

Additional Context:

• This issue affects certain objects but not all. Other IDs work as expected.
• Please confirm if this object is permanently removed or if it's an API error.

[stephenhmarsh]

Hi Zouhair, thanks for creating this issue. I will make sure that my colleagues who maintain this API get a chance to see it. I personally agree with everything you said.

In the meantime, I can tell you that 855340 represents an object that is not part of The Met's own collection, but is actually an item on loan from another institution. Hopefully that context helps you to ignore these cases, which are probably not API errors. PS, I know this is not ideal but you can also use our web frontend to confirm certain details, like loan status: https://www.metmuseum.org/art/collection/search/855340 (/art/collection/search/:objectID)

[ZOUHAIRFGRA]

Subject: RE: ❌ Invalid Object Response for Certain Object IDs

Hi Stephen,

Thank you for your response and for providing clarification about loaned objects. That explanation makes sense, and we appreciate the insight.

Given that some objects in the API are on loan and not part of The Met’s permanent collection, is there any specific flag in the API response that indicates whether an object is on loan? If so, we could use that to filter out these cases on our end, ensuring a smoother user experience.

If no such flag currently exists, would adding one be a possible enhancement for the API? This would help developers distinguish between truly "invalid" objects and those that are simply loaned items.

Thanks again for your time and assistance!

Best,
Zouhair