Check status code AND content
check status code AND content (via regexp) with the same "ping". Currently you should configure 2 "ping", one for the status code and one for the content
That’s a pretty limited use-case, an API returning the good content but wrong status is pretty unlikely to happen, not worth modifying the product. If you really want to check both, feel free to use two checks with one very slow (10m) so it doesn’t cost much.
Bot Bootstragram commented
To detect any bad implementation, useful for rest api. For example, the response has the status code expected but the wrong message (you can't detect this case if you check the status code only). Or the response has the message expected but the wrong status code (you can't detect this if you check the message only).
During development phase, you can try to cover all cases with unit testing.
But during the production phase, you have sometimes some unexpected event, the API can mess up. Check status code AND content can help to detect this kind of bug.