I’m relatively new to Postman and API calls but have a decent grasp on how they work. However, I can’t figure out how to handle the Authentication part within LM. I read through the various KB articles but didn’t find a step-by-step which is what I need for this one.
I was able to grab my ID and Key from our portal, but I’m not sure where I put them in Postman. Do I create them as variables and then add them as parameters somehow? I made a Collection for LM, but when I edit it and go to the Authentication area, I’m not sure which item to choose as none seem to let me put in an ID and a Key.
Can anyone help me with how I get this setup?
Ah, I saw that one out there but since it’s from almost 5 years ago, and mentions v1, I wasn’t sure if it was still valid. I’ll give it a go.
Yeah, it’s still valid. Just substitute a 3 for a 1. Here’s the documentation for v3 api. You can also import the json from the top to get all the queries pre-loaded into postman.
Thanks. It seems to be working.
Can I setup the ID/Key variables in the Collection or does that have to be in an Environment? I have two LM portals I use, and have a Collection for each, but the Environment doesn’t seem to be linked to a Collection so I have to always change it.
Can I create a Collection for LM1 and LM2 and put teach set of ID/Key variables in at the collection level? Any reason that won’t work?
The idea is that the collection is independent of the environment. That lets you switch back and forth between environments without having to maintain two separate collections. Separates the action (collection) from the target (environment). But that idea is for people who are doing transactions with one portal at a time.
There are some problems with certain variables. If you are using a variable for something that goes into the calculation of the signature via the pre-request script, it won’t work. Any other variables should work fine.
FWIW: I would not attempt to do the migration through postman. I would test my calls and get everything with each call working the way i want and then script them all together. That’s just me though.
I have been able to use the APIv1 through Postman for awhile, does anyone have successful notes around v3 configuration? I’m interested in using this within Postman and other places because I’m starting some fresh projects and would like to future-proof this as much as possible.
either add v=3 to the query parameters or add a header X-Version = 3. Nothing more complicated. The difference is the response structure.
I did find some things that don’t work with v1. They do with with v=2. Didn't try v=3. Is it best to just use v3 for everything since it’s newer?
The idea is that the collection is independent of the environment. That lets you switch back and forth between environments without having to maintain two separate collections. Separates the action (collection) from the target (environment).
So would I want to create two Environments and one Collection? One for old and one for new since they each have their own url and keys? Then within my Collection I would just need one and could switch between portals by switching the Environment dropdown?