How does OpenUV API work?
The clear sky UV Index at sea level is first calculated from the solar zenith angle (SZA) and from ozone forecast fields and based on a math model firstly published by The National Institute of Water and Atmospheric Research (NIWA) of New Zealand. The raw UV Index then factored by elevation (optional) and sun-to-earth distance.
The ozone level data is based on global near-real-time OMTO3e product from OMI Instrument installed onAURA Satellite, NASA.
What is the difference between OpenUV API and other weather providers?
Our service is focused on real-time UV Index and UV Index Forecast for any location on the Earth. To achieve that we're using the near-real-time ozone levels that makes our UV Index predictions one of the most accurate on the market. If you've ever tried the Forecast.io or OpenWeatherMap APIs for UV Index retrieving (that are great services by the way) you'll instantly notice the difference in data accuracy and global coverage.
How much will it cost me to use the OpenUV API?
By default you have 50 API calls per day for free. For unlimited requests per day we recommend to move to Extended plan that will cost you $15 USD/month for up 15k reqs daily. Payments and billing details processed by Stripe and do not live on OpenUV servers.
Are you load tested?
Yes. This is our Loader.io results for 150 clients/sec or 540,000 reqs/hour. The Service has been built on Node.js, hosted on top of Heroku, mLab and AWS so scalability is not an issue and will be a really good problem to have.
Feeling you need a couple of dedicated API servers for your Enterpriseproject? No problem. Contact us on
Any requests rate limitation?
Yep. 50 reqs per sec from one IP Address.
Why do I need the OpenUV API in my life?
Imagine your current running or fitness app is getting the UV Index forecast. You could notify users about the best time to run, aware them about harmful UV rays and engage users to apply sunscreen. Imagine your weather app where you could alter the clear sky UV Index by clouds absorption that you have from Forecast.io and even apply some area reflection factors. Imagine the Twitter bot that recommend the best UV protection time and sunscreens to users who got sunburn recently. Imagine new Fitbit Ionic sun safety app... The possibilities are endless. Also check our Knowledge Base page for more UV Index ideas.
What is the reason to pay for the OpenUV API?
For sure you could spend 1-2 months to build your own UV Index API, put aside 3-5k$ for decent backend developer, maintain infrastructure for 7-20$ per month, no questions. Or instead you could use our service, add valuable sun safety information to your product within a couple of days, market sun safety features as a factor of differentiation and focus on your primary project's goals. That's all your choose.
How could I contribute to the project?
The best you can do is to build a decent sun safety app so other people could stay protected from the sun and skin cancer. You could also suggest the API to your fellow developers or mention it on your blog or in your app.
Reach us on email@example.com if you have any suggestion or advices how to improve the API.