API calls to Salesforce from standalone application

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












4















We plan to have an application on an internal server that fetches data from one source, manipulates it, sends it to Salesforce using Rest APIs.



I have some questions:
Do I need to have a connected app?
If so, what is the callback url? I have taken a few trailheads and understand that the callback URL is used for human interaction but this is all automated and I'm not sure that there is a URL as such.










share|improve this question
























  • If you are planning to use REST APIs then Yes, you will need a connected app.

    – Jayant Das
    Jan 4 at 20:44











  • Yes it is REST. (updating post)

    – SeanGorman
    Jan 4 at 20:45












  • The callback URL is used to provide you with an OAuth token. It will be specific to your local application. OAuth does not need to involve user interaction. The JWT flow, for example, does not.

    – David Reed
    Jan 4 at 20:49















4















We plan to have an application on an internal server that fetches data from one source, manipulates it, sends it to Salesforce using Rest APIs.



I have some questions:
Do I need to have a connected app?
If so, what is the callback url? I have taken a few trailheads and understand that the callback URL is used for human interaction but this is all automated and I'm not sure that there is a URL as such.










share|improve this question
























  • If you are planning to use REST APIs then Yes, you will need a connected app.

    – Jayant Das
    Jan 4 at 20:44











  • Yes it is REST. (updating post)

    – SeanGorman
    Jan 4 at 20:45












  • The callback URL is used to provide you with an OAuth token. It will be specific to your local application. OAuth does not need to involve user interaction. The JWT flow, for example, does not.

    – David Reed
    Jan 4 at 20:49













4












4








4








We plan to have an application on an internal server that fetches data from one source, manipulates it, sends it to Salesforce using Rest APIs.



I have some questions:
Do I need to have a connected app?
If so, what is the callback url? I have taken a few trailheads and understand that the callback URL is used for human interaction but this is all automated and I'm not sure that there is a URL as such.










share|improve this question
















We plan to have an application on an internal server that fetches data from one source, manipulates it, sends it to Salesforce using Rest APIs.



I have some questions:
Do I need to have a connected app?
If so, what is the callback url? I have taken a few trailheads and understand that the callback URL is used for human interaction but this is all automated and I'm not sure that there is a URL as such.







api connected-apps






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 4 at 20:45







SeanGorman

















asked Jan 4 at 20:20









SeanGormanSeanGorman

595318




595318












  • If you are planning to use REST APIs then Yes, you will need a connected app.

    – Jayant Das
    Jan 4 at 20:44











  • Yes it is REST. (updating post)

    – SeanGorman
    Jan 4 at 20:45












  • The callback URL is used to provide you with an OAuth token. It will be specific to your local application. OAuth does not need to involve user interaction. The JWT flow, for example, does not.

    – David Reed
    Jan 4 at 20:49

















  • If you are planning to use REST APIs then Yes, you will need a connected app.

    – Jayant Das
    Jan 4 at 20:44











  • Yes it is REST. (updating post)

    – SeanGorman
    Jan 4 at 20:45












  • The callback URL is used to provide you with an OAuth token. It will be specific to your local application. OAuth does not need to involve user interaction. The JWT flow, for example, does not.

    – David Reed
    Jan 4 at 20:49
















If you are planning to use REST APIs then Yes, you will need a connected app.

– Jayant Das
Jan 4 at 20:44





If you are planning to use REST APIs then Yes, you will need a connected app.

– Jayant Das
Jan 4 at 20:44













Yes it is REST. (updating post)

– SeanGorman
Jan 4 at 20:45






Yes it is REST. (updating post)

– SeanGorman
Jan 4 at 20:45














The callback URL is used to provide you with an OAuth token. It will be specific to your local application. OAuth does not need to involve user interaction. The JWT flow, for example, does not.

– David Reed
Jan 4 at 20:49





The callback URL is used to provide you with an OAuth token. It will be specific to your local application. OAuth does not need to involve user interaction. The JWT flow, for example, does not.

– David Reed
Jan 4 at 20:49










1 Answer
1






active

oldest

votes


















4















Do I need to have a connected app?




Yes. If you are using REST API to integrate with Salesforce, then you will need a Connected App.




If so, what is the callback url? I have taken a few trailheads and understand that the callback URL is used for human interaction but this is all automated and I'm not sure that there is a URL as such.




Callback URL is the URL where you want the access token code to be sent to after successful authentication. It can be any URL or even a localhost URL on a specific port. There is not necessarily a human interaction required here. You just need a URL where you can receive the token after the authentication. So if you are authenticating using an API, you can always specify a callback URL pointing back to your application which can programmatically accept the incoming token.



Notice this from the Digging Deeper into OAuth 2.0 in Salesforce documentation (emphasis mine):




Apps that use OAuth can also directly authenticate and access Salesforce resources without a user’s presence.




This is how it is defined here on the documentation:




Enter a Callback URL. Depending on which OAuth flow you use, this is typically the URL that a user’s browser is redirected to after successful authentication. As this URL is used for some OAuth flows to pass an access token, the URL must use secure HTTP (HTTPS) or a custom URI scheme. Separate multiple callback URLs with line breaks.
The callback URL field has a limit of 2000 characters, cumulatively. If you enter several URLs and they exceed this limit, configure another connected app to manage more callback URLs.





You should go through the documentation to get more details on the setup for Connected Apps. Good places to start are:



  • Connected Apps

  • Defining Connected Apps

  • Digging Deeper into OAuth 2.0 in Salesforce





share|improve this answer

























  • Thanks for this. I have read 'most' of these resources but the emphasis seems geared towards human interacted processes.

    – SeanGorman
    Jan 4 at 21:37






  • 1





    I agree. I have struggled on this topic for a long time until I knew what it was.

    – Jayant Das
    Jan 4 at 21:46










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "459"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f245498%2fapi-calls-to-salesforce-from-standalone-application%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









4















Do I need to have a connected app?




Yes. If you are using REST API to integrate with Salesforce, then you will need a Connected App.




If so, what is the callback url? I have taken a few trailheads and understand that the callback URL is used for human interaction but this is all automated and I'm not sure that there is a URL as such.




Callback URL is the URL where you want the access token code to be sent to after successful authentication. It can be any URL or even a localhost URL on a specific port. There is not necessarily a human interaction required here. You just need a URL where you can receive the token after the authentication. So if you are authenticating using an API, you can always specify a callback URL pointing back to your application which can programmatically accept the incoming token.



Notice this from the Digging Deeper into OAuth 2.0 in Salesforce documentation (emphasis mine):




Apps that use OAuth can also directly authenticate and access Salesforce resources without a user’s presence.




This is how it is defined here on the documentation:




Enter a Callback URL. Depending on which OAuth flow you use, this is typically the URL that a user’s browser is redirected to after successful authentication. As this URL is used for some OAuth flows to pass an access token, the URL must use secure HTTP (HTTPS) or a custom URI scheme. Separate multiple callback URLs with line breaks.
The callback URL field has a limit of 2000 characters, cumulatively. If you enter several URLs and they exceed this limit, configure another connected app to manage more callback URLs.





You should go through the documentation to get more details on the setup for Connected Apps. Good places to start are:



  • Connected Apps

  • Defining Connected Apps

  • Digging Deeper into OAuth 2.0 in Salesforce





share|improve this answer

























  • Thanks for this. I have read 'most' of these resources but the emphasis seems geared towards human interacted processes.

    – SeanGorman
    Jan 4 at 21:37






  • 1





    I agree. I have struggled on this topic for a long time until I knew what it was.

    – Jayant Das
    Jan 4 at 21:46















4















Do I need to have a connected app?




Yes. If you are using REST API to integrate with Salesforce, then you will need a Connected App.




If so, what is the callback url? I have taken a few trailheads and understand that the callback URL is used for human interaction but this is all automated and I'm not sure that there is a URL as such.




Callback URL is the URL where you want the access token code to be sent to after successful authentication. It can be any URL or even a localhost URL on a specific port. There is not necessarily a human interaction required here. You just need a URL where you can receive the token after the authentication. So if you are authenticating using an API, you can always specify a callback URL pointing back to your application which can programmatically accept the incoming token.



Notice this from the Digging Deeper into OAuth 2.0 in Salesforce documentation (emphasis mine):




Apps that use OAuth can also directly authenticate and access Salesforce resources without a user’s presence.




This is how it is defined here on the documentation:




Enter a Callback URL. Depending on which OAuth flow you use, this is typically the URL that a user’s browser is redirected to after successful authentication. As this URL is used for some OAuth flows to pass an access token, the URL must use secure HTTP (HTTPS) or a custom URI scheme. Separate multiple callback URLs with line breaks.
The callback URL field has a limit of 2000 characters, cumulatively. If you enter several URLs and they exceed this limit, configure another connected app to manage more callback URLs.





You should go through the documentation to get more details on the setup for Connected Apps. Good places to start are:



  • Connected Apps

  • Defining Connected Apps

  • Digging Deeper into OAuth 2.0 in Salesforce





share|improve this answer

























  • Thanks for this. I have read 'most' of these resources but the emphasis seems geared towards human interacted processes.

    – SeanGorman
    Jan 4 at 21:37






  • 1





    I agree. I have struggled on this topic for a long time until I knew what it was.

    – Jayant Das
    Jan 4 at 21:46













4












4








4








Do I need to have a connected app?




Yes. If you are using REST API to integrate with Salesforce, then you will need a Connected App.




If so, what is the callback url? I have taken a few trailheads and understand that the callback URL is used for human interaction but this is all automated and I'm not sure that there is a URL as such.




Callback URL is the URL where you want the access token code to be sent to after successful authentication. It can be any URL or even a localhost URL on a specific port. There is not necessarily a human interaction required here. You just need a URL where you can receive the token after the authentication. So if you are authenticating using an API, you can always specify a callback URL pointing back to your application which can programmatically accept the incoming token.



Notice this from the Digging Deeper into OAuth 2.0 in Salesforce documentation (emphasis mine):




Apps that use OAuth can also directly authenticate and access Salesforce resources without a user’s presence.




This is how it is defined here on the documentation:




Enter a Callback URL. Depending on which OAuth flow you use, this is typically the URL that a user’s browser is redirected to after successful authentication. As this URL is used for some OAuth flows to pass an access token, the URL must use secure HTTP (HTTPS) or a custom URI scheme. Separate multiple callback URLs with line breaks.
The callback URL field has a limit of 2000 characters, cumulatively. If you enter several URLs and they exceed this limit, configure another connected app to manage more callback URLs.





You should go through the documentation to get more details on the setup for Connected Apps. Good places to start are:



  • Connected Apps

  • Defining Connected Apps

  • Digging Deeper into OAuth 2.0 in Salesforce





share|improve this answer
















Do I need to have a connected app?




Yes. If you are using REST API to integrate with Salesforce, then you will need a Connected App.




If so, what is the callback url? I have taken a few trailheads and understand that the callback URL is used for human interaction but this is all automated and I'm not sure that there is a URL as such.




Callback URL is the URL where you want the access token code to be sent to after successful authentication. It can be any URL or even a localhost URL on a specific port. There is not necessarily a human interaction required here. You just need a URL where you can receive the token after the authentication. So if you are authenticating using an API, you can always specify a callback URL pointing back to your application which can programmatically accept the incoming token.



Notice this from the Digging Deeper into OAuth 2.0 in Salesforce documentation (emphasis mine):




Apps that use OAuth can also directly authenticate and access Salesforce resources without a user’s presence.




This is how it is defined here on the documentation:




Enter a Callback URL. Depending on which OAuth flow you use, this is typically the URL that a user’s browser is redirected to after successful authentication. As this URL is used for some OAuth flows to pass an access token, the URL must use secure HTTP (HTTPS) or a custom URI scheme. Separate multiple callback URLs with line breaks.
The callback URL field has a limit of 2000 characters, cumulatively. If you enter several URLs and they exceed this limit, configure another connected app to manage more callback URLs.





You should go through the documentation to get more details on the setup for Connected Apps. Good places to start are:



  • Connected Apps

  • Defining Connected Apps

  • Digging Deeper into OAuth 2.0 in Salesforce






share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 4 at 21:01

























answered Jan 4 at 20:50









Jayant DasJayant Das

13.1k2723




13.1k2723












  • Thanks for this. I have read 'most' of these resources but the emphasis seems geared towards human interacted processes.

    – SeanGorman
    Jan 4 at 21:37






  • 1





    I agree. I have struggled on this topic for a long time until I knew what it was.

    – Jayant Das
    Jan 4 at 21:46

















  • Thanks for this. I have read 'most' of these resources but the emphasis seems geared towards human interacted processes.

    – SeanGorman
    Jan 4 at 21:37






  • 1





    I agree. I have struggled on this topic for a long time until I knew what it was.

    – Jayant Das
    Jan 4 at 21:46
















Thanks for this. I have read 'most' of these resources but the emphasis seems geared towards human interacted processes.

– SeanGorman
Jan 4 at 21:37





Thanks for this. I have read 'most' of these resources but the emphasis seems geared towards human interacted processes.

– SeanGorman
Jan 4 at 21:37




1




1





I agree. I have struggled on this topic for a long time until I knew what it was.

– Jayant Das
Jan 4 at 21:46





I agree. I have struggled on this topic for a long time until I knew what it was.

– Jayant Das
Jan 4 at 21:46

















draft saved

draft discarded
















































Thanks for contributing an answer to Salesforce Stack Exchange!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f245498%2fapi-calls-to-salesforce-from-standalone-application%23new-answer', 'question_page');

);

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






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?