postman-open-technologies / collections Goto Github PK

@Gbahdeyboh I could use a single template collection for building a Twitter thread and be able to post via Twitter API. I have many Twitter threads I want to do, and I want a way to do it with a collection -- so I can copy or fork my template and create new Twitter threads.

This is a request for a Google Chrome extension that will inject a text or image button into the Postman web interface. When the button is clicked it runs a specific collection. This is simply an exploratory exercise to understand different ways collection runs can be embedded into the workspace experience on Postman in the browser. Since almost anything can be run using a collection, including most of the contents in the workspace using the Postman API, or using any other 3rd party API, it opens up endless opportunities for introducing API Lifecycle capabilities into the workspace.

To better understand what is possible, let’s explore:

• Simple Chrome extension that injects a text link into Postman web interface via workspace in a specific location.
• Next, inject a link that runs a specific collection and environment, executing the capabilities present in the collection.
• We will have to figure out how to allow users to manage their Postman API keys using this Chrome extension.
• We will have to figure out the most optimal way to run the collection for the user and communicate the end state.

Let’s experiment with what is possible and report the findings here, opening up this project to the community.

Auth0 has taken interest in joining the Public API Network but do not have an API schema on hand that we can easily import. They've linked us to the documentation they are interested in creating collections for and will be doing further research on providing other files that we may be able to import. I believe their team will be quicker to support a workspace if we created one for them in this case.

Creating this issue to see if we can build out collections for these two documented APIs:

Authentication API
Management API

If I can provide additional assistance or if there are any particular details I should include in future issues, let me know!

We need to gather up as many of the existing collections that we have developed across developer relations, customer org, and other parts of Open Technology. When we find collections we can either add them to the README or share them here as a response to this issue.

There are different tools that help convert different API definition formats to the collection format. GraphQL to collections, OpenAPI to collections, AsyncAPI to collections, etc. All of these toolings help you convert the API definitions in their respective formats to different API requests, variables, headers, etc represented as collections. But that's about all they do. It can be taken even a step further.

The formats that convert to collections have a standard way of representing data(JSON Schema) and this can be greatly leveraged upon. Specifications like GraphQL are declarative in nature, and hence the type of different data points can be inferred.

A library can be built that helps do the following with already generated collection so far its schema can be provided.

• Generate mock responses for requests
• Include sample test cases and events in the collection
• Include a data/schema-driven documentation in the generated collection
• etc

Collections do not provide a way for us to define data schema, but it does provide a way for us to provide user-defined properties which can be leveraged for this use case.

I love the Resource Bot as a single point of automation for Postman knowledge, but I'd like to have it exploded into four separate microbots that do one thing and does it well!

Let's break up the Resource Bot into four separate collections:

• Documentation
• Blog
• Videos

Document each one separately, allowing anyone to fork and use it for just one purpose, applying to their own documentation, blog, or videos.

Once separated we can evolve over time based on others feedback.

We need a default collection for pulling data from a Google Sheet. Providing robust documentation of the steps for how to take any Google Sheet and pull it via the API. Then provide at least a basic HTML listing using Visualizer for the data.

I'd like to have a workspace dedicated to building out a bunch of Airtable-focused collections. Let's start with the workspace, and then add the first collection which is just a basic 101 of connecting to an Airtable base and pulling data, and rendering as a simple HTML table using visualizer. Once done, let's link the workspace and collection here.

I'd like to have a collection that will pull an OpenAPI from the Postman API, add CORS headers:

      headers:
        Access-Control-Allow-Origin:
          type: "string"
        Access-Control-Allow-Methods:
          type: "string"
        Access-Control-Allow-Headers:
          type: "string"

to all of the 2X responses for operations, ensuring they are all CORS enabled at the gateway.

This is largely inspired by Jordan Walsh's Value Map and Arnaud Lauret's Open API mind map. The idea is to build a mind map that can be diagrammatically traversed in a very interactive manner.

We need a collection that will provide as many possible examples of what a collection can do. Starting with a couple of simple examples, but then getting more and more advanced, organizing the different types of collections by folder. Over time we can add more examples, and keep showing the power of collections.

Add Supercharge Your API Development with Utility Collections to the README list - https://blog.postman.com/supercharge-api-development-with-utility-collections/

I'd like to have a collection that will pull a collection from the Postman API, spider all paths and parameters, then output a list of variables used via the visualizer.

Landing page, blog posts, videos, licensing, schema, and other resources that showcase what is possible with a collection, and helps you understand how to put to work.