There shall be a service consumption constraint to ensure that a service consumer does not impose undue loads on computer and network resources, for example, by polling it at a higher frequency than the status is normally provided.
SERVICE_CONSUMPTION_CONSTRAINT
Usage is limited as per our Throttling standard policies.
Limited to either:
200 requests per day per unique user.
or
1000 requests per day per unique user.
The API makes use of standard HTTP headers, as specified in the SWIM Yellow Profile, WS Light Service Interface Binding.
Consumers needs to subscribe for the service by contacting the DWD before data can be received.
<p>According to ICAO Annex 3 the meteorological information is retained for a period of at least 30 days from the date of issue. This relates to the information itself and not the request time of the customer!</p>
Consumers needs to subscribe for the service by contacting the DWD before data can be received.
<p>According to ICAO Annex 3 the meteorological information is retained for a period of at least 30 days from the date of issue. This relates to the information itself and not the request time of the customer!</p>
Consumers needs to subscribe for the service by contacting the DWD before data can be received.
<p>According to ICAO Annex 3 the meteorological information is retained for a period of at least 30 days from the date of issue. This relates to the information itself and not the request time of the customer!</p>
Consumers needs to subscribe for the service by contacting the DWD before data can be received.