"See bottom for general descriptive information. --- # Releases ## [1.9.0] 2025-12-17 ### Add parameterization to auth requests * authorization URL now defined by variable set for environment ## [1.7.3] 2025-06-05 ### Add constraints to temporal parameter values * make request fail if parameter is set to something that would obviously not correspond to available data * are sanity checks, as still possible to specify time values for which data cannot be provided ## [1.3.0] 2025-02-03 ### Completely revamp PIREPs endpoint functionality from only returning PIREPs for single station to allowing to use various parameters to allow more thorough selection capabilities as with like METARs and TAFs... * spatial filters * including bounding box, polygon, circle, corridor * distance units for circle, corridor * SRID for points * temporal filters * from datetime * until datetime * data filters * Boolean for inclusion of geometry in output * aircraft types * aircraft sizes * Navaid Ids * minimum/maximum flight level * minimum/maximum turbulence score * minimum/maximum icing score * unit system for response ### Add new parameter handling to select by insert time... * inserted after datetime * inserted through datetime ### Documentation updates ## [1.0.1] 2024-04-30 ### Add PIREP API docs ## [1.0.0] 2024-04-26 ### Add PIREP API --- # PIREP API information _last updated for v1.3.0_ PIREPs are considered valid beginning with their reported time. Records become no longer available for requests about 3 hours after their report times. See documentation for complete request parameter definitions. Response data is in GeoJSON format. See Postman collection for description of properties in response feature objects. Many data fields frequently have no content for any given report and are removed from response objects when that is the case. See Postman collection for details. Values with units are provided in either \"default\" (mostly, but not all, imperial) or \"metric\" system. See documentation or Postman collection for details. ## Spatial filters These allows to select data within a specific area. Only one may be used per request. * Bounding box - Defines rectangular area set by furthest southwest location and furthest northeast location. * Polygon - Defines area enclosed by series of points. Response behavior is unpredictable if created shape is self-interesting other than last point matching first point. * Circle - Defines area from center point and radius. The larger the defined area, the more its shape on projected map will differ from true circle on spherical coordinates. Constraint is set to limit radius and thus circle size. Request will fail or have unpredictable response behavior if circle area crosses the antimeridian (180W/180E longitude). * Corridor - Defines area from series of points defining a (not necessarily straight) line and halfwidth that tells distance from line to encompass. Constraint is set to limit halfwidth, though line length not limited. However response behavior is unpredictable for long distances between points. Request will fail or have unpredictable response behavior if corridor area crosses the antimeridian (180W/180E longitude). ## Temporal filters These allow to select based on time-related characteristics on data. Parameters can limit responses to data valid at a particular time or within a timeframe, ingested/saved within a timeframe, and for data from forecast models corresponding to specific model run times. * valid at - Allows to specify an exact time to limit to data valid then. * from/until - Allows to set a timeframe to limit to data whose valid periods overlap at all with that timeframe. * inserted after/through - Allows to set a timeframe to limit to data ingested/saved at some time within that period. This is useful for chaining requests to continually acquire newly available data, like by setting the \"after\" time as the latest insert time seen from a previous request and the \"through\" time as the current time. "