

You can publish a collection and easily share it with a URL. Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work.

This makes it possible to use Postman for one-off API tasks instead of writing code. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. You can generalize a collection with “collection variables”. Over time you can build up a set of requests and organize them into a “Postman Collection”. You download the desktop app, and build API requests by URL and payload. Postman is an “API development environment”.

For the API reference doc we are using Postman. A public API is only as good as its #documentation. We just launched the Segment Config API (try it out for yourself here) - a set of public REST APIs that enable you to manage your Segment configuration.
