Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Removed translated content for 'fr'
Sv translation
languageen

SalesForce Account

First of all, verify that the SalesForce Account works, by logging in. 

If necessary, a verification token must be entered (this happens on each new browser you login to). 

Recommend: when asked by SalesForce, input a mobile number as this speeds the process up considerably in the future.

...

(warning) Please note: the relevant Salesforce Account password for the jtel API should not contain some special characters (e.g. "< ) but may consist of a long sequence using alphanumeric characters.

Reset Security Token

If the account is new, the security token must be reset.

In the top navigation, go here:

Image Modified

Then on the left, here:

Image Modified

Then click "Reset Security Token".

The new security token will be delivered by E-Mail.

Generate OAUTH Token

To use REST Services, an OAUTH Token must be generated by SalesForce.

See https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_understanding_username_password_oauth_flow.htm for a reference.

The customer will provide the following information:

  • client_id
  • client_secret

The OAUTH Token is generated using CURL.

Code Block
titleCURL - Generate OAUTH Token
curl -d "grant_type=password&client_id=<client_id>&client_secret=<client_secret>&username=<salesforce_user_name>&password=<salesforce_password><security_token>" -X POST https://login.salesforce.com/services/oauth2/token

NOTE: there is no space between <salesforce_password> and <security_token>

For the endpoints, use the following for the live system:

https://login.salesforce.com/services/oauth2/token 

And the following for the test / sandbox system:

https://test.salesforce.com/services/oauth2/token 

 

Sv translation
languagede

Status
colourRed
titleThis page is only available in English

...