Salesforce Integration - Creating an API User in Salesforce

Creating an API User

The Salesforce documentation for creating an API User can be found here. Please refer to that guide if you find this one incomplete. While we can use a pre-existing user that you might be using for other integrations, we recommend creating a new one so that permissions may be kept separately for Mongoose.

If you already have an API User:

We require just a few permissions be enabled on it:

1. API Enabled is checked
2. Account read is checked
3. Contact read, create, and edit is checked
4. Read, create, and edit is checked on any custom SMS object you have created and plan to use to export message history out of Mongoose
5. Edit Tasks is checked
6. Password never expires

If you don’t already have an API User:

Start by creating a new custom profile (we named ours “API only”) and give it the permissions listed above at a minimum.

Create a new user and give it the API profile you just created. This will use up one license in your Salesforce instance, but insulates you from changes to actual users which may interrupt your integration with Mongoose. Salesforce will email you a security token for this user - keep track of this as it is needed for setting up Mongoose.

In either case, continue as follows;

The username of this new user is the Username we require in Mongoose. The password in Mongoose is a concatenation of the password and the user’s security token. For example, if the user’s password is “mypassword” and the security token is “ABC123” then the Mongoose password will be “mypasswordABC123”. We recommend setting this user with a very strong password as it is not set to expire or be reset.