If the user cannot access the idv this will be the ONLY IdentityVerificationrResponse
they will ever get, regardless of the IdentifyUserRequest or the id* sent.
*there is a cavet about what id you send, as providing a non existing id will make the server throw a 404 http error instead of returning an idv response at all. Although this doesn’t contradict what previously stated, as an http error is not an IdentityVerificationResponse instance, don’t rely on
the api always returning IdentityVerificationUnavailable if the user cannot access the idv.