…. maybe a good Chrome tool in which to develop API calls
for example, in my current project, right in the SparkPost doc i see …
← one developer communicating effeciently with another
put it in my Dock
#chrome #WebTools #api
#git #gui #api
of course i hesitate to add have a file to stick in the application under a button for a user to execuite it … which i have yet to demonstrate
If you have ever opened the file that is created when you export a collection from within the Postman app, you’d notice that it actually is a JSON file. The file contains all data (and metadata) that is required by Postman to recreate the collection when imported back into Postman. The same file is utilised by Newman to run the collection from command-line.
Instead of sharing complex API documentation, developers could now share collections that exactly outline the web services (along with documentation and tests.)
In the specific project that i am doing now, ‘Project: Sparkpost for Speak To Me Catalog”, that will almost certainly be a php program under speaktomecatalog.com/db called for in the “email mailing procedure for speaktomecatalog”
#btw, i have security concerns about passing that data through a clipboard where it can be composed willy nilly by whomever.
… er, we could maybe learn something from the Star Wars
Collections can be downloaded as a JSON file which you can share with others or shared through your Postman account. You can also share collections anonymously but it is strongly recommended to create a Postman account when uploading collections. This will let you update your existing collection, make it public or delete it later.
of course i have yet to edit specifics for Project: Sparkpost for Speak To Me Catalog into the API calls, but the doc to do it is right there in POSTMAN next to where it needs to be changed.
← Note: that button is really for Chrone only. Clicking on it in FF or Explorere and/or not on a Mac will not work nearly as well and will probably yield a confusion.
si #OMG … it #FuckingWorks
But all of that can be easily rectified by encrypted packages so that the flexibility and intuitive ease of using the clipboard can remain a viable proliferation option.
#OOB transfers are possible too, and technically quite easy, but procedurally very complex, mainly because it would require dual login semantics which is not directly supported by browsers and HTTP protocols … using the clipboard completely gets around the need for synchronized logins on both ends since the login is the normal one already in the browser cookie and is automatically only one login per domain at a time.
Later when the app is tested and working the transactions will be transferred to a program at speaktomecatalog.com with appropriate gated access.