We, at getBible, have a robust system to ensure our API stays up-to-date with the Crosswire project's modules. Let me walk you through how it all works, making sure it all makes sense without any technical jargon.

Our Bible text comes directly from the Crosswire modules. To track any changes, we create what are known as "hash values" for every chapter, book, and translation. Think of these hash values as unique identifiers that change when the content they're associated with changes. This system firmly links getBible with the Crosswire modules.

Every month, a process kicks off that takes about three hours. During this time, we pull the Bible text again from the Crosswire modules and place it into a special repository. We then check if there are any changes by comparing the new hash values and the actual text with the old ones. If we detect any changes, we automatically update our official getBible repository, which holds the JSON API files. This process has been running flawlessly for nearly three years and happens without any human intervention.

Once our official repository is updated, a new event is triggered to push these fresh files to our actual API endpoints, which is https://api.getbible.net/v2/translations.json. This URL lists all the available translations in our API.

At this point, all the hash values are updated too. So, any application using our API should monitor for changes in these hash values, either on the chapter, book, or translation level. If a change in hash is detected, they should update their systems accordingly.

Changes in hash values may occur due to fixes in the text, such as adding missing verses or correcting spelling mistakes, or any other types of errors detected by the Publishers maintaining the modules at Crosswire.

The Crosswire project, also known as the SWORD Project, is therefore the "source of truth" for getBible. Any change in the Crosswire modules reflects in our API within a few days, ensuring our API always provides the most accurate and up-to-date Bible text. This will continue for as long as getBible exists and we're able to run our build scripts.

Remember, we're all in this together to maintain the integrity and accuracy of the Bible text. So, if you have any questions or need further clarification, please feel free to open issues in the relevant repositories, and we'll respond as soon as we can.

Thank you very much for your attention and for being a part of our mission at getBible.