API Terms of Use

Who these terms are for

These terms are for anyone who uses the Muslim.Blue developer API ("the API"), at api.muslim.blue or on muslim.blue, with or without a key. Muslim.Blue is run by Muslim Blue LLC, a Wyoming limited liability company ("we", "us"). These terms add to our Terms of Use and Acceptable Use Policy, which apply to you as well. If you use the API for a company or a masjid, you agree for it, and you tell us you may.

By using the API, or by getting a key, you agree to these terms. When you get a key, we record the version of these terms in force at that moment, with the exact words.

What the API is

• The API only reads. No route of it changes anything on Muslim.Blue.
• It answers masjids (found by name, place or distance), a masjid's prayer and iqamah times by day, month or year, calculated adhan times for any place, and the Hijri date. The docs list every route.
• Reading a masjid's times, finding masjids and getting the Hijri date work without a key. Calculated times for any place need a free key.
• Every answer carries an ETag, so you can ask again cheaply.

Your keys

• Keys are free. You get one on our developer page with your Muslim Colors account, and you can see each key's use there.
• We show a key's secret once, on the page that made it. We keep only a one-way hash of it, so nobody at Muslim.Blue can read your key back.
• Send your key in the X-Api-Key header. Never put it in a web address, in code anyone can read, or in an app where it can be copied out. Anyone with your key can use your limits.
• One person may hold up to 5 keys at once, and make or rotate up to 10 in a day. Use one key for each app or site, so you can rotate one without breaking the others.
• Rotating a key gives it a new secret at once, and the old secret stops working on the next request. If a key leaks, rotate it right away.
• You are responsible for what is done with your keys.

Limits

• A key allows 60 requests a minute and 10,000 a day, counted by the day in UTC.
• Without a key, one network address may make 60 requests a minute and 2,500 a day that reach our servers. Answers from our cache do not count.
• An answer of "not changed" (304), which you get by sending back an ETag, never counts toward your day.
• We may give a key other limits, for example for a masjid's own site or an app many people use. Write to us to ask.
• Please do not get around a limit, for example with many keys or many network addresses for one app.

Showing the times honestly

People pray by these times, so please take care with them.

• Every answer about a masjid's times says whether they are the masjid's own published times or calculated times. A masjid that has not published its times on Muslim.Blue answers calculated adhan times with no iqamah, and a notice saying so.
• Answers from the calculator are always marked as calculated.
• Wherever you show calculated times, say they are calculated. Never present them, or times you changed, as a masjid's own.
• The moment a masjid publishes its own times, the same addresses answer them, and we clear our cached copies. Ask again at least daily, so your users see what the masjid published.
• Each masjid announces its own Ramadan, Eid and Jumu'ah. A calculated Hijri date may differ from the date a masjid follows by local sighting.
• Do not suggest that a masjid, or Muslim.Blue, endorses your app or site. Use a masjid's name, logo and colors only to show which masjid the times are for.

Credit for OpenStreetMap data

Some masjid listings are made from OpenStreetMap, which is open data under the Open Database License (ODbL). Every answer about such a masjid carries the credit in an X-Data-Attribution header, with a Link header to the license. A masjid's day and month answers also carry it in an "attribution" list, and its calendar feed carries it in the calendar's description. Wherever you show those facts, or anything worked out from them, such as calculated times at that masjid's map point, show this credit where people can see it:

Contains information from OpenStreetMap, © OpenStreetMap contributors, available under the Open Database License (ODbL). Link the words to openstreetmap.org/copyright.

If you make a database from those facts and share it with anyone, the ODbL asks you to share that database under the same license.

If you keep listings made from OpenStreetMap, keep them apart from your other data, as we do, and offer them under the ODbL to anyone who asks for them.

What you may build

You may use the API in your own apps, websites, screens and tools, and show its answers to your users, as these terms allow.

You may use the API in free apps and sites only. To use it in an app or site people pay for, you need our written permission first; write to developers@muslim.blue to ask. This limit does not change what the ODbL lets you do with listings made from OpenStreetMap.

Please do not:

1. Show calculated times as a masjid's own, or remove the word that marks them as calculated.
2. Use the contact details in a masjid's listing to send it messages it did not ask for, or to sell to it.
3. Copy the API in bulk beyond what your app needs, or get around a limit or a cache.
4. Probe, scan or overload the API, or use it to break any law.
5. Share a key in public, or give it to someone else to use.

What we keep about your use

• For each key, we count its requests, its "not changed" answers and its refusals for a limit, by the day, and delete the counts after 90 days. We do not keep the addresses you asked for, your network address or your query with those counts.
• To keep the limits without a key, we count requests per network address, kept only as a keyed hash of it, never the address itself.
• Your keys and their counts are deleted when your Muslim Colors account is deleted.
• Our Privacy Notice says more about what Muslim.Blue keeps and the choices you have.

When we may turn off a key

We may block a key that breaks these terms, puts the API at risk, or was shared in public, and we record why. While a key of yours is blocked, you cannot make or rotate keys. You can turn off your own keys at any time on the developer page.

We may block a key, or end your use of the API, at any time, for any reason, and without notice. Where we can, we tell you that we did, but we do not owe you a reason or a second look.

Changes to the API and to these terms

We may add to the API at any time. The docs and the OpenAPI document always describe the API as it is.

We may change the API in a way that breaks existing apps, or end it, at any time, and we say so on the docs page. When we can, we also email the holders of active keys before we change the API in a way that breaks apps, or end it. When we turn off a key, now or on a day we set, we may email its holder first or at the time, and we keep a record of each notice we send.

When we change these terms, we post the new version here with what changed. Using the API after a change means you agree to the new version.

Promises and limits

The API is free. We work to keep it running and its times right, but prayer times are worked out by calculation, and iqamah, Ramadan and Eid are each masjid's own decision. For anything that matters, check with the masjid.

The API is provided as is and as available, without warranties of any kind, to the extent the law allows.

To the extent the law allows, we are not liable for any loss that comes from using the API. Where a court holds that we must be liable for some amount anyway, our total liability to you for the API is no more than 100 US dollars.

Our Terms of Use's section on disagreements and the law that applies covers the API too: the same law, the same arbitration and the same limits apply to a disagreement about the API.

Contact us

For a question about the API, other limits for a key, or a key you think was misused, write to developers@muslim.blue.