Skip to main content
Version: Next

Release Notes

Version 1.1.0​

Released April 2026

New Features​

Service-Level Assertion Checks (API)​

When sending a request using the Esri Map Service or Esri Feature Service service type, Quetzly now automatically runs a suite of service-level checks and displays the results in a new Assertions tab in the response panel.

Checks include verifying the service is reachable, that layers and tables are defined, that the spatial reference is consistent with the extent coordinates, and that feature layers contain data. For Map Services, a live map export is also tested. See Assertion Checks for the full list.

Service-Level Assertions in Monitoring​

The Monitor section now has an Enable Assertions toggle next to the Add button. When enabled (on by default), adding an ArcGIS Map Service or Feature Service endpoint also runs the full assertion suite. The status column in the monitor table now shows:

  • 🟢 All checks passed
  • ⚠️ Non-critical failures detected
  • 🔴 Critical failure (no layers, unreachable, bad status)

Hovering over the status icon shows a detailed tooltip breaking down every passed and failed check. See Assertion Checks for details.

GIS Service Health Report (New Section)​

A new Report section has been added to the sidebar. Enter an ArcGIS Server root URL and click Run to automatically discover all services across all folders and run assertion checks on every one. Results are presented as:

  • Summary cards (total services, health score, critical outages, avg response time)
  • A health donut chart and service-type bar chart
  • A sortable, filterable table of every service with status icons and failure details
  • Click any service name in the table to open it directly in the API section

Reports can be exported as a PDF. See Reporting for details.

Save URLs Directly to a Set​

The Sets section now includes a text area where you can paste one or more service URLs (one per line) and save them as a named set — without needing to have any layers loaded on the map first. The saved set appears immediately in the Sets list and each URL can be clicked to load it into the API section. See Adding Service URLs Directly for details.

Version 1.0.0​

Initial release

  • API section for sending requests to JSON, WMS, WFS, Esri Map Service, and Esri Feature Service endpoints
  • Map visualization with OpenLayers for geospatial responses
  • Request history with open, re-send, and download actions
  • Sets for saving, exporting, and importing collections of API requests
  • Automated endpoint monitoring with configurable check intervals
  • Request and response inspection (status, headers, body, layers)