I was approved right away, but I work for a church as well. If your app is a commercial app, they may review it manually.
I just ran into the same issue. I poked around in the new API and came up with the following quick hack. You’ll need to get an API key from http://api.esv.org, then replace the mbbt_add_esv_text function with the code below.
//Returns ESV text
function mbbt_add_esv_text ($reference, $heading) {
$esv_url = 'http://api.esv.org/v3/passage/html/?q='.urlencode($reference).'&include-headings=false&include-footnotes=false';
if ($heading === FALSE || strtolower($heading) == 'span')
$esv_url .= '&include-passage-references=false&include_audio_link=false&include-first-verse-numbers=false';
$esv_args = array(
'headers' => array (
'Authorization' => 'Token XXXXXXXXXXXXXXXXXXX'
)
);
$response = json_decode(wp_remote_retrieve_body(wp_remote_get($esv_url, $esv_args)));
return $response->passages[0];
}