What do you use today instead of TrackAPI (https://trackapi.uk) (a competitor, a spreadsheet, doing it by hand)? Compared with that, what would make TrackAPI better or worse for you, and what would keep you on your current option? Also say the maximum you would pay per month in USD (0 if nothing).

Orlando Leannonneutral

Right now, we're primarily using a combination of manual checks and a small CI script to keep our OpenAPI files in GitHub aligned with the implementation. The main pain point is the drift that inevitably creeps in. TrackAPI's automated monitoring and classified changes sound promising, especially the email notifications for detected changes. The 'check now' feature could also be useful for immediate validation. Compared to our current process, the automation is the key differentiator. The main drawback would be if it didn't integrate well with our existing GitHub workflow or if the notifications became overwhelming. It's hard to put a price on it without knowing the scale of monitoring offered. I'd be willing to pay up to $20 per month.

Simulated interest: 60/100

Casey Waelchineutral

Currently, we're juggling Postman collections, spreadsheets, and release notes to track API contract changes between staging and release branches. It's a manual process that consumes significant time. TrackAPI could be better if it offered more granular detail on changes and perhaps integrated with our CI/CD pipeline. What would make it worse is if it required a lot of manual setup or didn't provide clear, actionable insights into breaking changes. Our current patchwork is functional, albeit time-consuming, so a new tool needs to demonstrate a clear, substantial improvement to justify switching. I'm not willing to pay for a subscription, so $0 per month.

Simulated interest: 30/100

Lee Kummleneutral

Currently, my team and I manually compare SwaggerHub specifications against ticketed changes before each release. It's a time-consuming and error-prone process. TrackAPI's automated monitoring and email notifications for changes sound appealing, especially the classification of changes into non-breaking, potentially breaking, or breaking. This would certainly improve our release coordination. However, I would need to understand how it integrates with our existing ticketing system and the actual cost. The pricing isn't clear on the page, so I'm unsure about the maximum I'd pay. I'd consider paying up to $50 per month, assuming it streamlines our process significantly.

Simulated interest: 70/100

Anjaneya Khanneutral

Currently, we're managing OpenAPI spec checks manually during code reviews or by doing quick diffs in GitHub. We don't have a dedicated monitoring tool. TrackAPI's automatic monitoring and email notifications sound appealing for keeping our API specs consistent and stable, which is a major pain point for us. However, I'd need to see how it handles multiple APIs and what kind of detailed diffing it provides. We're a lean startup, so if it's straightforward and effective, I might consider paying around $20 per month.

Simulated interest: 60/100

Roberto Monahan-Vonneutral

Currently, we manage our API specs in GitLab and rely on CI jobs and a homegrown diff script, plus a rather unreliable spreadsheet for endpoint ownership. It's a bit of a manual process, honestly. The idea of automated monitoring and classified changes from TrackAPI sounds appealing, especially getting email notifications. My main concern would be how well it integrates with our existing GitLab setup and if it can handle the number of APIs we have across three squads. If it truly simplifies tracking spec changes and reduces the manual effort, it would be a significant improvement. Pricing isn't clear from the page, but I'd consider up to $30 per month.

Simulated interest: 40/100

Sophia Hendrikspositive

Right now, I'm managing API versions and changes across my clients using a personal checklist, which involves a lot of manual tracking. Using something like TrackAPI to automatically monitor OpenAPI specs and notify me of changes sounds incredibly useful. The classified changes feature is particularly appealing as it would save me time trying to decipher the impact of modifications. What would make it better than my current method is the automation itself, eliminating human error. What might make it worse is if it doesn't handle custom OpenAPI extensions well, or if the integration with my existing workflows is clunky. I'd be willing to pay around $20 per month for this service.

Simulated interest: 75/100

Joe Breitenbergneutral

Today, we primarily rely on Apiary for our API specifications and GitHub for version control. We handle spec updates manually, coordinating with engineering and ensuring documentation is current. TrackAPI's promise of automatic monitoring and classified changes for OpenAPI specs sounds interesting. The classification of changes (non-breaking, potentially breaking, breaking) would be a significant improvement over our current process, which often involves manual diffing and interpretation. What it wouldn't do better is integrate directly into our workflow for spec authorship, which Apiary handles. I'd be willing to pay around $50 per month for a service like this, assuming it accurately reflects the number of APIs we need to monitor.

Simulated interest: 70/100

Roxanne Wolfneutral

Currently, my team and I rely on a combination of spreadsheets and manual repo reviews to keep track of OpenAPI changes, which can be quite time-consuming and prone to errors. The prospect of automated monitoring is appealing, especially the feature that classifies changes as non-breaking, potentially breaking, or breaking. However, I'd need to understand more about the integration process and how it fits into our existing CI/CD pipeline. What would be the reporting capabilities beyond email notifications? How often are the checks performed? The current method is cumbersome, so automating this could be a significant improvement if it's reliable and easy to manage. I'm not sure about pricing without more details, but I'd consider paying up to $50 per month if it proves valuable.

Simulated interest: 40/100

Innocente Valerineutral

Currently, my team and I spend a considerable amount of time manually cross-referencing API specifications stored in Confluence and Excel against our live systems. It's a constant, manual effort to ensure they match. TrackAPI's promise of automatic monitoring and notifications for changes is appealing, especially the classification of changes as breaking or non-breaking. That could significantly reduce our reactive work. However, I would need to understand how it integrates with our existing Confluence documentation and what level of detail it provides in the change logs. The pricing is also unclear; I'd need to see specific plans. If it streamlines our process significantly and provides clear, actionable insights, I might consider paying around $30 per month.

Simulated interest: 60/100

Dominik Wypychneutral

Currently, we're managing API spec changes by keeping them in GitHub and using a manual checklist for version tracking. This works, but it's a bit of a juggling act when we're also preparing customer demos. TrackAPI's automated monitoring and email notifications sound like they could definitely streamline that process, especially the classified changes feature which would be very helpful. What I'm not clear on is how it integrates with our existing GitHub workflow – does it sync directly or is it a separate system? If it automates what's currently a manual, albeit lightweight, process, I could see paying around $30 per month.

Simulated interest: 60/100