Mayro Najarro

Quetzly - Test, monitor, and visualize your location APIs in one place

Quetzly helps developers, GIS and IT teams test, monitor, and visualize geospatial APIs. Send http requests, adjust headers and query params, and inspect JSON with an integrated editor. Render WMS, WFS, GeoJSON and ArcGIS services on an interactive map, toggle layers, zoom to extents, and export data as GeoJSON or Shapefile. Track endpoint health to reduce downtime and keep location services reliable. Quetzly is currently in open Beta. Try it for free.

Add a comment

Replies

Best
Mayro Najarro
Hi Product Hunt! I'm Mayro Najarro, the creator of Quetzly. As a GIS developer, I was constantly frustrated by having to juggle Postman, a code editor, and a map viewer just to debug a single location API endpoint. It was an inefficient, manual process of copying data back and forth. I built Quetzly to fix that. It's the first desktop API client designed specifically for spatial data and location services. What makes Quetzly different? When you make a request in Quetzly, you don't just get a raw JSON response; you get an instant, interactive map visualization. Here’s what the public beta helps you do: - Instant Map Rendering: Visualize GeoJSON, WMS, WFS, and ArcGIS Feature Services on the fly. - Workflow Efficiency: Ditch the time-consuming export/import dance between different tools. - Automated Monitoring: Set up simple uptime validation checks. I believe that debugging spatial APIs should be as easy as debugging any other API. I'd Love Your Feedback! Quetzly is launching in beta today to get real-world feedback from developers like you. We are eager to hear: - What location APIs are you currently working with (Mapbox, Google Maps, ArcGIS, something else)? - What feature would make this an indispensable tool in your daily workflow? I appreciate you checking us out and trying the beta! — The Quetzly Team
Elior

Congrats on the launch! Love how Quetzly unifies testing, monitoring, and live map visualization for WMS/WFS/GeoJSON into one workflow for geospatial teams.​

Mayro Najarro

@zeiki_yu thank you!

kxbnb

The focus on location APIs specifically is smart - those are notoriously hard to debug when things go wrong (coordinates that look valid but aren't, geocoding edge cases, etc.).

Curious how you handle visualizing failed requests vs successful ones? We've found that seeing the actual request/response payloads is often more useful than just status codes when debugging API issues.

Congrats on the launch!

Mayro Najarro

@kxbnb thanks! Good point. We check for schema validation at the moment. Whether it's valid Geojson or esri json. If not, it doesn't get visualized on the map and the user still gets json response but with a warning. Next step for me is to add some more specific validations like highlighting flipped coordinates and malformed geometry. This is great feedback!