--- title: "RevSure Salesforce API Integration & Permissions" slug: "revsure-salesforce-api-integration-permissions" description: "Revsure's Salesforce integration uses OAuth 2.0 for secure data access, ensuring scalability, user control, and robust token management across customer orgs." tags: ["OAuth Authorization", "Connected App", "Data Access"] updated: 2026-09-29T07:57:46Z published: 2026-09-29T07:57:46Z canonical: "documents.revsure.ai/revsure-salesforce-api-integration-permissions" --- > ## Documentation Index > Fetch the complete documentation index at: https://documents.revsure.ai/llms.txt > Use this file to discover all available pages before exploring further. # RevSure Salesforce API Integration & Permissions ## **1. OAuth Authorization Flow & Connected App** Revsure’s Salesforce integration leverages the OAuth 2.0 framework to securely access customer data via a Connected App that is created and managed within Revsure’s own Salesforce org. This follows the standard multi-tenant SaaS integration model, where **a single Connected App** is defined by the provider and reused across multiple customer orgs. When a customer authorizes Revsure, they are granting this existing Connected App permission to access their data—no new app is created within their Salesforce environment. This approach ensures scalability, centralized configuration management, and a consistent security model across all integrations. ### **Authorization Flow** 1. User initiates connection from Revsure 2. User is redirected to Salesforce login page 3. User reviews and approves requested permissions 4. Salesforce generates: - **Access Token** (short-lived, used for API calls) - **Refresh Token** (used to obtain new access tokens) 5. Revsure securely stores these tokens ### **Connected App Configuration** | **Setting** | **Value** | | --- | --- | | **OAuth** **Scopes** | Access the identity URL service (id, profile, email, address, phone) Manage user data via APIs (api) Perform requests at any time (refresh_token, offline_access) | | **Callback URL** | [https://gw.revsure.cloud/data-hub/v1/oauth/callback](https://gw.revsure.cloud/data-hub/v1/oauth/callback) https://gw.revsure-eu.cloud/data-hub/v1/oauth/callback | | **Refresh Token Policy** | Valid until revoked | ### **Visibility & Control for Customers** After authorization, Revsure appears in Salesforce under: • Setup → Connected Apps → OAuth Usage ![](https://cdn.document360.io/1ba0d15e-f1ca-43db-aba7-8e6b7d8766f9/Images/Documentation/revsure-salesforce-api-integration--permissions-image-8w3d4e82.png) Customers can: • View authorized users and sessions • Revoke access at any time • Block the application if required Revsure leverages Salesforce OAuth to securely access data across multiple customer orgs. Access is granted explicitly by users, **governed by defined scopes**, and **can be revoked at any time**—ensuring a secure and transparent integration model. ## **2. Integration User Permissions** ### **Object-Level Access** The integration user requires **READ** access to the following Salesforce objects: | **Category** | **Object Details** | | --- | --- | | **Core CRM Objects** | Account, Contact, Lead, Opportunity, Campaign, CampaignMember, User, Product2, RecordType | | **Pipeline Objects** | OpportunityLineItem, OpportunityStage, OpportunityPartner, OpportunityContactRole, Period, ForecastingFact, ForecastingItem, ForecastingType | | **History Objects** | LeadHistory, OpportunityHistory, OpportunityFieldHistory, AccountHistory, CampaignHistory, ContactHistory | | **Other Objects** | Task, Event, EmailMessage, EmailMessageRelation, LeadStatus, CampaignInfluence, UserRole | | **Custom Objects** | | ### **Field-Level Access** By default, the integration user is expected to have **READ** access to all fields on the above objects, including: - All standard fields (Id, Name, CreatedDate, LastModifiedDate, SystemModstamp) - All custom fields - Any UTM tracking parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term) - Currency fields (if multi-currency is enabled) ### **System Permissions Required** - API Enabled - View All Data (or configure appropriate sharing rules) While RevSure requires READ access to all fields to enable quick ingestion of custom objects and custom fields for reporting, the following document lists all the standard Objects and Fields that are required by the standard mapping. - [RevSure - Salesforce Integration Standard Fields](https://docs.google.com/spreadsheets/d/1qngD7MEhHw97gfRlJhNvYpNYHwjqq-9hjg_XkGsxPGQ/edit?gid=0#gid=0) ## ## **3. Data Access Scope & Usage** - Revsure performs **read-only data extraction** from Salesforce - No create/update/delete operations are performed unless explicitly enabled - Data is accessed strictly for: - Reporting - Analytics - Attribution modeling - Access is limited by: - OAuth scopes - The permissions of the authorized Salesforce user ## ## ## ## ## ## ## ## ## ## **4. Token Management & Security** - Access tokens are short-lived and automatically rotated - Refresh tokens are stored securely using encryption at rest - Tokens are never exposed in logs or client-side systems - If access is revoked in Salesforce: - Tokens immediately become invalid - API access is terminated ## **References** [Salesforce Authorization Through External Client Apps or Connected Apps and OAuth 2.0](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_oauth_and_connected_apps.htm) ## Related - [RevSure Integration Access and Permissions](/revsureintegrationaccessandpermissions.md) - [Google Analytics Integration](/google-analytics-integration.md) - [Google Search Console Integration](/google-search-console-integration.md)