Whenever issues arise, their developers and testers can more easily work together on a resolution. “When we need to show what parameters one can send and what kinds of results one can expect to get back, Postman is the best way for us to collaborate.”Īnd then there are larger teams like VideoAmp, which maintains a Postman workspace as a central hub for cross-team collaboration and information. Postman gives them a way to clearly communicate within their team which parts of other companies’ APIs they are using and how (they also use Postman for their internal APIs). They use Postman to develop their integrations with other tools like Salesforce and QuickBooks. For example, there are small teams like Chiffer-a startup with three engineers building the first subscription intelligence platform to help financial and executive teams get the metrics they need. We love seeing the way our community uses Postman to collaborate. So over the ensuing years, we’ve been working tirelessly to address this need by introducing collections, team, private, and personal workspaces, and more recently, public workspaces to make collaborating on APIs easier. But it soon became clear that that wasn’t enough: APIs are inherently collaborative, and the original Postman product did not explicitly facilitate that collaboration. When I built the first iteration of Postman in 2012, it was designed to help individual developers interact with APIs.
0 kommentar(er)
