Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

An Embeddable 'Run in Postman' Button for Your API

DZone's Guide to

An Embeddable 'Run in Postman' Button for Your API

The API client tool Postman recently debuted an embeddable 'Run in Postman' button which makes API integration even easier. Check out this neat functionality, and what it means for your API dabbling.

· Integration Zone
Free Resource

Share, secure, distribute, control, and monetize your APIs with the platform built with performance, time-to-value, and growth in mind. Free 90-day trial of 3Scale by Red Hat

The popular API client tool Postman just launched an embeddable "run in Postman" button, that you can use to fast-track integration with your API(s). Shortly after I wrote a post about the importance of API definition driven embeddable tools for API service providers, Postman contacted me and said, "hey! we are already working on that!"

With the latest update, when you use your Postman Client, you can generate some embeddable JavaScript, which you can then post alongside your API documentation, throughout your developer portal, or possibly anywhere on the open web. Something that could trim minutes, or even hours off the time it takes for new developers to go from discovery to integration.

Embeddable tooling for APIs is nothing new, something we've seen leading providers like Twitter and Facebook employ successfully, but it is something that is fairly new for API service providers. Having a robust embeddable strategy like this one from Postman, and last week's example from SDK provider APIMATIC, is something all API service providers should be considering in 2016.

Explore the core elements of owning an API strategy and best practices for effective API programs. Download the API Owner's Manual, brought to you by 3Scale by Red Hat

Topics:
rest ,rest api ,tools

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}