Uploaded November 2019 | Updated September 2026, 2 weeks ago
An API-first approach assumes the design and development of an application programming interface (API) comes before the implementation. Your team begins by creating an interface for their application. After the API is developed, the team relies on this interface to build the rest of the application. By introducing new features as an independent service accessed by API, the rest of the app can be stitched together, along with any other future apps.
Throughout an API’s entire lifecycle, different stakeholders have unique requirements. It’s not just developers who are collaborating on APIs within your organization. In a world where speed-to-market holds a premium, learn how to harness the power of your team to build better APIs within your own organization.
Joyce Lin
Developer Advocate, Postman
twitter.com/PetuniaGray
Check out all our events
fitc.ca
twitter.com/fitc
Save 10% off any FITC event with discount code 'youtube'.
See our upcoming events at fitc.ca
An API-first approach assumes the design and development of an application programming interface (API) comes before the implementation. Your team begins by creating an interface for their application. After the API is developed, the team relies on this interface to build the rest of the application. By introducing new features as an independent service accessed by API, the rest of the app can be stitched together, along with any other future apps.
Throughout an API’s entire lifecycle, different stakeholders have unique requirements. It’s not just developers who are collaborating on APIs within your organization. In a world where speed-to-market holds a premium, learn how to harness the power of your team to build better APIs within your own organization.
Joyce Lin
Developer Advocate, Postman
twitter.com/PetuniaGray
Check out all our events
fitc.ca
twitter.com/fitc
Save 10% off any FITC event with discount code 'youtube'.
See our upcoming events at fitc.ca
