Postman 9.3.1 Download

[Hilary Laite]

Idid have an earlier (unknown) version of Postman working and at some point it stopped working. Since then I have uninstalled/reinstalled many times. During installation process the install screen displays very quickly then nothing.

When I launch Postman nothing happens aside from the cursor briefly changing to indicate something is processing. Checking Task Manager Postman does sometimes appear under Background Processes for less then a second then disappears.

Would you be able to share the App Startup Logs from view > Developer > View Logs(.zip folder), Network Logs from View > Developer > Show DevTools (Current View) and View > Developer > Show DevTools (Shared) and send them to he...@getpostman.com?

Hi,

I am having the issue to open the postman desktop from Windows 10. I had followed the instruction -us/articles/360025359014-Troubleshooting-steps-for-Postman-desktop-issues to remove all postman local files from AppData\Local\Postman and AppData\Roaming\Postman. And reinstalled the Postman-win64-8.12.5-Setup.exe. However, I still not able to open the postman desktop. Any suggestion? Thanks.

One more note, none of my coworkers had the same problem. I was the only one with data loss. We are on the same OS, but not sure about the exact version of postman. But I was the only one stupid enough to not have a backup of some type.

I am trying to get some experience with calling meraki api from powershell. I've been through a few of the tutorial articles but I can't seem to get anything working. I'm currently looking at this reference -postman-collection-getting-started/

When I try the first call for List Organizations This User Has Access To I don't get a list of organizations as indicated in step 9. Instead I get an HTML page and if I click the Preview link I can see that it is a login page

I'm confused about what I'm doing wrong. I thought the point of the api key is that it supplies the credentials. I don't see anything in the documentation about passing login information. I'm sure I'm missing something that is so completely obvious that it is not included in the instructions but I can't figure it out.

For my learning and exploration I"m trying to work with the api key provided in the tutorial article I linked above. I'm not able to get a basic call and return in postman so I haven't pushed forward with powershell yet. In fact I started with powershell but just kept getting 404 errors

This led me to try working with postman so I could more easily understand the return. That's when I realized that I'm clearly not working with the api key correctly. At this point I am just confused about where I went wrong. The tutorial article is pretty simple and straight forward but I can't seem to get the same results with the provided key.

Thanks Philip! I don't know what I was doing wrong but I wound up restarting and reconfiguring everything from scratch and I can now make successful api calls using the api key from the article and I have them working in powerhsell now as well.

Lastly, I read your comments about storing api keys in an include file. I'm still not super comfortable about having an administrative api key in plain text anywhere. Do you have any other thoughts on best practices for api key management?

But I'm wondering if I'm just not understanding the intent of the tutorial. I'm trying to work with the provided api key rather than generating an api key for our network. I had the impression that I could work out code examples using the test api key before trying to run calls directly against our organization. Is that possible? Am I misunderstanding? When I follow the steps in the tutorial and hit send I just get HTML as a response and when I click preview I get the Dashboard login message below. Do I need to establish a VPN connection for this to work?

Your environment will still need the X-Cisco-Meraki-API-Key defined, as you have done. Just be sure you are using the API key you have intended (initial vs current). This can be verified after you run the request as well (see image)

Thank you to everyone who replied offering help! I don't know what my initial problem is but I suspect that I just didn't have postman configured correctly. When I uninstalled everything and then set it up again from scratch it started working as expected. I then managed to mess up part of the collection by editing the Get string on one of the calls and I couldn't get it to go back to the default. So I then tried deleting the Meraki collection thinking I could add it back in again but was then unable to get the open in postman link to work again! I wound up going to an old IE browser and that let me install the collection again. Now I'm being very cautious about changing anything in postman but it is working to help me test the calls. Now that I've got that going I'm having no problem making calls form Powershell and I'm loving how easy it is to get the results that I want through api calls. I did create a read only api key for our organization and I can audit firewall rules across all of our networks which is what got me wanting to understand how to work with the api in the first place.

Grpc supports discovery endpoint (its called reflection service) and its standardized. Instead of uploading and keeping proto files in sync, it would be great to be able to provide just the URL of the grpc service that implements reflection protocol.

Glad to see this support, are there any plans to leverage comments in the protocol buffers themselves in the Postman UI versus having to add documentation separately in Postman? e.g. have them show up next to field names when creating a request, or show the protocol buffer service level comment as an API summary. Thanks!

After the first time I specify the local proto file to import into postman, it works fine. Bug when I change the proto file in my later dev work , for example add more parameter to a method, I want Postman auto watch the protofile and refresh the lastest version of proto defination file , but now I has to reconfigure the path again, hope to provide this feature. The Grpc Invoke feature is Awesome!

No, I have to select each stupid collection, right-click, select delete, wait, click okay. Repeat twenty times. And guess what, if the re-import does it separately again. I have to do it ALL over again. Good-bye afternoon worth of time wasted.

which is the best upgrade package for GRPC. I want to add full collections with each request using a proto which converts into a API. i think the sutomation package would be most helpful long term. but require to add multiple protos on one workspace in a single collection. at present it states this account is limited to 3 APIs. please can you advise

Thanks for your reply @voracityemail , I ended up using collection provided here GitHub - uglyeoin/companies_house_api__postman: JSON Import file for the companies house API. Test the companies house API with no knowledge other than something like your company number. You will need to replace all of the variables within the API to your own variables. and it worked for me.

I am going to go out on a limb and assume that everybody here is already aware of the tool Postman. I was thinking that it would be really helpful if a postman collection full of example and REST api examples was available for users to download from downloads. Or even in this community board. Just my two cents.

Any updates on this, we tried following the document :- -started-with-wapis-using-postman/. We can only login to the Infoblox reporting applinace. we were unable to fetch any reports from the reporting server or create any reports using the postman or any other means of API.

I've created a Postman request collection of all the API's in the API documentation for Airwave and I figured I would share with anyone interested! Below is a tutorial on how to import the collection and a brief overview of all of the requests in the collection and descriptions of most of their outputs (I got tired of writing everything out mid-way through). Let me know if you have any questions, comments, ideas, or would like me to explain anything further.

Airwave Appliance - Virtual or HW - I used v8.2.9.1 but this will still work on older versions. Just check the API documentation on your version by navigating to your appliance and appending "/api" to the end. location-of-your-airwave/api

My Postman workspace assumes an admin account named "apiadmin" with password "Aruba123!" exists and assumes no security or obscurity in the login script. Feel free to change or harden as desired/required for your environment.

Then from the "Manage Environments" section create two new Globals, one named "host" with the initial and current value of your Airwave server. This global variable is used in all of the connection URL's so you don't have to modify all 36 requests with the location of your appliance. Instead each navigate to "host/" so you only have to change it i one place.

For the second global variable name it "session_token" and leave the initial and current values blank. We'll use this variable to store the unique session token Airwave requires for authentication when we run any POST requests. I'll explain that more in the "AMP: Login" request.

We'll need to run this POST request first in order to get the session cookie and token we need to authenticate us to use any of the other POST requests (it seems like just the cookie is good enough to successfully run GET requests). Per the Airwave 8.2.8 API Guide we see that we need to supply "credential_0" and "credential_1" as username and password respectively. So if you click on the AMP: Login request then click "body" you'll see we're supplying credentials ampadmin/Aruba123! and an optional destination value (that I don't think does anything, but I made it drive to "/api" anyway).

3a8082e126