Weather API in Detail

Weather API is based on HTTP queries, which are sent to Foreca servers. Locations are identified by lat/lon coordinates. Replies are JSON, XML or delimited ASCII raw data, which is language independent.

Customer must relay queries from end users/devices via a central proxy server(s). Foreca will open access to the query interface only for specified proxy server IP address(es). The service also assumes a random distribution of queries, i.e. it is not allowed to use Weather API for batch mode querying of a large number of places in a busy loop. Any batch mode querying should include a 1 s delay between queries (1 QPS), over 10 QPS batch querying accounts may be throttled without advance notice.


Weather data provided

Current conditions: data from the closest relevant weather observation station which has recently reported data

  • If there are no recent observations within 100 km of the given coordinates, current conditions will not be reported
  • Foreca provides complimentary gif/png images for visualization of weather codes
  • Current condition parameters as reported by the station
    • observation station name - e.g. "London Heathrow"
    • distance - distance to the observations station from the chosen location e.g. "8 km NE"
    • observation time - the time the observation was made in local time
    • temperature in Celsius or Fahrenheit
    • feels-like temperature in Celsius or Fahrenheit
    • graphical symbol code - e.g. "d420"
    • wind speed in m/s, knots, km/h or miles/h
    • wind direction (N, NE, E, ...)
    • pressure in hPa, e.g. "1012"
    • relative humidity in percentages, e.g. "87"
    • visibility in meters, e.g. "10000" for 10 km

Detailed short forecasts: contain intra-day details for several time steps

  • Available with one hour, 3-hourly, 6-hourly intervals
  • Foreca provides complimentary gif/png images for visualization of weather codes
  • Recommended forecast length up to two days

Daily overview forecasts: contain summary data for one day

  • Recommended forecast length up to seven days
  • Foreca provides complimentary gif/png images for visualization of weather codes
  • Weather parameters limited to:
    • graphical symbol code
    • min/max temperature in Celsius or Fahrenheit



Weather API can be configured with an additional for-fee GeoLocation feature. Enabling the GeoLocation feature adds an additional name attribute to the weather data replies so that a meaningful location name can be provided for the end-user in addition to the weather data.


How to display attribution?

All products which use any of the Weather API, Weather Map API or other Foreca raw data feed packages must display attribution to Foreca near the weather information by one of the following phrases, or an appropriate translation: "Powered by Foreca", "Weather data provided by Foreca", "Weather data source: Foreca". If possible, the text "Foreca" should be replaced by one of the graphic images available here. See document Foreca logo and attribution requirements for detailed instructions.


Query examples

NOTE: reply parsing must be able to cope with new weather parameters that may appear in the API in the future, i.e. new JSON keys, XML tags or new columns in delimited ASCII.

Daily overview queries

Forecast for the next two days



Short forecast queries

Forecast for the next two hours



Requesting several forecast intervals in one call

It is possible to request for example hourly and daily forecast in one API call. The following request


is responded with hourly forecast for the next 24 hours and daily forecast for the next 5 days.

Using location name to search for weather forecast

Search a location from Foreca location database, for example with term "lond":


Pick the location from the result list and use its "id" to request weather data for the location:


Response interpretation

Be prepared to handle missing current conditions (observations) information, since missing instrumentation or instrument malfunctions may affect data. Any of the parameter values can be missing/empty, and even the entire obs key (in JSON), tag (in XML) or OBSH/OBS rows (in text) can be missing, try lon=0&lat=0 for an example. In case of missing data it is recommended to simply adapt lay-out so that white space is shown instead. Texts like "No data" are often interpreted by end-users as a service malfunction, which is not the case.

The forecast parameters/rows will always be there, so missing value handling does not need to be as robust as with the current conditions. The forecasts can only be missing in the case of real technical problems. 

Required query parameters:

  • lon - the longitude of the location, in decimal degrees
  • lat - the latitude of the location, in decimal degrees


  • id - Foreca location id
  • format - reply format, Each customer is provided a dedicated format name, "json/standardfeed" and "xml/standardfeed" are used as examples above. Custom formats can be created.

Optional query parameters:

  • alt - altitude above sea level in meters, e.g. "2148" for 2148 meters. By default the altitude is estimated from the numerical weather prediction (NWP) model value for the given coordinates, which can cause errors in mountain regions. Providing the actual altitude will enable the Weather API forecast engine to make better temperature predictions in locations with large height variation. On level ground the benefit will be negligible.
  • tempunit - either "C" or "F" for Celsius or Fahrenheit, defaults to Celsius
  • windunit - either "MS", "KTS", "KMH", or "MPH" for m/s, knots, km/h or miles/h, defaults to m/s
  • tz - POSIX formatted time zone string for response time stamps, e.g. "UTC", or "Europe/Helsinki". If not given, time zone is approximated from coordinates, which can result in errors near time zone borders.
  • ftimes - (only standard/premium packages) length/step-interval of the requested forecast in hours, 24h interval switches on the daily overview mode. E.g. "72/24h" returns daily overview for next three days, "48/3h" returns three-hourly forecasts for the next two days, and "12/1h" returns hourly forecasts for the next 12 hours. Recommended intervals are: 1, 3, 6, 24. Maximum forecast length is 10 days. Optionally the time of the first forecast can be given in the ftimes parameter, see below for details (*).

(*) using ftimes query parameter to specify first timestep

There are two formats:

  1. ftimes=length/timestep
  2. ftimes=length/timestep/firststep

Format 1 uses default values for deciding the time of the first forecast. In format 2 the firststep parameter modifies the time of the first forecast. For daily summary forecasts (of type x/24h) it is interpreted as the number of hours before midnight, default is 11. For hourly forecasts it is interpreted as the minimum number of hours from now to the first forecast time step, default is 0. Examples:

  • ftimes=72/24h - Default, 1 pm, i.e. switch the date at 13:00 o'clock
  • ftimes=72/24h/11 - Same as default, switch the date at 13:00 o'clock, 11 hours before midnight
  • ftimes=72/24h/3 - Switch the date at 9 pm (3 hours before midnight)
  • ftimes=72/24h/0 - Switch the date at midnight
  • ftimes=72/24h/-6 - Show yesterday's forecast until 6 am
  • ftimes=12/1h - Default, hourly forecasts twelve hours forwards from now
  • ftimes=12/1h/0 - Same as default, hourly forecasts with first time step zero hours from now
  • ftimes=12/1h/6 - Hourly forecasts for twelve hours, starting six hours from now, i.e. ending 18 hours from now

Please note that the time zone calculation for local time is approximate.

Response parameters:

  • dt - time stamp of the observation/forecast, for daily overview dt contains only the date part. Unless provided in the query parameters, for Weather API forecasts the time zone is an approximation, which may be inaccurate near time zone borders. When using Foreca IDs the time zone is accurate. For observations (the obs tag) the time is always in local time of the observation station.
  • station - observation station name - e.g. "Berlin Tegelhof"
  • dist - distance to the observations station from the given coordinates appended with wind direction in English, e.g. "8 km NE"
  • p - pressure in hPa, e.g. "1012"
  • v - visibility in meters, e.g. "10000" for 10 km
  • t - air temperature (default unit: Celsius)
  • tx - 24h maximum temperature (default unit: Celsius) (daily summary data)
  • tn - 24h minimum temperature (default unit: Celsius) (daily summary data)
  • tf - the so-called feels-like temperature (default unit: Celsius), which is the combined NOAA/NWS 'face only' wind chill index and Rothfusz heat index, which take into account the cooling and heating effects of wind and humidity
  • rh - relative humidity in percentages, range from 0 to 100
  • pp - probability of precipitation in percentages, range from 0 to 100
  • tp - probability of thunder in percentages, range from 0 to 100
  • pr - accumulated precipitation (default unit: millimeters)
  • ws - 10 minute average wind speed (default unit: m/s)
  • wsx - daily maximum of the 10 minute average wind speed (default unit: m/s)
  • wsa - daily average of the 10 minute average wind speed (default unit: m/s)
  • wn - wind direction string, one of: N, NE, E, SE, S, SW, W, NW
  • s - symbol code (see explanations in
  • c - cloudiness, in percentages, range from 0 to 100
  • ca - average cloudiness during the day in percentages, range from 0 to 100
  • sT - symbol code as text, use lang parameter to control output language
  • rise - sun rise time in 24h clock notation in local time
  • set - sun set time in 24h clock notation in local time
  • uv - UV index based on the global ozone forecast model (1-2=low, 3-5=moderate, 6-7=high, 8-10=very high, 11+=extreme) NOTE: max 5 days forecast available
  • dl - day length in minutes

Please note that Weather API may be upgraded with new data in the future. This means that your application must parse the response so that it does not break if the order of the parameters changes, or new parameters appear. 

Pricing principle

Weather API is designed to be flexible in order to give application developer possibility to optimize queries to include only data that is used in the application. I.e. if application uses only short forecasts it is possible to request only short forecasts. Pricing is based on the requested data units.

One data unit is:

  • one forecast time step for one location
  • one observation data for one location
  • one response to name search query



Weather data queried for 8 time steps consumes 8 data units.


For example, query:


The query above consumes 3 data units (1 observation + 2 forecast time steps).

For example, query:


The query above consumes 25 data units (1 observation + 24 forecast time steps).

For example, query:


The query above consumes 1 data unit.


Name search

One location name search response consumes 1 data unit.

Contact Us

For more information, please fill out the form.