blog.postman.com Open in urlscan Pro
35.208.222.22  Public Scan

Form analysis
2 forms found in the DOM

GET /

<form class="form-inline my-lg-0" method="get" action="/"> <label htmlfor="search-lc" class="search-label"> <svg class="nav-search__icon" width="16" height="16" viewBox="0 0 16 16" fill="#6b6b6b" xmlns="http://www.w3.org/2000/svg">
      <path fill-rule="evenodd" clip-rule="evenodd"
        d="M9.87147 9.16437C10.5768 8.30243 11 7.20063 11 6C11 3.23858 8.76142 1 6 1C3.23858 1 1 3.23858 1 6C1 8.76142 3.23858 11 6 11C7.20063 11 8.30243 10.5768 9.16437 9.87147L9.89648 10.6036L9.64648 10.8536L13.5758 14.7829C13.8101 15.0172 14.19 15.0172 14.4243 14.7829L14.7829 14.4243C15.0172 14.19 15.0172 13.8101 14.7829 13.5758L10.8536 9.64648L10.6036 9.89648L9.87147 9.16437ZM6 10C8.20914 10 10 8.20914 10 6C10 3.79086 8.20914 2 6 2C3.79086 2 2 3.79086 2 6C2 8.20914 3.79086 10 6 10Z">
      </path>
    </svg> </label> <input class="form-control" id="search-lc" type="search" placeholder="Search Postman Blog" aria-label="Search" name="s" autocomplete="off" spellcheck="false" dir="auto" value=""></form>

POST https://blog.postman.com/wp-comments-post.php

<form action="https://blog.postman.com/wp-comments-post.php" method="post" id="commentform" class="comment-form" novalidate="">
  <p class="comment-notes"><span id="email-notes">Your email address will not be published.</span> Required fields are marked <span class="required">*</span></p>
  <hr>
  <p class="comment-form-author"><label for="author">Your name</label><br><input class="form-control" id="author" name="author" aria-required="true"></p>
  <p class="comment-form-email"><label for="author">Your email</label><br><input class="form-control" id="email" name="email"></p>
  <div class="comment-form-comment"><label for="author">Write a public comment</label><textarea class="form-control" id="comment" name="comment" aria-required="true"></textarea></div><label class="prompt-comment-subscribe"><input type="checkbox"
      name="prompt_comment_subscribe" value="1">&nbsp;<span class="postmatic-tooltip">Receive replies to your comment via email.<em>Receive replies to your comment via email</em></span></label>
  <p class="form-submit"><input name="submit" type="submit" id="comment-submit" class="submit btn btn__primary" value="Post Comment"> <input type="hidden" name="comment_post_ID" value="13651" id="comment_post_ID"> <input type="hidden"
      name="comment_parent" id="comment_parent" value="0"></p>
  <p style="display: none;"><input type="hidden" id="akismet_comment_nonce" name="akismet_comment_nonce" value="db39853f80"></p><textarea name="ak_hp_textarea" cols="45" rows="8" maxlength="100" style="display: none !important;"></textarea><input
    type="hidden" id="ak_js" name="ak_js" value="1631812761777">
</form>

Text Content

 * Product
   What is Postman? API repository Tools Intelligence Workspaces Integrations
   Get started free →
 * Pricing
 * Enterprise
   Postman Enterprise Enterprise case studies Contact us
 * Resources and support
   
   LEARNING
   
   Docs Webinars Breaking Changes show Postman Space Camp Case studies
   
   COMMUNITY & EVENTS
   
   Blog Community Student program Student Summit Postman Galaxy Postman for
   Nonprofits Postman swag
   
   SUPPORT
   
   Support Center Reseller support Postman status Release notes
 * Explore

Sign In Sign Up Launch Postman
Blog (current)

 * Product Updates
 * Company News
 * Tutorial
 * Postman Culture




THE NEW POSTMAN API PLATFORM: REDEFINING API MANAGEMENT FOR THE API-FIRST WORLD


Tags: API Platform Company News Product Updates

--------------------------------------------------------------------------------

By Abhinav Asthana
September 16, 2021
Reading Time: 7 min.

Today’s consumers need great software. Consumers demand experiences that span
multiple devices, they expect their data to be instantly available, and they
expect everything to work around the clock. There are billions of software
consumers today and there will be many billions more in the future.

To meet this demand, the world of software development has undergone a radical
change in the last decade. Infrastructure is readily available on the cloud
without having to buy and provision hardware. Millions of repositories of open
source code are available in dozens of languages that can be used to build
applications of any nature. The DevOps movement has brought automation to the
process of integration of code and deployment of software to the cloud at rapid
rates. This is still not enough.

Why? Building software is hard! First, no single company, team, or engineer can
build every piece of functionality themselves. And secondly, combining code into
a monolithic application architecture does not scale: you can only fit so many
bits in a single computer and run and deploy them efficiently. Most monolithic
applications very quickly become distributed monoliths where the same
application is deployed multiple times with some configuration to manage which
state runs where. Not to mention the constant risk the architecture runs into
integrating disparate parts and testing them for quality and security.

How can we solve these challenges? Enter APIs.

APIs allow pieces of code to bridge together applications so they can work
cohesively together.



APIs can take many shapes, like internal microservices, data APIs, cloud
services, integration components, SaaS services, and frontend APIs. APIs can be
internal to an organization (private APIs) or external (partner APIs or public
APIs). While public APIs are available to all developers, partner APIs are
typically available to a subset of them through contractual partnerships. What
they all share in common is that they enable compute or data functionality over
the network.

APIs are the building blocks of all modern software.

At Postman, our vision is to build The API-First World. What does this mean for
API Management?


WHAT IS API MANAGEMENT?

API Management arose as a category in the last decade, slightly before the rapid
growth of the cloud, in what we call the “code-first world.” In the code-first
world, developers are focused on building applications by primarily writing code
and optimizing the process from lines of code to bits deployed on a server.

Vendors—most notably Apigee, and later, Mulesoft—understood that many
organizations would like to extend their value propositions through public APIs
just like Salesforce, Google, or Facebook had done.

Many organizations built monolithic applications with a ton of data sitting
around waiting to be harnessed by internal and external developers. To use this
data and maybe offer some external services, organizations deployed gateways
provided by vendors with developer portals (i.e., websites built on a CMS) to
help developers register their APIs. This led to the first wave of public APIs.

The second wave was led by the rise of SaaS applications. The software delivery
model itself shifted from delivering application bits in packaged form to
delivering software over the cloud through the software-as-a-service model. Now
all these applications need APIs to integrate with each other for
business-focused workflows.

Public APIs and integration needs have forced organizations to build APIs, but
due to the lack of tooling and strategy around APIs, most organizations weren’t
able to leverage the full power of APIs.

Gateways did function as a starting point for companies to factor APIs into
their software strategy, but those gateways didn’t help them succeed with the
true power of APIs.

Partner APIs were often not supported in these offerings, and the explosion of
private APIs (e.g., microservices, serverless, internal apps) meant that almost
70-90% of APIs were missing from the API landscape that leaders thought they
had.

Finally, end users (developers, testers, product managers, and several other
functions) didn’t have any tooling support from API Management vendors. With
application development shifting to an API-first mindset, engineering
organizations have learned that they need tooling, enablement, and processes to
build and deliver great APIs.

API Management vendors don’t treat APIs as the building blocks of modern
software.


API-FIRST SUPERPOWERS

From a central vantage point in the industry, Postman has seen the rise of
API-first companies—API-first companies use APIs as the building blocks of their
software strategy.


API-FIRST DEVELOPMENT IS A DEVELOPMENT MODEL IN WHICH APPLICATIONS ARE
CONCEPTUALIZED AND BUILT AS AN INTERCONNECTION OF INTERNAL AND EXTERNAL SERVICES
THROUGH APIS.

API-first companies have superpowers:

 * API-first companies choose technologies that are right for their goals. This
   includes gateways, protocols, languages, and runtimes.
 * API-first companies have a place for discovery for their most important
   digital building block: their APIs.
 * API-first companies have a standardized process for building APIs that meet
   their guidelines and provide a great developer experience for end users.
 * API-first companies understand the complete landscape of their private,
   partner, and public integration points.
 * API-first companies have an ecosystem of partners and third-party developers
   to continuously add more value to their offering.
 * API-first companies understand and control their data to meet regulatory
   challenges.
 * API-first companies understand their API perimeter to prevent malicious
   actors from using APIs in a malicious way.

Becoming API-first requires an evolution of your software development pipeline
all the way to production and your interactions with consumers.


INTRODUCING THE NEXT-GENERATION API PLATFORMS

At Postman, we believe that the transition from code-first to API-first is a
significant technology shift happening in every company today. Companies that
don’t make this transition will be relegated to being niche players in their
businesses, and new kinds of businesses will emerge in this decade to take their
place. To succeed in the API-first world, engineering organizations need a new
category of solutions: API Platforms.


API PLATFORMS ARE SOFTWARE SYSTEMS WITH INTEGRATED TOOLS AND PROCESSES THAT
ALLOW PRODUCERS AND CONSUMERS TO EFFECTIVELY BUILD, MANAGE, PUBLISH, AND CONSUME
APIS.

These platforms have the following components:


#1: TOOLS FOR THE ENTIRE API LIFECYCLE

 1. API client: A developer tool to send API calls during debugging or API
    consumption.
 2. API designing and mocking: API design and mocking capabilities help
    developers and architects define and test the expected behavior of an API
    before investing time in coding.
 3. API testing and automation: Testing of the API through a variety of
    ways—including manual, automated, functional/behavioral, contract,
    performance, security, and others—to ensure that the API behaves as per
    requirements after the coding phase. Testing can be done manually or it can
    be automated as part of a regular build process.
 4. API documentation: Reference guides, how-to documentation, recipes, and
    other means of communication about how an API works.
 5. API monitoring: Operational monitoring of an API to ensure that it is
    behaving as desired and alerting when things go wrong.


#2: COLLABORATION CAPABILITIES FOR PRODUCERS AND CONSUMERS

 1. API workspaces: Collaboration on API-related workflows during development,
    testing, documentation, operations, support, and sales-related workflows.
    API collaboration tools notify stakeholders about changes and help multiple
    participants to work together. API collaboration can be between producers,
    between consumers, or between producers and consumers.
 2. API catalog: A central place for APIs for private, partner, and public APIs.
    The catalog contains up-to-date information about the API and related
    artifacts so producers and consumers can find the right APIs.


#3 GOVERNANCE CAPABILITIES FOR OPERATIONS, ARCHITECTURE, AND SECURITY TEAMS

 1. API security: Preventing unauthorized and malicious access and use of APIs
    through checks during development time, testing, and production. Discovery
    of previously undocumented APIs through scanning applications,
    infrastructure, or any other artifact.
 2. API observability: Measurement of API traffic through sampling or
    aggregating data for use by developers, ops, or product managers.


#4 INTEGRATIONS WITH THE SDLC

These capabilities need to be integrated with the key components that an
organization has:

 1. Source code management
 2. CI/CD
 3. Cloud/on-prem infrastructure (this is where gateways fit in today)
 4. Application performance management

An API platform helps organizations manage the entire API lifecycle from design
to production while also bringing the most critical constituents—the API
consumers—into the API landscape. Not only does the platform help with a single
API but it helps govern the entire API landscape. An API platform in this form
is a core system that an organization should deploy to ensure success with APIs.


THE POSTMAN API PLATFORM LAUNCH

We are excited about today’s platform launch. We believe that it is the best
version of Postman so far in an integrated way that is loved by millions around
the world. Ankit, Postman’s co-founder and CTO, talks about the new platform
capabilities in his blog post here. While we don’t do everything in the API
Platforms category yet, we believe we have the best-in-class integrated
experience that scales from individual developers to organizations with
thousands of people working together.



Postman is already deployed at scale at organizations like Kroger, PayPal,
Cvent, and many other API-first organizations, and we’re excited about bringing
the API-first mindset to many more.


WHAT’S NEXT FOR API PLATFORMS

We see that a lot of organizations (outside of the ones who have adopted
Postman) are building homegrown solutions through expensive developer resources.

Along with homegrown solutions, there are many different vendors in a
dynamically evolving landscape. Lately, we have seen API security vendors like
Salt.security and Noname get funded and new companies like Akita and Moesif
emerge. Some vendors like Stoplight and Apollo are focusing only on one
specification. We have also seen API catalogs and the emergence of open source
solutions like Backstage.

So, what happens to gateways? Gateways were a core component of the last decade
of the API Management category. We believe gateways are an important
infrastructure piece and we will see the emergence of new kinds of gateways. The
last few years have already seen new models on the backs of containers led by
Kubernetes, serverless functions, and service meshes—almost all of it open
source. The challenge with gateway vendors when they do service other parts of
the API-first workflow like API catalogs or API clients is this: they only
integrate with that specific gateway. Unfortunately, organizations deploy many
kinds of gateways depending on the use case each gateway fulfills best.

Here is our view of the landscape today:



Download the API Platform Landscape diagram here

We are excited about leading the conversation around APIs. If you have any
thoughts, comments, or questions, feel free to leave them below or write to us
at help@postman.com or tweet to us at @getpostman or @a85.

+22

--------------------------------------------------------------------------------

Abhinav Asthana

  

Abhinav is the co-founder and CEO at Postman. View all posts by Abhinav Asthana

What do you think about this topic? Tell us in a comment below.




COMMENTS CANCEL REPLY

Your email address will not be published. Required fields are marked *

--------------------------------------------------------------------------------

Your name


Your email


Write a public comment
 Receive replies to your comment via email.Receive replies to your comment via
email





This site uses Akismet to reduce spam. Learn how your comment data is processed.


YOU MIGHT ALSO LIKE:


THE NEW POSTMAN API PLATFORM: ANNOUNCING 6 KEY PLATFORM IMPROVEMENTS

APIs are the building blocks of all modern software. Since the beginning of
Postman, we have been obsessed with helping our users solve problems around
their APIs. Postman started by making it easy for developers to make simple API
calls and verify responses—as well as helping developers test and debug APIs.
Since then, we’ve massively…

Read More →


THE NEW POSTMAN API PLATFORM: INTRODUCING POWERFUL INTEGRATIONS

Ever since we started Postman, our vision has been to streamline API workflows.
We discovered some of these workflows as a result of our own organization’s
growth from a small team of five to more than 400 today, but many more came
about by talking to our global community of Postman users. We launched a…

Read More →


INTRODUCING POSTMAN V8: A WHOLE NEW DESKTOP APP EXPERIENCE

Despite all its challenges, last year was a remarkable one for Postman. We, just
like many of you, faced adversity, but we prevailed to make some massive strides
in 2020: We recently launched Postman on the web, going back to our roots
starting out as a web-based utility (a Chrome extension); we launched the
private…

Read More →
More
 * Continuous API Testing with Postman
 * 10 Tips for Working with Postman Variables
 * Bite-Sized Videos to Level Up Your Postman Game

© 2021 Postman, Inc.


PRODUCT

 * What is Postman?
 * API Respository
 * Tools
 * Intelligence
 * Workspaces
 * Integrations
 * Enterprise
 * Plans and pricing
 * Download the app
 * Support Center


COMPANY

 * About
 * Careers and culture
 * Contact us
 * Press and media


SECURITY AND TERMS

 * Security
 * Privacy policy
 * Terms


SOCIAL

 * Twitter
 * LinkedIn
 * GitHub
 * YouTube
 * Asset 2
   Twitch

© 2021 Postman, Inc.


PRIVACY PREFERENCE CENTER

When you visit any website, it may store or retrieve information on your
browser, mostly in the form of cookies. This information might be about you,
your preferences or your device and is mostly used to make the site work as you
expect it to. The information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies. Click on the
different category headings to find out more and change our default settings.
However, blocking some types of cookies may impact your experience of the site
and the services we are able to offer. More information
Allow All


MANAGE CONSENT PREFERENCES

STRICTLY NECESSARY COOKIES

Always Active

These cookies are necessary for the website to function and cannot be switched
off in our systems. They are usually only set in response to actions made by you
which amount to a request for services, such as setting your privacy
preferences, logging in or filling in forms. You can set your browser to block
or alert you about these cookies, but some parts of the site will not then work.
These cookies do not store any personally identifiable information.

Cookies Details‎

FUNCTIONAL COOKIES

Functional Cookies

These cookies enable the website to provide enhanced functionality and
personalisation. They may be set by us or by third party providers whose
services we have added to our pages. If you do not allow these cookies then some
or all of these services may not function properly.

Cookies Details‎

TARGETING COOKIES

Targeting Cookies

These cookies may be set through our site by our advertising partners. They may
be used by those companies to build a profile of your interests and show you
relevant adverts on other sites. They do not store directly personal
information, but are based on uniquely identifying your browser and internet
device. If you do not allow these cookies, you will experience less targeted
advertising.

Cookies Details‎

PERFORMANCE COOKIES

Performance Cookies

These cookies allow us to count visits and traffic sources so we can measure and
improve the performance of our site. They help us to know which pages are the
most and least popular and see how visitors move around the site. All
information these cookies collect is aggregated and therefore anonymous. If you
do not allow these cookies we will not know when you have visited our site, and
will not be able to monitor its performance.

Cookies Details‎


BACK BUTTON PERFORMANCE COOKIES

Vendor Search Search Icon
Filter Icon

Clear
checkbox label label
Apply Cancel
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label


 * 33ACROSS
   
   HOST DESCRIPTION
   
   VIEW COOKIES
   
   
    * Name
      cookie name

Confirm My Choices


By clicking “Accept All Cookies”, you agree to the storing of cookies on your
device to enhance site navigation, analyze site usage, and assist in our
marketing efforts.

Accept All Cookies

Cookies Settings