Indeed, but in that case wouldn't you want to use the status codes that the consumed API throws by default?
In case it always throws 200 even if the request is incorrect you could use OnAfterResponse, not OnBeforeRequest, since this allows you to manipulate the response and create custom logic.
See if that helps.