Skip to main content

​
Windy Weather

This guide explains how to integrate the Windy API into your superun application. The integration uses an Edge Function to securely proxy all API requests, ensuring your API key is never exposed to the client.

​
Documentation

For more details on the Windy API, refer to the official documentation:

​
Environment Variables

Calling the SupabaseEdgeFunctionSecretsCreate tool will open the secrets configuration panel. The plugin_secret_prefix must be SUPERUN. In this panel, you can:
  • Use shared keys — superun provides ready-to-use shared test keys. Check the option to get started quickly without applying for your own keys.
  • Enter your own keys — For production use, enter your own API keys in the input fields.
Required secrets:
  • WINDY_POINT_FORECAST_KEY - Windy Point Forecast API Key
  • WINDY_MAP_FORECAST_KEY - Windy Map Forecast API Key
  • WINDY_WEBCAMS_KEY - Windy Webcams API Key

​
Step 1: Create an Edge Function

Create a Supabase Edge Function to securely proxy Windy API requests. This example shows how to handle different Windy API endpoints:

​
Point Forecast

​
Map Forecast

​
Webcams API

​
Step 2: Frontend Integration

Call the Edge Function directly from the frontend. The API key is securely stored on the server.

​
API Features

The Windy API provides three main services:

​
Point Forecast API

  • Real-time weather conditions for specific coordinates
  • Multi-day forecasts (up to 10 days)
  • Multiple weather parameters (temperature, wind speed, precipitation, etc.)
  • High-resolution weather data (up to 1 km resolution)

​
Map Forecast API

  • Weather data visualization for map overlays
  • Multiple data sources (ECMWF, GFS, etc.)
  • Customizable parameters and models
  • Regional and global coverage

​
Webcams API

  • Nearby webcam locations for visual weather verification
  • Real-time camera feeds
  • Location-based search with radius filtering
  • Weather condition verification

​
Usage Guidelines

When using the Windy API:
  • Respect rate limits and usage quotas
  • Cache weather data appropriately to reduce API calls
  • Handle errors gracefully and provide fallback data when available