Crosby News Burn Ban API

openapi: 3.2.0
info:
  title: crosbynews.com Burn Ban API
  version: 1.7.0
  description: 'Crosby, Texas community data: current conditions, hourly and 7-day forecast, active alerts, the EPA UV index, and a measured air-quality index (EPA/AirNow monitors, with an Open-Meteo modeled fallback) from the U.S. National Weather Service, EPA/AirNow, and Open-Meteo; river/bayou flood levels; the Atlantic tropical outlook; the Houston Health Department''s measured daily pollen and mold count; the Harris County burn-ban status from the Texas A&M Forest Service; road incidents and lane closures from Houston TranStar; recent local news headlines; and the Crosby ISD school calendar. Public, no authentication.'
  contact:
    url: https://crosbynews.com/
  license:
    name: Public domain (NWS source data)
    url: https://www.weather.gov/disclaimer
servers:
- url: https://crosbynews.com
security: []
tags:
- name: Burn Ban
paths:
  /api/burn-ban:
    get:
      operationId: getBurnBan
      summary: Harris County, TX outdoor-burning ban status from the Texas A&M Forest Service
      parameters:
      - $ref: '#/components/parameters/IfNoneMatch'
      responses:
        '200':
          description: Countywide burn-ban status. Countywide only — no sub-county resolution.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/BurnBan'
        '304':
          $ref: '#/components/responses/NotModified'
        '502':
          description: Burn ban data unavailable
      tags:
      - Burn Ban
components:
  responses:
    NotModified:
      description: Not Modified — the caller's If-None-Match matches the current snapshot, so no body is sent. The ETag is derived from the cache's refresh stamp, so it changes exactly when the payload would.
  parameters:
    IfNoneMatch:
      name: If-None-Match
      in: header
      required: false
      description: A previously returned weak ETag. When it still matches the cached snapshot, the endpoint answers 304 with no body — the cheap way to poll.
      schema:
        type: string
  schemas:
    BurnBan:
      type: object
      description: Countywide outdoor-burning ban status for Harris County, TX (which includes Crosby) from the Texas A&M Forest Service. Countywide only — TFS has no sub-county resolution.
      properties:
        county:
          type: string
          description: Always "Harris".
        source:
          type: string
        status:
          type:
          - string
          - 'null'
          enum:
          - 'Yes'
          - 'No'
          - null
          description: '"Yes" = ban in effect, "No" = no active ban, null = status unavailable from the last check.'
        startDate:
          type:
          - string
          - 'null'
          format: date-time
          description: When the current ban took effect, as reported by TFS; null when there is no active ban.
        statusSince:
          type:
          - string
          - 'null'
          format: date-time
          description: 'When the CURRENT status was first observed by this site. Read it against `trackingSince`: when the two are EQUAL no status change has ever been witnessed, so this is simply when observation began and must not be presented as a transition date. When `statusSince` is later than `trackingSince`, a real change was observed, to within the refresh cadence.'
        trackingSince:
          type:
          - string
          - 'null'
          format: date-time
          description: The first observation ever recorded for this feed.
        lastChecked:
          type:
          - string
          - 'null'
          format: date-time
          description: When we last checked TFS's feed.
        officialUrl:
          type: string
          format: uri
          description: The Texas A&M Forest Service's official burn-ban tracker.