Mixing
How to set environment variable while posting data to API in Postman
I have few APIs which uses a variable instance with values as dev, test and prod. These values are used in the variable so that the API remains the same and the data can be posted to different environments like dev, test, prod. These APIs are deployed on azure platform
I am using postman to publish data to the API. I have created an environment variable and set its value as dev. I want to know where in the api url I should include this variable in order to successfully send the data.
API Url:
https://ashtechdev.azurewebsites.net/tempdata
api postman
asked Nov 20 '18 at 14:56
S AndrewS Andrew
719937
add a comment |
I have few APIs which uses a variable instance with values as dev, test and prod. These values are used in the variable so that the API remains the same and the data can be posted to different environments like dev, test, prod. These APIs are deployed on azure platform
I am using postman to publish data to the API. I have created an environment variable and set its value as dev. I want to know where in the api url I should include this variable in order to successfully send the data.
API Url:
https://ashtechdev.azurewebsites.net/tempdata
api postman
asked Nov 20 '18 at 14:56
S AndrewS Andrew
719937
I think that's a bad idea. What will stop your users from changing the environment on their own? You should have a separate deployment for each environment, and in POSTMAN you would call different URLs using Variables.
– Hubert Jarema
Nov 20 '18 at 15:00
@HubertJarema You mean separate API URL for each environment.?
– S Andrew
Nov 20 '18 at 15:01
Yes. Then you can lock out other environments from public access. You also specify different configurations per each environment based on your deployment location etc. If you pass in your configuration in the URL, anyone who will figure out you're doing it, will be able to switch the environment. Also, when you make a deployment to development, you'll be making a deployment to production at the same time - not ideal. How would you catch errors before production?
– Hubert Jarema
Nov 20 '18 at 16:10
add a comment |
I have few APIs which uses a variable instance with values as dev, test and prod. These values are used in the variable so that the API remains the same and the data can be posted to different environments like dev, test, prod. These APIs are deployed on azure platform
I am using postman to publish data to the API. I have created an environment variable and set its value as dev. I want to know where in the api url I should include this variable in order to successfully send the data.
API Url:
https://ashtechdev.azurewebsites.net/tempdata
api postman
asked Nov 20 '18 at 14:56
S AndrewS Andrew
719937
I have few APIs which uses a variable instance with values as dev, test and prod. These values are used in the variable so that the API remains the same and the data can be posted to different environments like dev, test, prod. These APIs are deployed on azure platform
I am using postman to publish data to the API. I have created an environment variable and set its value as dev. I want to know where in the api url I should include this variable in order to successfully send the data.
API Url:
https://ashtechdev.azurewebsites.net/tempdata
api postman
api postman
asked Nov 20 '18 at 14:56
S AndrewS Andrew
719937
asked Nov 20 '18 at 14:56
S AndrewS Andrew
719937
asked Nov 20 '18 at 14:56
S AndrewS Andrew
719937
asked Nov 20 '18 at 14:56
S AndrewS Andrew
719937
asked Nov 20 '18 at 14:56
S AndrewS Andrew
719937
719937
I think that's a bad idea. What will stop your users from changing the environment on their own? You should have a separate deployment for each environment, and in POSTMAN you would call different URLs using Variables.
– Hubert Jarema
Nov 20 '18 at 15:00
@HubertJarema You mean separate API URL for each environment.?
– S Andrew
Nov 20 '18 at 15:01
Yes. Then you can lock out other environments from public access. You also specify different configurations per each environment based on your deployment location etc. If you pass in your configuration in the URL, anyone who will figure out you're doing it, will be able to switch the environment. Also, when you make a deployment to development, you'll be making a deployment to production at the same time - not ideal. How would you catch errors before production?
– Hubert Jarema
Nov 20 '18 at 16:10
add a comment |
I think that's a bad idea. What will stop your users from changing the environment on their own? You should have a separate deployment for each environment, and in POSTMAN you would call different URLs using Variables.
– Hubert Jarema
Nov 20 '18 at 15:00
@HubertJarema You mean separate API URL for each environment.?
– S Andrew
Nov 20 '18 at 15:01
Yes. Then you can lock out other environments from public access. You also specify different configurations per each environment based on your deployment location etc. If you pass in your configuration in the URL, anyone who will figure out you're doing it, will be able to switch the environment. Also, when you make a deployment to development, you'll be making a deployment to production at the same time - not ideal. How would you catch errors before production?
– Hubert Jarema
Nov 20 '18 at 16:10
I think that's a bad idea. What will stop your users from changing the environment on their own? You should have a separate deployment for each environment, and in POSTMAN you would call different URLs using Variables.
– Hubert Jarema
Nov 20 '18 at 15:00
I think that's a bad idea. What will stop your users from changing the environment on their own? You should have a separate deployment for each environment, and in POSTMAN you would call different URLs using Variables.
– Hubert Jarema
Nov 20 '18 at 15:00
@HubertJarema You mean separate API URL for each environment.?
– S Andrew
Nov 20 '18 at 15:01
@HubertJarema You mean separate API URL for each environment.?
– S Andrew
Nov 20 '18 at 15:01
Yes. Then you can lock out other environments from public access. You also specify different configurations per each environment based on your deployment location etc. If you pass in your configuration in the URL, anyone who will figure out you're doing it, will be able to switch the environment. Also, when you make a deployment to development, you'll be making a deployment to production at the same time - not ideal. How would you catch errors before production?
– Hubert Jarema
Nov 20 '18 at 16:10
Yes. Then you can lock out other environments from public access. You also specify different configurations per each environment based on your deployment location etc. If you pass in your configuration in the URL, anyone who will figure out you're doing it, will be able to switch the environment. Also, when you make a deployment to development, you'll be making a deployment to production at the same time - not ideal. How would you catch errors before production?
– Hubert Jarema
Nov 20 '18 at 16:10
add a comment |
1 Answer
1
active
oldest
votes
I have posted my answer here in this below link. Please use the same.
Hope this helps.
answered Nov 21 '18 at 11:22
Sobhit SharmaSobhit Sharma
64111
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53395722%2fhow-to-set-environment-variable-while-posting-data-to-api-in-postman%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have posted my answer here in this below link. Please use the same.
Hope this helps.
answered Nov 21 '18 at 11:22
Sobhit SharmaSobhit Sharma
64111
add a comment |
I have posted my answer here in this below link. Please use the same.
Hope this helps.
answered Nov 21 '18 at 11:22
Sobhit SharmaSobhit Sharma
64111
add a comment |
I have posted my answer here in this below link. Please use the same.
Hope this helps.
answered Nov 21 '18 at 11:22
Sobhit SharmaSobhit Sharma
64111
I have posted my answer here in this below link. Please use the same.
Hope this helps.
answered Nov 21 '18 at 11:22
Sobhit SharmaSobhit Sharma
64111
answered Nov 21 '18 at 11:22
Sobhit SharmaSobhit Sharma
64111
answered Nov 21 '18 at 11:22
Sobhit SharmaSobhit Sharma
64111
answered Nov 21 '18 at 11:22
Sobhit SharmaSobhit Sharma
64111
64111
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53395722%2fhow-to-set-environment-variable-while-posting-data-to-api-in-postman%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I think that's a bad idea. What will stop your users from changing the environment on their own? You should have a separate deployment for each environment, and in POSTMAN you would call different URLs using Variables.
– Hubert Jarema
Nov 20 '18 at 15:00
@HubertJarema You mean separate API URL for each environment.?
– S Andrew
Nov 20 '18 at 15:01
Yes. Then you can lock out other environments from public access. You also specify different configurations per each environment based on your deployment location etc. If you pass in your configuration in the URL, anyone who will figure out you're doing it, will be able to switch the environment. Also, when you make a deployment to development, you'll be making a deployment to production at the same time - not ideal. How would you catch errors before production?
– Hubert Jarema
Nov 20 '18 at 16:10