Whether you are building a smartwatch app for Laudes, an Alexa skill for Completas, or simply want to embed the Divine Office into your parish website, the GitHub JSON ecosystem provides the most reliable, transparent, and customizable foundation.
If you have found a .github.io/json endpoint, here is how to integrate it into your project. Step 1: Fetch the Data (JavaScript Example) async function fetchLiturgia(fecha = '2026-05-07') const response = await fetch(`https://example.github.io/liturgia-horas/data/$fecha.json`); if (!response.ok) throw new Error('Liturgia not found for this date'); const data = await response.json(); return data; liturgia de las horas.github.io json
This endpoint computes the proper psalms, antiphons, and readings based on the General Roman Calendar. This is the holy grail for app developers. Given the keyword is in Spanish ( liturgia de las horas ), many JSON schemas offer a bilingual view: Whether you are building a smartwatch app for
"antiphon": "es": "Cantad al Señor un cántico nuevo", "la": "Cantate Domino canticum novum" This is the holy grail for app developers
General Instruction of the Liturgy of the Hours (official guidelines) | GitHub Actions for Liturgical Data .
"date": "2026-05-07", "liturgical_day": "Jueves de la IV semana de Pascua", "hours": "laudes": "invitatorio": "antiphona": "El Señor ha resucitado, aleluya.", "psalmus": "Salmo 94" , "psalmodia": [ "psalm": "Salmo 62", "antiphon": "De madrugada te busco, Señor" , "canticum": "Daniel 3", "antiphon": "Bendito eres, Señor" ], "lectio_brevis": "Romanos 6, 8-9", "oratio": "Oh Dios, que nos alegras cada año..." , "visperas": ...
Some projects don't store static JSON but generate it on-the-fly via GitHub Actions. For example, a repository might expose: