I have an endpoint in API 1 (my api) that queries API 2 (another companies api) to view and edit objects stored in API 2's database. API 1 is essentially acting as a wrapper service around API 2, providing some extra functionality.
If a call to API 2 within API 1 ends up with a 404 being returned (in my case because an object is still provisioning in the background) then should this 404 from the sub API call be passed back to the user? The request is correct, from their end they have made no mistakes other than maybe being a little too quick off the draw with calling endpoints on API 1 so soon after the object creation.
Especially in this case where the object DOES exist, but some of the metadata that might be required for the call doesn't exist so that part 404s. At the moment this 404 error is being packaged up in a 500, but I'm not 100% sure this is correct.