Handling Errors

Overview

Server responses can be confusing, so we want to help by providing a description and, where applicable, a remedy for the most common replies you'll get back from API.Bible.

Common Responses

These codes follow RFC 2616 and RFC 6585.

• 202: Your request was successful. No action needed on your part.
• 400: The request was formatted incorrectly. Look at your request parameters and ensure they match the specifications of the API.
• 401: We couldn't authenticate you. Ensure you are passing your API key (more on that here) and that it is valid and typed correctly.
• 403: You are requesting a Bible that you don't have access to. Double check via the /bibles endpoint that the bible_id you are using is a part of your plan. If it is, contact support@api.bible. If it is not, consider adding it to your plan.
• 404: The endpoint (or bible_id if applicable) you are accessing doesn't exist. If after double-checking your endpoint and bible_id this error persists, contact support@api.bible.

Note: Error descriptions may vary per-endpoint. More information on individual error codes can be found by searching for your endpoint in our API Reference.