![]() ![]() In order to save this token to the environment variable SitecoreIdToken, click on the tab called “Tests” and add Now if you have correctly updated your environment, clicking on Send should get a new token from Sitecore. Make sure you add the parameters in Body/Form-encode It is created in the list of collections.Ĭreate a folder “Sitecore” right under it.Īnd create a New Request called GetToken under the Sitecore folder.Ĭhange the method, URL, Headers and Body for this GetToken request as they appear in Postman Name your new collection “Authentication”. While the menu Collections is highlighted, click on the side menu and choose “New Collection” ![]() Let’s create a new collection called Authentication, and as it should be in Sitecore’s own postman collection, we’ll have a folder Sitecode and a request called “GetToken”. You can also download my own version here. ![]() I got a message “Failed to Import”.Īs this one is fairy important to have in our environment, let’s create it manually. Click on Collections and choose “Import” in the menu.ĬatalogAPISamples and CartAPISamples are the one that I tested and they imported without problem.īut Authentication.postman_collection didn’t work. ![]() We can also import Collections the same way. Here I chose to import “Habitat Environment.postman_environment.json” To import an environment file, click on “Env”, then on the menu (the three horizontal lines under “Env”) and choose “Import”. How can I use XC Postman collections in Thunder Client ?īasically, you can import Environments and Collections the same way you did with Postman, with the same files provided by Sitecore in Sitecore Commerce Engine SDK It looks like the authors of this extension tried to mimick the way we use to work in Postman, as we have the same concepts of Collections and Environments. The resultat of the installation is a new circle icon in the list of extensions. Easy to install, just search for it in the Marketplace, or install it from its website The solution is a Visual Code Extension called Thunder Client. It looks like that, unlike U2, I have now found what I’m looking for ? And for years I have been tired of this memory-hungry elephant where I just needed a simple REST client. The transformer also provides a Command line API to normalize collections for full forward compatibility.For years I have been using Postman in order to get information about my XC environments and data. Var transformer = require ( 'postman-collection-transformer' ), objectToConvert = ) Normalizing v1 collections If you'd rather use the transformer as a library: w, -overwrite Overwrite the output file if it exists retain-ids Retain the request and folder IDs during conversion (collection ID is always retained) p, -output-version required version to which the collection is needed to be converted to o, -output target file path where the converted collection will be written j, -input-version the version of the input collection format standard (v1 or v2) i, -input path to the input postman collection file The transformer provides a Command line API to convert collections.Įxample: $ postman-collection-transformer convert \Īll options: $ postman-collection-transformer convert -hĬonvert Postman Collection from one format to another The formats are documented at Installationįor CLI usage: $ npm install -g postman-collection-transformerĪs a library: $ npm install -save postman-collection-transformer Perform rapid conversion of JSON structure between Postman Collection Format v1 and v2. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |