Member-only story
API-First Development: Build Consistent, Meaningful APIs With Postman
Build strong APIs with Open API Spec and Postman
We live in a truly revolutionary time.
Household items are getting smarter, services assume your behavior (and are usually right!), and things just get done… automatically.
Between AI and ML rapidly getting introduced into our lives, things are progressively getting easier. More convenient. Better.
When my alarm goes off in the morning, I can have it trigger my towel warmer to turn on. By the time I’m done with my shower, I have a nice hot towel to dry off with. How does this happen? Is everything connected?
In a sense, yes.
Just about everything and their grandma has an API (Application Programming Interface) enabling access and control of certain features. With public-facing APIs becoming the norm, standards must be put in place so connecting services together is easy and intuitive.
Let’s discover how you can start bringing consistent APIs to your apps so you can join the revolution.
The Platform
You want a place where you can design, develop, test, and observe all in one. Enter Postman.
Postman handles all components of the API lifecycle, providing a seamless experience for all members of a development team.
Analysts can describe the data shape, developers can build the endpoints and connections to back-end code, QA can verify that responses adhere to the design, technical writers can build beautiful documentation in Markdown, and automation engineers can build complex workflows to test it.
Not to mention, the application allows for full source control and commenting/collaboration on almost every component.
The Objective
When you decide to go API-first, what exactly are you committing to? What gives you the ability to say that?
Think about your consumers for a second — both internal and external. What would they want out of an API?
- Consumability
- Consistency
- Clear documentation
