gong_api 1.0.0

data/spec/api/calls_api_spec.rb

@@ -0,0 +1,123 @@
+=begin
+#Gong API
+
+#<h2>Overview</h2> <p> The Gong API allows you to: </p> <ol> <li> Receive the following information from Gong: <ol type=\"a\"> <li> Your company's <a href=\"#tag--Calls\">calls</a> in Gong </li> <li> Your company's <a href=\"#tag--Users\">users</a> in Gong </li> <li> Your company's user <a href=\"#tag--Stats\">stats</a> in Gong </li> <li> Your company's user <a href=\"#tag--Settings\">settings</a> in Gong </li> <li> Your company's <a href=\"#tag--Library\">libraries</a> in Gong </li> </ol></li> <li> <a href=\"#post-/v2/calls\">Upload</a> new or  <a href=\"#put-/v2/calls/-id-/media\">update</a>  call recordings in Gong, in order to support cases where you have an internal system that records  calls or obtains them from a third-party entity. </li> <li> <a href=\"#post-/v2/data-privacy/erase-data-for-email-address\">Data Privacy</a>:  Delete users and all their associated elements.</li> <li> Upload <a href=\"#tag--CRM\">CRM</a> data into Gong.  </li> </ol> <p>Base URL for all API calls is <a href=\"https://us-55616.api.gong.io\"> https://us-55616.api.gong.io </a> </p> <h2>Authentication</h2>  <p> There are two ways to retrieve credentials to the Gong Public API: </p> <ol><li>Retrieve Manually:<br> <p> In the <a href=\"https://app.gong.io/company/api\">Gong API Page</a> (you must be a technical administrator in Gong), click \"Create\" to receive an <b>Access Key</b>  and an <b>Access Key Secret</b>.<br> </p> <p> Use the Basic Authorization HTTP header (as per <a target=\"_blank\" href=\"https://www.rfc-editor.org/rfc/rfc7617.txt\">RFC</a>) to access the Public API as shown below:<br> <code>Authorization: Basic &lt;token&gt;</code><br> </p> <p> To create the basic token, combine the <b>Access Key</b> and the <b>Access Key Secret</b> with  colon (:) and then encode in Base64 as following:<br> <code>Base64(&lt;accessKey&gt; : &lt;accessKeySecret&gt;)</code><br><br> </p></li> <li>Retrieve through OAuth<br> <p> To obtain the Bearer token, follow the steps described in the <a target=\"_blank\" href=\"https://help.gong.io/hc/en-us/articles/360056677792\">Gong OAuth Guide</a>. <br></p> <p> After obtaining the token, use the Bearer Authorization HTTP header (as per <a target=\"_blank\" href=\"https://www.rfc-editor.org/rfc/rfc6750.txt\">RFC</a>) to access the Public API as shown below:<br> <code>Authorization: Bearer &lt;token&gt;</code> </p> </li></ol> <h2>Limits</h2>  <p> By default Gong limits your company's access to the service to 3 API calls per second, and 10,000 API calls per day. </p> <p> When the rate of API calls exceeds these limits an HTTP status code <b>429</b> is returned and a <b>Retry-After</b> header indicates  how many seconds to wait before making a new request. </p><p> If required, contact help@gong.io to change these limits. </p>  <h2>Cursors</h2>  <p> Some API calls that return a list are limited in the amount of records they may return, so multiple API calls may be  required to bring all records. Such an API call also returns a <b>records</b> field, which contains the number of records  in the current page, the current page number and the total number of records. </p> <p> In cases where the total number of records exceeds the number of records thus far retrieved, the <b>records</b> field will also  contain a <b>cursor</b> field which can be used to access the next page of records. To retrieve the next page, repeat the API call with  the <b>cursor</b> value as supplied by the previous API call. All other request inputs should remain the same. </p> <h2>Forward Compatibility</h2>  <p> When coding a system to accept Gong data, take into account that Gong may, without prior warning, add fields to the JSON output.  It is recommended to future proof your code so that it disregards all JSON fields you don't actually use.  </p><p></p>
+
+OpenAPI spec version: V2
+
+Generated by: https://github.com/swagger-api/swagger-codegen.git
+Swagger Codegen version: 3.0.37
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for GongAPI::CallsApi
+# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
+# Please update as you see appropriate
+describe 'CallsApi' do
+  before do
+    # run before each test
+    @instance = GongAPI::CallsApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of CallsApi' do
+    it 'should create an instance of CallsApi' do
+      expect(@instance).to be_instance_of(GongAPI::CallsApi)
+    end
+  end
+
+  # unit tests for add_call_recording_using_put
+  # Add call media (/v2/calls/{id}/media)
+  # Adds a call media, recorded by a telephony system (PBX) or other media recording facility. Gong accepts call recordings in various audio and video file formats, including WAV, MP3, MP4, MKV and FLAC. If uploading a dual-channel (stereo) file separated by speaker, make sure to specify which channel correspondsto the company team member (rep) in the parties/mediaChannelId parameter of the Add New Call operation.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:calls:create&#x27;.
+  # @param id callId returned from &#x27;Add New Call&#x27; request
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :media_file 
+  # @return [NewCallRecordingResponse]
+  describe 'add_call_recording_using_put test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for add_call_using_post
+  # Add new call (/v2/calls)
+  # When using this endpoint, either provide a downloadMediaUrl or use the returned callId in a follow-up request to /v2/calls/{id}/media to upload the media file.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:calls:create&#x27;.
+  # @param body newCallAddingRequest
+  # @param [Hash] opts the optional parameters
+  # @return [NewCallAddingResponse]
+  describe 'add_call_using_post test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_call_transcripts_using_post
+  # Retrieve transcripts of calls by date or callIds (/v2/calls/transcript)
+  # Lists the transcripts of calls that took place during a specified date range and have specified callIds.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:calls:read:transcript&#x27;.
+  # @param body callsRequest
+  # @param [Hash] opts the optional parameters
+  # @return [CallTranscripts]
+  describe 'get_call_transcripts_using_post test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_call_using_get
+  # Retrieve data for a specific call (/v2/calls/{id})
+  # Retrieve data for a specific call.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:calls:read:basic&#x27;.
+  # @param id Gong&#x27;s unique numeric identifier for the call (up to 20 digits).
+  # @param [Hash] opts the optional parameters
+  # @return [SpecificCall]
+  describe 'get_call_using_get test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for list_calls_extensive_using_post
+  # Retrieve detailed call data by various filters (/v2/calls/extensive)
+  # Lists detailed call data for calls that took place during a specified date range, have specified call IDs or hosted by specified users.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:calls:read:extensive&#x27;.  Moreover, clients requesting media download URLs by the contentSelector.exposedFields.media field should also have the scope &#x27;api:calls:read:media-url&#x27;.
+  # @param body callsRequest
+  # @param [Hash] opts the optional parameters
+  # @return [Calls]
+  describe 'list_calls_extensive_using_post test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for list_calls_using_get1
+  # Retrieve call data by date range (/v2/calls)
+  # List calls that took place during a specified date range.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:calls:read:basic&#x27;.
+  # @param from_date_time The date from which to list calls, in the ISO-8601 format (e.g., &#x27;2018-02-18T02:30:00-07:00&#x27; or &#x27;2018-02-18T08:00:00Z&#x27;, where Z stands for UTC); if not specified, the calls start with the earliest recorded call. For web-conference calls recorded by Gong, the date denotes its scheduled time, otherwise, it denotes its actual start time.
+  # @param to_date_time The date until which to list calls, in the ISO-8601 format (e.g., &#x27;2018-02-18T02:30:00-07:00&#x27; or &#x27;2018-02-18T08:00:00Z&#x27;, where Z stands for UTC); if not specified, the calls end with the latest recorded call. For web-conference calls recorded by Gong, the date denotes its scheduled time, otherwise, it denotes its actual start time.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :cursor When paging is needed, provide the value supplied by the previous API call to bring the following page of records.
+  # @option opts [String] :workspace_id Optional Workspace identifier, if supplied the API will return only the calls belonging to this workspace.
+  # @return [CallsResponse]
+  describe 'list_calls_using_get1 test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for list_crm_calls_manual_association_using_get
+  # List all calls that were manually associated with CRM objects (/v2/calls/manual-crm-associations) in Beta Phase
+  # Returns a list of all calls that were manually associated or re-associated with CRM account and deal/opportunity since a given time.  Actions will be listed in the ascending order of their timing.   Notice if a call was associated and later re-associated the API will return both events.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:crm-calls:manual-association:read&#x27;.
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :cursor When paging is needed, provide the value supplied by the previous API call to bring the following page of records.
+  # @option opts [String] :from_date_time Association time filter - only the associations made after that time will be listed. The time is in the ISO-8601 format (e.g., &#x27;2018-02-18T02:30:00-07:00&#x27; or &#x27;2018-02-18T08:00:00Z&#x27;, where Z stands for UTC); if not specified all association events will be listed.
+  # @return [ManualAssociationResponse]
+  describe 'list_crm_calls_manual_association_using_get test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/crm_api_spec.rb

@@ -0,0 +1,161 @@
+=begin
+#Gong API
+
+#<h2>Overview</h2> <p> The Gong API allows you to: </p> <ol> <li> Receive the following information from Gong: <ol type=\"a\"> <li> Your company's <a href=\"#tag--Calls\">calls</a> in Gong </li> <li> Your company's <a href=\"#tag--Users\">users</a> in Gong </li> <li> Your company's user <a href=\"#tag--Stats\">stats</a> in Gong </li> <li> Your company's user <a href=\"#tag--Settings\">settings</a> in Gong </li> <li> Your company's <a href=\"#tag--Library\">libraries</a> in Gong </li> </ol></li> <li> <a href=\"#post-/v2/calls\">Upload</a> new or  <a href=\"#put-/v2/calls/-id-/media\">update</a>  call recordings in Gong, in order to support cases where you have an internal system that records  calls or obtains them from a third-party entity. </li> <li> <a href=\"#post-/v2/data-privacy/erase-data-for-email-address\">Data Privacy</a>:  Delete users and all their associated elements.</li> <li> Upload <a href=\"#tag--CRM\">CRM</a> data into Gong.  </li> </ol> <p>Base URL for all API calls is <a href=\"https://us-55616.api.gong.io\"> https://us-55616.api.gong.io </a> </p> <h2>Authentication</h2>  <p> There are two ways to retrieve credentials to the Gong Public API: </p> <ol><li>Retrieve Manually:<br> <p> In the <a href=\"https://app.gong.io/company/api\">Gong API Page</a> (you must be a technical administrator in Gong), click \"Create\" to receive an <b>Access Key</b>  and an <b>Access Key Secret</b>.<br> </p> <p> Use the Basic Authorization HTTP header (as per <a target=\"_blank\" href=\"https://www.rfc-editor.org/rfc/rfc7617.txt\">RFC</a>) to access the Public API as shown below:<br> <code>Authorization: Basic &lt;token&gt;</code><br> </p> <p> To create the basic token, combine the <b>Access Key</b> and the <b>Access Key Secret</b> with  colon (:) and then encode in Base64 as following:<br> <code>Base64(&lt;accessKey&gt; : &lt;accessKeySecret&gt;)</code><br><br> </p></li> <li>Retrieve through OAuth<br> <p> To obtain the Bearer token, follow the steps described in the <a target=\"_blank\" href=\"https://help.gong.io/hc/en-us/articles/360056677792\">Gong OAuth Guide</a>. <br></p> <p> After obtaining the token, use the Bearer Authorization HTTP header (as per <a target=\"_blank\" href=\"https://www.rfc-editor.org/rfc/rfc6750.txt\">RFC</a>) to access the Public API as shown below:<br> <code>Authorization: Bearer &lt;token&gt;</code> </p> </li></ol> <h2>Limits</h2>  <p> By default Gong limits your company's access to the service to 3 API calls per second, and 10,000 API calls per day. </p> <p> When the rate of API calls exceeds these limits an HTTP status code <b>429</b> is returned and a <b>Retry-After</b> header indicates  how many seconds to wait before making a new request. </p><p> If required, contact help@gong.io to change these limits. </p>  <h2>Cursors</h2>  <p> Some API calls that return a list are limited in the amount of records they may return, so multiple API calls may be  required to bring all records. Such an API call also returns a <b>records</b> field, which contains the number of records  in the current page, the current page number and the total number of records. </p> <p> In cases where the total number of records exceeds the number of records thus far retrieved, the <b>records</b> field will also  contain a <b>cursor</b> field which can be used to access the next page of records. To retrieve the next page, repeat the API call with  the <b>cursor</b> value as supplied by the previous API call. All other request inputs should remain the same. </p> <h2>Forward Compatibility</h2>  <p> When coding a system to accept Gong data, take into account that Gong may, without prior warning, add fields to the JSON output.  It is recommended to future proof your code so that it disregards all JSON fields you don't actually use.  </p><p></p>
+
+OpenAPI spec version: V2
+
+Generated by: https://github.com/swagger-api/swagger-codegen.git
+Swagger Codegen version: 3.0.37
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for GongAPI::CRMApi
+# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
+# Please update as you see appropriate
+describe 'CRMApi' do
+  before do
+    # run before each test
+    @instance = GongAPI::CRMApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of CRMApi' do
+    it 'should create an instance of CRMApi' do
+      expect(@instance).to be_instance_of(GongAPI::CRMApi)
+    end
+  end
+
+  # unit tests for delete_generic_crm_integration_using_delete
+  # Delete a Generic CRM integration (/v2/crm/integration/delete)
+  # &lt;style&gt;.public-api-info {    background: rgb(222, 235, 255);}.public-api-tip {    background: rgb(227, 252, 239);}.public-api-parameter {    background: rgba(9,30,66,0.08);}.public-api-note {    background: rgb(234, 230, 255);}.public-api-important {    background: rgb(255, 250, 230);}.public-api-critical {    background: rgb(255, 235, 230);}table, th, td {  border: 1px solid gray;  border-collapse: collapse;}th, td {  padding: 5px;}th {  text-align: left;}&lt;/style&gt;&lt;p&gt;Deletes a Generic CRM integration and all its associated crm objects (Accounts, Contacts, Deals, Leads, and Users).&lt;/p&gt;&lt;p&gt;This API is asynchronous. Call \&quot;/request-status\&quot; API with the clientRequestId sent to this API to track progress of the delete request:&lt;br&gt;Status DONE indicates that the integration and all its associated crm objects have been successfully deleted. Calls associations may take up to 24 hours to be deleted.&lt;/p&gt;&lt;h3&gt;Example&lt;/h3&gt;&lt;h4&gt;Request&lt;/h4&gt;&lt;code&gt;DELETE https://api.gong.io/v2/crm/integration/delete?clientRequestId&#x3D;1234&amp;integrationId&#x3D;6286478263646&lt;/code&gt;&lt;p&gt;When accessed using a bearer token, this endpoint requires the scope &#x27;api:crm:integration:delete&#x27;.&lt;/p&gt;
+  # @param client_request_id A unique identifier sent by you to allow troubleshooting requests. Valid characters for this field are letters, numbers, dashes and underscores.
+  # @param integration_id Integration ID generated when creating the integration
+  # @param [Hash] opts the optional parameters
+  # @return [AsyncProcessingResponse]
+  describe 'delete_generic_crm_integration_using_delete test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_crm_objects_using_get
+  # Get CRM objects (/v2/crm/object/list)
+  # &lt;style&gt;.public-api-info {    background: rgb(222, 235, 255);}.public-api-tip {    background: rgb(227, 252, 239);}.public-api-parameter {    background: rgba(9,30,66,0.08);}.public-api-note {    background: rgb(234, 230, 255);}.public-api-important {    background: rgb(255, 250, 230);}.public-api-critical {    background: rgb(255, 235, 230);}table, th, td {  border: 1px solid gray;  border-collapse: collapse;}th, td {  padding: 5px;}th {  text-align: left;}&lt;/style&gt;&lt;p&gt;This API is intended to be used in &lt;b&gt;development phase only&lt;/b&gt;, to manually verify that objects are uploaded and processed correctly in Gong.&lt;/p&gt;&lt;p&gt;Returns a JSON object where each key is the object crm id and the corresponding value is a nested JSON object representing the CRM object fields. Each key in the nested JSON is the field name and the corresponding value is the field value.&lt;/p&gt;&lt;p&gt;The objects are fetched from the Gong main DB. If the object is not found, the JSON’s value will be null.&lt;/p&gt;&lt;p&gt;The request body contains an array of objects ids.&lt;/p&gt;&lt;p&gt;The request is limited to 100 objects. If more than 100 objects are requested only the first 100 are returned.&lt;/p&gt;&lt;p&gt;When accessed using a bearer token, this endpoint requires the scope &#x27;api:crm:get-objects&#x27;.&lt;/p&gt;
+  # @param body Requested objects crm ids
+  # @param integration_id Integration ID generated when creating the integration
+  # @param object_type Requested objects type
+  # @param [Hash] opts the optional parameters
+  # @return [GetGenericCrmObjectsResponse]
+  describe 'get_crm_objects_using_get test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for get_request_status_using_get
+  # Get Request Status (/v2/crm/request-status)
+  # &lt;style&gt;.public-api-info {    background: rgb(222, 235, 255);}.public-api-tip {    background: rgb(227, 252, 239);}.public-api-parameter {    background: rgba(9,30,66,0.08);}.public-api-note {    background: rgb(234, 230, 255);}.public-api-important {    background: rgb(255, 250, 230);}.public-api-critical {    background: rgb(255, 235, 230);}table, th, td {  border: 1px solid gray;  border-collapse: collapse;}th, td {  padding: 5px;}th {  text-align: left;}&lt;/style&gt;&lt;p&gt;Returns the current status of the request for \&quot;/map/users\&quot;, \&quot;/object/entities\&quot; or \&quot;/integration/delete\&quot; API.&lt;/p&gt;&lt;p&gt;When accessed using a bearer token, this endpoint requires the scope &#x27;api:crm:upload&#x27;.&lt;/p&gt;&lt;h3&gt;Status Codes&lt;/h3&gt;&lt;ul&gt;    &lt;li&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;PENDING&lt;/span&gt; - File is pending parsing&lt;/li&gt;    &lt;li&gt;&lt;span class&#x3D;&#x27;public-api-note&#x27;&gt;IN_PROGRESS&lt;/span&gt; - File is being parsed&lt;/li&gt;    &lt;li&gt;&lt;span class&#x3D;&#x27;public-api-info&#x27;&gt;DONE&lt;/span&gt; - All objects in the file were successfully parsed&lt;/li&gt;    &lt;li&gt;&lt;span class&#x3D;&#x27;public-api-critical&#x27;&gt;FAILED&lt;/span&gt; - Failed to parse some objects in the file or on a general error when the file was being processed&lt;/li&gt;&lt;/ul&gt;&lt;h3&gt;Status Indication&lt;/h3&gt;&lt;ul&gt;    &lt;li&gt;For \&quot;/object/entities\&quot; API, status &lt;span class&#x3D;&#x27;public-api-info&#x27;&gt;DONE&lt;/span&gt; indicates that all objects in the LDJSON file were successfully parsed and stored in raw storage.&lt;br&gt;        Note that it can take up to 1 hour from the time the LDJSON file was uploaded using the \&quot;/object/entities\&quot; API until deals are fully processed and available to the end user on the Deals Board.    &lt;/li&gt;    &lt;li&gt;For \&quot;/map/users\&quot; API, status &lt;span class&#x3D;&#x27;public-api-info&#x27;&gt;DONE&lt;/span&gt; indicates that the mapping was successfully created and is available in Gong for the processing of other objects.&lt;/li&gt;    &lt;li&gt;&lt;span class&#x3D;&#x27;public-api-critical&#x27;&gt;FAILED&lt;/span&gt;:        &lt;ul&gt;            &lt;li&gt;If you receive a &lt;span class&#x3D;&#x27;public-api-critical&#x27;&gt;FAILED&lt;/span&gt; status with a specific error list there are errors you need to address in the object:                &lt;ul&gt;                    &lt;li&gt;Fix the objects&#x27; JSON.&lt;/li&gt;                    &lt;li&gt;Resend the entire LDJSON file to \&quot;/object/entities\&quot; or \&quot;/map/users\&quot; API.&lt;br&gt;                        Note that The returned errors list is &lt;b&gt;limited to the first 20 errors&lt;/b&gt;. To make sure you have corrected all the possible errors you need to upload the entire file repeatedly until you receive a &lt;span class&#x3D;&#x27;public-api-info&#x27;&gt;DONE&lt;/span&gt; status.                    &lt;/li&gt;                &lt;/ul&gt;            &lt;/li&gt;            &lt;li&gt;If you received a &lt;span class&#x3D;&#x27;public-api-critical&#x27;&gt;FAILED&lt;/span&gt; status with a single error in the form of&lt;br&gt;                {\&quot;line\&quot;:0,\&quot;description\&quot;:\&quot;.....\&quot;} this indicates a general processing error:                &lt;ul&gt;                    &lt;li&gt;Fix the LDJSON file according to the error message.&lt;/li&gt;                    &lt;li&gt;Upload the entire LDJSON file again.&lt;/li&gt;                &lt;/ul&gt;            &lt;/li&gt;        &lt;/ul&gt;    &lt;/li&gt;&lt;/ul&gt;
+  # @param client_request_id &lt;span style&#x3D;&#x27;background: rgba(9,30,66,0.08)&#x27;&gt;clientRequestId&lt;/span&gt; sent to \&quot;/map/users\&quot;, \&quot;/object/entities\&quot; or \&quot;/integration/delete\&quot; API
+  # @param integration_id Integration ID generated when creating the integration
+  # @param [Hash] opts the optional parameters
+  # @return [RequestStatusResponse]
+  describe 'get_request_status_using_get test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for list_crm_schema_fields_using_get
+  # List Schema Fields (/v2/crm/object/schema/list)
+  # &lt;style&gt;.public-api-info {    background: rgb(222, 235, 255);}.public-api-tip {    background: rgb(227, 252, 239);}.public-api-parameter {    background: rgba(9,30,66,0.08);}.public-api-note {    background: rgb(234, 230, 255);}.public-api-important {    background: rgb(255, 250, 230);}.public-api-critical {    background: rgb(255, 235, 230);}table, th, td {  border: 1px solid gray;  border-collapse: collapse;}th, td {  padding: 5px;}th {  text-align: left;}&lt;/style&gt;&lt;p&gt;Retrieves a list of the object schema fields.&lt;/p&gt;&lt;p&gt;When accessed using a bearer token, this endpoint requires the scope &#x27;api:crm:schema&#x27;.&lt;/p&gt;&lt;h3&gt;Example&lt;/h3&gt;&lt;h4&gt;Request&lt;/h4&gt;&lt;code&gt;GET https://api.gong.io/v2/crm/object/schema/list?integrationId&#x3D;6286478263646&amp;objectType&#x3D;ACCOUNT&lt;/code&gt;&lt;h4&gt;Response&lt;/h4&gt;&lt;code&gt;{    \&quot;requestId\&quot;: \&quot;afjkzqkqglog7ueki5\&quot;,    \&quot;selectedFields\&quot;: {        \&quot;ACCOUNT\&quot;: [            {                \&quot;name\&quot;: \&quot;accountTypePicklist\&quot;,                \&quot;label\&quot;: \&quot;Account Type\&quot;,                \&quot;type\&quot;: \&quot;PICKLIST\&quot;,                \&quot;lastModified\&quot;: null,                \&quot;isDeleted\&quot;: false,                \&quot;referenceTo\&quot;: null,                \&quot;orderedValueList\&quot;: null            },            {                \&quot;name\&quot;: \&quot;accountTypePicklist2\&quot;,                \&quot;label\&quot;: \&quot;Account Type2\&quot;,                \&quot;type\&quot;: \&quot;PICKLIST\&quot;,                \&quot;lastModified\&quot;: null,                \&quot;isDeleted\&quot;: false,                \&quot;referenceTo\&quot;: null,                \&quot;orderedValueList\&quot;: null            },            {                \&quot;name\&quot;: \&quot;fooBar\&quot;,                \&quot;label\&quot;: \&quot;Foo Bar\&quot;,                \&quot;type\&quot;: \&quot;STRING\&quot;,                \&quot;lastModified\&quot;: null,                \&quot;isDeleted\&quot;: false,                \&quot;referenceTo\&quot;: null,                \&quot;orderedValueList\&quot;: null            }        ]    }}&lt;/code&gt;
+  # @param integration_id Integration ID generated when creating the integration
+  # @param object_type Type of object to retrieve the schema fields for (case-sensitive). &lt;br&gt;Omitting this parameter returns the schema for all object types.
+  # @param [Hash] opts the optional parameters
+  # @return [ListSelectedFieldsResponse]
+  describe 'list_crm_schema_fields_using_get test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for list_generic_crm_integration_using_get
+  # Get Generic CRM integration details (/v2/crm/integration/list)
+  # &lt;style&gt;.public-api-info {    background: rgb(222, 235, 255);}.public-api-tip {    background: rgb(227, 252, 239);}.public-api-parameter {    background: rgba(9,30,66,0.08);}.public-api-note {    background: rgb(234, 230, 255);}.public-api-important {    background: rgb(255, 250, 230);}.public-api-critical {    background: rgb(255, 235, 230);}table, th, td {  border: 1px solid gray;  border-collapse: collapse;}th, td {  padding: 5px;}th {  text-align: left;}&lt;/style&gt;&lt;p&gt;Returns a list of all active Generic CRM integrations of the company. Only integrations created with &#x27;Register a Generic CRM integration&#x27; API are returned.&lt;br&gt;Only one active integration is currently supported.&lt;/p&gt;&lt;p&gt;When accessed using a bearer token, this endpoint requires the scope &#x27;api:crm:integrations:read&#x27;.&lt;/p&gt;
+  # @param [Hash] opts the optional parameters
+  # @return [ListGenericCrmIntegrationsResponse]
+  describe 'list_generic_crm_integration_using_get test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for map_crm_users_using_post
+  # Map Users (Deprecated)
+  # &lt;style&gt;.public-api-info {    background: rgb(222, 235, 255);}.public-api-tip {    background: rgb(227, 252, 239);}.public-api-parameter {    background: rgba(9,30,66,0.08);}.public-api-note {    background: rgb(234, 230, 255);}.public-api-important {    background: rgb(255, 250, 230);}.public-api-critical {    background: rgb(255, 235, 230);}table, th, td {  border: 1px solid gray;  border-collapse: collapse;}th, td {  padding: 5px;}th {  text-align: left;}&lt;/style&gt;&lt;p&gt;This API is &lt;b&gt;Deprecated&lt;/b&gt;. Please use \&quot;/object/entities?objectType&#x3D;BUSINESS_USER\&quot; API instead.&lt;/p&gt;&lt;p&gt;Gong associates users with the CRM &lt;b&gt;User&lt;/b&gt; entity. Mapping users accurately is essential for Gong to connect users with all their associated objects in the CRM.&lt;/p&gt;&lt;p&gt;This API creates a mapping in Gong between the user ID in the CRM system and the user ID in Gong.&lt;/p&gt;&lt;br&gt;&lt;div class&#x3D;&#x27;public-api-important&#x27;&gt;&lt;b&gt;Important:&lt;/b&gt;&lt;p&gt;User mapping is important to ensure deals are processed in Gong correctly. Each uploaded deal contains an ownerId field, which contains a user ID from the CRM system.&lt;br&gt;&lt;b&gt;Gong only processes a deal if this user ID is mapped to a user in Gong who is set to record or import calls.&lt;/b&gt;&lt;/p&gt;&lt;p&gt;Each request to this API must include the complete list of users from the CRM system.&lt;/p&gt;&lt;/div&gt;&lt;p&gt;If a user mapping is sent after a deal is uploaded:&lt;/p&gt;&lt;ol&gt;    &lt;li&gt;Gong retroactively searches for deals whose ownerId matches the user ID mapping.&lt;/li&gt;    &lt;li&gt;Gong starts to reprocess those matched deals from raw storage into Gong’s main database.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;Gong matches the user from the uploaded JSON to a user in Gong based on the email address.&lt;/p&gt;&lt;div class&#x3D;&#x27;public-api-info&#x27;&gt;&lt;p&gt;The user mapping will not be created when:&lt;/p&gt;&lt;ul&gt;    &lt;li&gt;There is no user in Gong with the supplied email address&lt;/li&gt;    &lt;li&gt;Mapping already exists for the supplied email address&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;To update an existing mapping:&lt;/p&gt;&lt;ol&gt;    &lt;li&gt;Delete the existing mapping by sending an existing mapping with isDeleted&#x3D;true.&lt;/li&gt;    &lt;li&gt;In a separate request send a new mapping for the email address.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;The request body is a file in LDJSON format, meaning the file should contain JSON objects - where each JSON object is on a separate line and represents a single user from the CRM system.&lt;/p&gt;&lt;p&gt;&lt;b&gt;Request Body Specifications:&lt;/b&gt;&lt;/p&gt;&lt;ul&gt;    &lt;li&gt;Content-Type should be multipart/form-data&lt;/li&gt;    &lt;li&gt;Maximum payload size: 200 megabytes&lt;/li&gt;    &lt;li&gt;The request body should include one parameter named \&quot;&lt;b&gt;dataFile&lt;/b&gt;\&quot; which contains the LDJSON file.&lt;/li&gt;&lt;/ul&gt;&lt;h3&gt;Request parameters (QUERY-STRING parameters)&lt;/h3&gt;&lt;table&gt;    &lt;thead&gt;        &lt;tr&gt;            &lt;th&gt;Name&lt;/th&gt;            &lt;th&gt;Description&lt;/th&gt;            &lt;th&gt;Data Type&lt;/th&gt;            &lt;th&gt;Mandatory&lt;/th&gt;        &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;clientRequestId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;A unique identifier sent by you to enable troubleshooting communication.&lt;br&gt;            Gong uses this identifier to prevent repeated attempts to upload the same users list.&lt;br&gt;            Valid characters for this field: Letters, numbers, dashes, and underscores.            &lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;integrationId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;Integration ID generated when creating the integration&lt;/td&gt;            &lt;td&gt;long&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;User JSON object requires the following fields:&lt;/p&gt;&lt;table&gt;    &lt;thead&gt;        &lt;tr&gt;            &lt;th&gt;Name&lt;/th&gt;            &lt;th&gt;Description&lt;/th&gt;            &lt;th&gt;Data Type&lt;/th&gt;            &lt;th&gt;Mandatory&lt;/th&gt;        &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;crmUserId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;User ID in the CRM system&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;emailAddress&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;Must match an email address of a user in Gong. Not mandatory when isDeleted &#x3D; true.&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;isDeleted&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;\&quot;true\&quot; deletes the user mapping. Default &#x3D; \&quot;false\&quot;&lt;/td&gt;            &lt;td&gt;boolean&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;h3&gt;Response&lt;/h3&gt;&lt;code&gt;201 Created&lt;/code&gt;&lt;table&gt;    &lt;thead&gt;        &lt;tr&gt;            &lt;th&gt;Name&lt;/th&gt;            &lt;th&gt;Data Type&lt;/th&gt;            &lt;th&gt;Description&lt;/th&gt;        &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;clientRequestId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;the &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;clientRequestId&lt;/span&gt; sent in the request&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;requestId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;A Gong request reference Id, generated for this request&lt;/td&gt;        &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;div class&#x3D;&#x27;public-api-important&#x27;&gt;&lt;p&gt;&lt;b&gt;Important:&lt;/b&gt; The users mapping API is asynchronous. A 201 response only indicates that the file successfully uploaded to Gong and is pending processing. Use the &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;clientRequestId&lt;/span&gt; to troubleshoot failed requests and watch the request status using \&quot;/request-status\&quot; API.&lt;/p&gt;&lt;/div&gt;&lt;h3&gt;Error Codes&lt;/h3&gt;400 - Malformed request&lt;br&gt;401 - Access denied&lt;br&gt;409 Conflict - clientRequestId already exists&lt;br&gt;429 - API request limit exceeded&lt;br&gt;500 - Internal Server Error&lt;p&gt;When accessed using a bearer token, this endpoint requires the scope &#x27;api:crm:upload&#x27;.&lt;/p&gt;&lt;h3&gt;Example&lt;/h3&gt;&lt;h4&gt;Request&lt;/h4&gt;&lt;code&gt;POST https://api.gong.io/v2/crm/map/users?clientRequestId&#x3D;1234&amp;integrationId&#x3D;6286478263646&lt;/code&gt;&lt;br&gt;&lt;br&gt;&lt;code&gt;{\&quot;crmUserId\&quot;: \&quot;2356ddfwe32\&quot;, \&quot;emailAddress\&quot;: \&quot;john.doe@acme.com\&quot;}&lt;br&gt;{\&quot;crmUserId\&quot;: \&quot;67534ghf745\&quot;, \&quot;isDeleted\&quot;: true} // remove user mapping for user 67534ghf745&lt;/code&gt;
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :data_file 
+  # @return [AsyncProcessingResponse]
+  describe 'map_crm_users_using_post test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for register_generic_crm_integration_using_put
+  # Register a Generic CRM integration (/v2/crm/integration/new)
+  # &lt;style&gt;.public-api-info {    background: rgb(222, 235, 255);}.public-api-tip {    background: rgb(227, 252, 239);}.public-api-parameter {    background: rgba(9,30,66,0.08);}.public-api-note {    background: rgb(234, 230, 255);}.public-api-important {    background: rgb(255, 250, 230);}.public-api-critical {    background: rgb(255, 235, 230);}table, th, td {  border: 1px solid gray;  border-collapse: collapse;}th, td {  padding: 5px;}th {  text-align: left;}&lt;/style&gt;&lt;p&gt;Register the CRM application in Gong and use the returned integrationId in future requests to the CRM API to correlate the data with the specific CRM.&lt;/p&gt;&lt;p&gt;Multiple CRM integrations are not currently supported. To create a new integration, first delete the old one.&lt;/p&gt;&lt;p&gt;When accessed using a bearer token, this endpoint requires the scope &#x27;api:crm:integration:register&#x27;.&lt;/p&gt;
+  # @param body registrationRequest
+  # @param [Hash] opts the optional parameters
+  # @return [RegisterGenericCrmResponse]
+  describe 'register_generic_crm_integration_using_put test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for upload_crm_data_using_post
+  # Upload CRM objects (/v2/crm/object/entities)
+  # &lt;style&gt;.public-api-info {    background: rgb(222, 235, 255);}.public-api-tip {    background: rgb(227, 252, 239);}.public-api-parameter {    background: rgba(9,30,66,0.08);}.public-api-note {    background: rgb(234, 230, 255);}.public-api-important {    background: rgb(255, 250, 230);}.public-api-critical {    background: rgb(255, 235, 230);}table, th, td {  border: 1px solid gray;  border-collapse: collapse;}th, td {  padding: 5px;}th {  text-align: left;}&lt;/style&gt;&lt;p&gt;Inserts, updates, or deletes a CRM object in Gong.&lt;br&gt;If an existing object with the same id is detected it will be updated, otherwise it will be inserted as a new object.&lt;/p&gt;&lt;p&gt;The request body is a file in LDJSON format, meaning the file should contain JSON objects, where each JSON object is in a separate line and represents a single CRM object.&lt;/p&gt;&lt;p&gt;All objects in a single request should be of the same object type. An object cannot be contained more than once in a given list.&lt;/p&gt;&lt;p&gt;&lt;b&gt;Request Body Specifications:&lt;/b&gt;&lt;/p&gt;&lt;ul&gt;    &lt;li&gt;Content-Type should be multipart/form-data&lt;/li&gt;    &lt;li&gt;Maximum payload size: 200 megabytes&lt;/li&gt;    &lt;li&gt;The request body should contain one parameter named \&quot;&lt;b&gt;dataFile&lt;/b&gt;\&quot; which holds the LDJSON file&lt;/li&gt;&lt;/ul&gt;&lt;div class&#x3D;&#x27;public-api-important&#x27;&gt;&lt;p&gt;&lt;b&gt;Important:&lt;/b&gt; The list must be sorted by modifiedDate Ascending.&lt;/p&gt;&lt;/div&gt;&lt;div class&#x3D;&#x27;public-api-info&#x27;&gt;&lt;p&gt;&lt;ul&gt;    &lt;li&gt;On initial upload: Only send the items that weren’t deleted&lt;/li&gt;    &lt;li&gt;On subsequent (incremental) uploads: Send all items.&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;&lt;/div&gt;&lt;div class&#x3D;&#x27;public-api-info&#x27;&gt;&lt;p&gt;Dates in the uploaded JSON objects are represented in ISO-8601 format without milliseconds (e.g. &#x27;2018-02-18T02:30:00-07:00&#x27; or &#x27;2018-02-18T08:00:00Z&#x27;, where Z stands for UTC).&lt;/p&gt;&lt;/div&gt;&lt;h3&gt;Request parameters (QUERY-STRING parameters)&lt;/h3&gt;&lt;table&gt;    &lt;thead&gt;        &lt;tr&gt;            &lt;th&gt;Name&lt;/th&gt;            &lt;th&gt;Description&lt;/th&gt;            &lt;th&gt;Data Type&lt;/th&gt;            &lt;th&gt;Mandatory&lt;/th&gt;        &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;integrationId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;Integration ID generated when creating the integration&lt;/td&gt;            &lt;td&gt;long&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;objectType&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;Must be one of: \&quot;ACCOUNT\&quot;, \&quot;CONTACT\&quot;, \&quot;DEAL\&quot;, \&quot;LEAD\&quot;, \&quot;BUSINESS_USER\&quot;, or \&quot;STAGE\&quot; (case-sensitive)&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;clientRequestId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;A unique identifier sent by you to allow troubleshooting communication.&lt;br&gt;            Gong also uses this identifier to prevent repeated attempts to upload the same object list.&lt;br&gt;            Valid characters for this field are letters, numbers, dashes and underscores.            &lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;h3&gt;Response&lt;/h3&gt;&lt;code&gt;201 Created&lt;/code&gt;&lt;table&gt;    &lt;thead&gt;        &lt;tr&gt;            &lt;th&gt;Name&lt;/th&gt;            &lt;th&gt;Data Type&lt;/th&gt;            &lt;th&gt;Description&lt;/th&gt;        &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;clientRequestId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;the &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;clientRequestId&lt;/span&gt; sent in the request&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;requestId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;A Gong request reference Id, generated for this request&lt;/td&gt;        &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;div class&#x3D;&#x27;public-api-important&#x27;&gt;&lt;p&gt;&lt;b&gt;Important:&lt;/b&gt; The upload objects API is asynchronous. A 201 response only indicates that the file successfully uploaded to Gong and is pending processing. Use the &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;clientRequestId&lt;/span&gt; to troubleshoot failed requests and watch the request status using \&quot;/request-status\&quot; API.&lt;/p&gt;&lt;/div&gt;&lt;h3&gt;Error Codes&lt;/h3&gt;400 - Malformed request&lt;br&gt;401 - Access denied&lt;br&gt;409 Conflict - clientRequestId already exists&lt;br&gt;429 - API request limit exceeded&lt;br&gt;500 - Internal Server Error&lt;p&gt;When accessed using a bearer token, this endpoint requires the scope &#x27;api:crm:upload&#x27;.&lt;/p&gt;&lt;h2&gt;Common CRM object fields&lt;/h2&gt;&lt;p&gt;All uploaded CRM objects should contain the following common JSON fields. In addition, each uploaded object should contain mandatory and optional fields as specified below for each object type.&lt;/p&gt;&lt;table&gt;    &lt;thead&gt;        &lt;tr&gt;            &lt;th&gt;Name&lt;/th&gt;            &lt;th&gt;Description&lt;/th&gt;            &lt;th&gt;Data Type&lt;/th&gt;            &lt;th&gt;Mandatory&lt;/th&gt;        &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;objectId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;Each object must have a unique id field provided by the CRM.&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;modifiedDate&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The object’s last modification date and time in the CRM in ISO-8601 datetime format, without milliseconds&lt;/td&gt;            &lt;td&gt;datetime&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;lastModified&lt;/span&gt;&lt;b&gt;(Deprecated)&lt;/b&gt;&lt;/td&gt;            &lt;td&gt;&lt;b&gt;Deprecated&lt;/b&gt;. Please use &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;modifiedDate&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;datetime&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;isDeleted&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;\&quot;true\&quot; deletes the object (For objectType&#x3D;BUSINESS_USER deletes also the user mapping. For objectType&#x3D;STAGE sets the stage to inactive). Default &#x3D; \&quot;false\&quot;&lt;/td&gt;            &lt;td&gt;boolean&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;url&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;A full http URL to browse this object in the CRM&lt;/td&gt;            &lt;td&gt;string (Qualified URI)&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;h2&gt;Business User Object&lt;/h2&gt;&lt;p&gt;Gong associates users with the CRM &lt;b&gt;User&lt;/b&gt; entity. Mapping users accurately is essential for Gong to connect users with all their associated objects in the CRM.&lt;/p&gt;&lt;p&gt;Uploading user objects via this API creates a mapping in Gong between the user ID in the CRM system and the user ID in Gong.&lt;/p&gt;&lt;br&gt;&lt;div class&#x3D;&#x27;public-api-important&#x27;&gt;    &lt;b&gt;Important:&lt;/b&gt;    &lt;p&gt;User mapping is important to ensure deals are processed in Gong correctly. Each uploaded deal contains an ownerId field, which contains a user ID from the CRM system.&lt;br&gt;        &lt;b&gt;Gong only processes a deal if this user ID is mapped to a user in Gong who is set to record or import calls.&lt;/b&gt;    &lt;/p&gt;    &lt;p&gt;On initial upload send the complete list of users from the CRM system. On incremental upload send only users that have changed.&lt;/p&gt;&lt;/div&gt;&lt;p&gt;If a user is uploaded after a deal is uploaded:&lt;/p&gt;&lt;ol&gt;    &lt;li&gt;Gong retroactively searches for deals whose ownerId matches the user ID mapping.&lt;/li&gt;    &lt;li&gt;Gong starts to reprocess those matched deals from raw storage into Gong’s main database.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;Gong matches the user from the uploaded JSON to a user in Gong based on the email address.&lt;/p&gt;&lt;div class&#x3D;&#x27;public-api-info&#x27;&gt;    &lt;p&gt;The user mapping will not be created when:&lt;/p&gt;    &lt;ul&gt;        &lt;li&gt;There is no user in Gong with the supplied email address&lt;/li&gt;        &lt;li&gt;Mapping already exists for the supplied email address&lt;/li&gt;    &lt;/ul&gt;&lt;/div&gt;&lt;p&gt;To update an existing mapping:&lt;/p&gt;&lt;ol&gt;    &lt;li&gt;Delete the existing mapping by sending the user with isDeleted&#x3D;true.&lt;/li&gt;    &lt;li&gt;In a separate request send the user with isDeleted&#x3D;false and a new email address, or send a different user for the same email address.&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;Business User JSON object requires the following fields:&lt;/p&gt;&lt;table&gt;    &lt;thead&gt;    &lt;tr&gt;        &lt;th&gt;Name&lt;/th&gt;        &lt;th&gt;Description&lt;/th&gt;        &lt;th&gt;Data Type&lt;/th&gt;        &lt;th&gt;Mandatory&lt;/th&gt;    &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;    &lt;tr&gt;        &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;emailAddress&lt;/span&gt;&lt;/td&gt;        &lt;td&gt;Must match an email address of a user in Gong. Not mandatory when isDeleted &#x3D; true.&lt;/td&gt;        &lt;td&gt;string&lt;/td&gt;        &lt;td&gt;Y&lt;/td&gt;    &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;h3&gt;Example&lt;/h3&gt;&lt;h4&gt;Request&lt;/h4&gt;&lt;code&gt;POST https://api.gong.io/v2/crm/object/entities?clientRequestId&#x3D;1234&amp;integrationId&#x3D;6286478263646&amp;objectType&#x3D;BUSINESS_USER&lt;/code&gt;&lt;br&gt;&lt;br&gt;&lt;code&gt;    {\&quot;objectId\&quot;: \&quot;user1_Id_In_The_CRM\&quot;, \&quot;emailAddress\&quot;: \&quot;john.doe@acme.com\&quot;, \&quot;modifiedDate\&quot;: \&quot;2019-01-03T23:45:57+01:00\&quot;}&lt;br&gt;    {\&quot;objectId\&quot;: \&quot;user2_Id_In_The_CRM\&quot;, \&quot;isDeleted\&quot;: true, \&quot;emailAddress\&quot;: \&quot;john.taylor@acme.com\&quot;, \&quot;modifiedDate\&quot;: \&quot;2019-01-03T23:45:57+01:00\&quot;} // remove user mapping for user user2_Id_In_The_CRM&lt;/code&gt;&lt;h2&gt;Stage Object&lt;/h2&gt;&lt;p&gt;Update the list of stages from the CRM system.&lt;/p&gt;&lt;p&gt;Stages must be uploaded via this API before you upload Deal objects. When you upload your Deal object, make sure that the stage field matches one of the stages you’ve uploaded using this API.&lt;/p&gt;&lt;div class&#x3D;&#x27;public-api-info&#x27;&gt;    &lt;p&gt;The upload stages request should only be sent after:&lt;/p&gt;    &lt;ul&gt;        &lt;li&gt;You have created a new integration.&lt;/li&gt;        &lt;li&gt;There are any changes to the list of stages in the CRM. You can also send a stages update request before any request to the &#x27;/object/entities&#x27; API.&lt;/li&gt;    &lt;/ul&gt;&lt;/div&gt;&lt;p&gt;Stage JSON object requires the following fields:&lt;/p&gt;&lt;table&gt;    &lt;thead&gt;    &lt;tr&gt;        &lt;th&gt;Name&lt;/th&gt;        &lt;th&gt;Description&lt;/th&gt;        &lt;th&gt;Data Type&lt;/th&gt;        &lt;th&gt;Mandatory&lt;/th&gt;    &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;    &lt;tr&gt;        &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;internalName&lt;/span&gt;&lt;/td&gt;        &lt;td&gt;Unique name or unique identifier that identifies the stage in the CRM.&lt;/td&gt;        &lt;td&gt;string&lt;/td&gt;        &lt;td&gt;Y&lt;/td&gt;    &lt;/tr&gt;    &lt;tr&gt;        &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;name&lt;/span&gt;&lt;/td&gt;        &lt;td&gt;Stage name (for display in Gong UI).&lt;/td&gt;        &lt;td&gt;string&lt;/td&gt;        &lt;td&gt;Y&lt;/td&gt;    &lt;/tr&gt;    &lt;tr&gt;        &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;isActive&lt;/span&gt;&lt;/td&gt;        &lt;td&gt;Indicates if the stage is active in the CRM.&lt;/td&gt;        &lt;td&gt;boolean&lt;/td&gt;        &lt;td&gt;Y&lt;/td&gt;    &lt;/tr&gt;    &lt;tr&gt;        &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;sortOrder&lt;/span&gt;&lt;/td&gt;        &lt;td&gt;The order of the stage in the sales process (starting from 1).&lt;/td&gt;        &lt;td&gt;integer&lt;/td&gt;        &lt;td&gt;Y&lt;/td&gt;    &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;h3&gt;Example&lt;/h3&gt;&lt;h4&gt;Request&lt;/h4&gt;&lt;code&gt;POST https://api.gong.io/v2/crm/object/entities?clientRequestId&#x3D;1234&amp;integrationId&#x3D;6286478263646&amp;objectType&#x3D;STAGE&lt;/code&gt;&lt;br&gt;&lt;br&gt;&lt;code&gt;    {\&quot;objectId\&quot;: \&quot;discovery\&quot;, \&quot;modifiedDate\&quot;: \&quot;2019-01-03T23:45:57+01:00\&quot;, \&quot;internalName\&quot;: \&quot;discovery\&quot;, \&quot;name\&quot;: \&quot;Discovery\&quot;, \&quot;isActive\&quot;: true, \&quot;sortOrder\&quot;: 1}&lt;br&gt;    {\&quot;objectId\&quot;: \&quot;won\&quot;, \&quot;modifiedDate\&quot;: \&quot;2019-01-03T23:45:57+01:00\&quot;, \&quot;internalName\&quot;: \&quot;won\&quot;, \&quot;name\&quot;: \&quot;Closed Won\&quot;, \&quot;isActive\&quot;: true, \&quot;sortOrder\&quot;: 5}&lt;/code&gt;&lt;h2&gt;Account Object&lt;/h2&gt;&lt;ul&gt;    &lt;li&gt;The Account object represents an active customer in the CRM system.&lt;/li&gt;    &lt;li&gt;The Account object is used by Gong to connect activities such as emails and calls to their associated account.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;The Deals page displays all the activities in Gong associated with an account as well as account status, contacts, and insights.&lt;/p&gt;&lt;div class&#x3D;&#x27;public-api-info&#x27;&gt;&lt;p&gt;Contacts and Deals are associated with accounts, and their processing in Gong requires the associated account.&lt;/p&gt;&lt;p&gt;In order for Deals to be processed correctly by Gong:&lt;ol&gt;    &lt;li&gt;Upload Accounts.&lt;/li&gt;    &lt;li&gt;Wait 60 seconds.&lt;/li&gt;    &lt;li&gt;Upload Contacts and Deals.&lt;/li&gt;&lt;/ol&gt;&lt;/p&gt;&lt;/div&gt;&lt;div class&#x3D;&#x27;public-api-critical&#x27;&gt;&lt;p&gt;When deals are being processed, the account referenced by Deal.accountId must exist in the Gong database.&lt;br&gt;If it does not exist in the database, the deal will not be processed or displayed in the Deals page and other areas throughout Gong.&lt;/p&gt;&lt;/div&gt;&lt;p&gt;The Account JSON object includes the following fields:&lt;/p&gt;&lt;table&gt;    &lt;thead&gt;        &lt;tr&gt;            &lt;th&gt;Name&lt;/th&gt;            &lt;th&gt;Description&lt;/th&gt;            &lt;th&gt;Data Type&lt;/th&gt;            &lt;th&gt;Mandatory&lt;/th&gt;        &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;name&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;Account name&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;domains&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;Domain names related to the account&lt;/td&gt;            &lt;td&gt;string array&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;h3&gt;Example&lt;/h3&gt;&lt;h4&gt;Request&lt;/h4&gt;&lt;code&gt;POST https://api.gong.io/v2/crm/object/entities?clientRequestId&#x3D;1234&amp;integrationId&#x3D;6286478263646&amp;objectType&#x3D;ACCOUNT&lt;/code&gt;&lt;br&gt;&lt;br&gt;&lt;code&gt;{\&quot;objectId\&quot;: \&quot;5ybyh6n6n65\&quot;, \&quot;modifiedDate\&quot;: \&quot;2019-01-03T23:45:57+01:00\&quot;, \&quot;url\&quot;: \&quot;https://crm.com/accounts/5ybyh6n6n65\&quot;, \&quot;name\&quot;: \&quot;PBR\&quot;, \&quot;domains\&quot;: [\&quot;pbr.com\&quot;, \&quot;pbr.gov\&quot;], \&quot;type\&quot;: \&quot;Investor\&quot;} // account with additional field&lt;br&gt;{\&quot;objectId\&quot;: \&quot;gfjhty756th\&quot;, \&quot;modifiedDate\&quot;: \&quot;2019-01-03T22:45:57Z\&quot;, \&quot;name\&quot;: \&quot;PBR\&quot;, \&quot;domains\&quot;: [\&quot;pbr.com\&quot;, \&quot;pbr.gov\&quot;], \&quot;isDeleted\&quot;: true} // remove account gfjhty756th from Gong&lt;/code&gt;&lt;h2&gt;Contact Object&lt;/h2&gt;&lt;ul&gt;    &lt;li&gt;A contact in Gong is a person with contact details associated with the account.&lt;/li&gt;    &lt;li&gt;Gong uses a contact to match an activity to the correct account.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;The Contact JSON object includes the following fields:&lt;/p&gt;&lt;table&gt;    &lt;thead&gt;        &lt;tr&gt;            &lt;th&gt;Name&lt;/th&gt;            &lt;th&gt;Description&lt;/th&gt;            &lt;th&gt;Data Type&lt;/th&gt;            &lt;th&gt;Mandatory&lt;/th&gt;        &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;accountId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The ID of the contact’s connected account in the CRM&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;emailAddress&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The contact’s main email address&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;firstName&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The contact’s first name&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;lastName&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The contact’s last name&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;title&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The contact’s title (if available)&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;phoneNumber&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The contact’s main phone number.&lt;br&gt;            If Gong is configured to import dialer calls the phoneNumber parameter is mandatory.            &lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y for dialer calls,&lt;br&gt;            N otherwise            &lt;/td&gt;        &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;h3&gt;Example&lt;/h3&gt;&lt;h4&gt;Request&lt;/h4&gt;&lt;code&gt;POST https://api.gong.io/v2/crm/object/entities?clientRequestId&#x3D;1234&amp;integrationId&#x3D;6286478263646&amp;objectType&#x3D;CONTACT&lt;/code&gt;&lt;br&gt;&lt;br&gt;&lt;code&gt;{\&quot;objectId\&quot;: \&quot;5zbwd7n5n65\&quot;, \&quot;modifiedDate\&quot;: \&quot;2019-01-03T23:45:57+01:00\&quot;, \&quot;url\&quot;: \&quot;https://crm.com/contacts/5zbwd7n5n65\&quot;, \&quot;accountId\&quot;: \&quot;5ybyh6n6n65\&quot;, \&quot;emailAddress\&quot;: \&quot;john.smith@acme.com\&quot;, \&quot;firstName\&quot;: \&quot;john\&quot;, \&quot;lastName\&quot;: \&quot;smith\&quot;, \&quot;phoneNumber\&quot;: \&quot;(912) 507-4395\&quot;}&lt;/code&gt;&lt;h2&gt;Lead Object&lt;/h2&gt;&lt;ul&gt;    &lt;li&gt;The Lead object represents a potential customer.&lt;/li&gt;    &lt;li&gt;Calls and emails are first associated with contacts based on email addresses.&lt;/li&gt;    &lt;li&gt;If there is no matching contact, Gong tries to match calls and emails to a lead.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;The Lead JSON object includes the following fields:&lt;/p&gt;&lt;table&gt;    &lt;thead&gt;        &lt;tr&gt;            &lt;th&gt;Name&lt;/th&gt;            &lt;th&gt;Description&lt;/th&gt;            &lt;th&gt;Data Type&lt;/th&gt;            &lt;th&gt;Mandatory&lt;/th&gt;        &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;emailAddress&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The Lead’s main email address&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;firstName&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The Lead’s first name&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;lastName&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The Lead’s last name&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;title&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The Lead’s title (if available)&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;phoneNumber&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The Lead’s phone number.&lt;br&gt;            If Gong is configured to import dialer calls the phoneNumber parameter is mandatory.            &lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y for dialer calls,&lt;br&gt;            N otherwise            &lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;convertedToDealId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The deal CRM ID, if the lead was converted to a Deal&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;convertedToContactId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The contact CRM ID if the lead was converted to a Contact&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;convertedToAccountId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The account CRM ID if the lead was converted to an Account&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;h3&gt;Example&lt;/h3&gt;&lt;h4&gt;Request&lt;/h4&gt;&lt;code&gt;POST https://api.gong.io/v2/crm/object/entities?clientRequestId&#x3D;1234&amp;integrationId&#x3D;6286478263646&amp;objectType&#x3D;LEAD&lt;/code&gt;&lt;br&gt;&lt;br&gt;&lt;code&gt;{\&quot;objectId\&quot;: \&quot;4v5bt54t553\&quot;, \&quot;modifiedDate\&quot;: \&quot;2019-01-03T23:45:57+01:00\&quot;, \&quot;url\&quot;: \&quot;https://crm.com/leads/45k4j5j5k44\&quot;, \&quot;emailAddress\&quot;: \&quot;jane.doe@acme.com\&quot;, \&quot;firstName\&quot;: \&quot;Jane\&quot;, \&quot;lastName\&quot;: \&quot;Doe\&quot;, \&quot;title\&quot;: \&quot;VP Special Effects\&quot;, \&quot;phoneNumber\&quot;: \&quot;(912) 507-4395\&quot;}&lt;br&gt;{\&quot;objectId\&quot;: \&quot;gf4543gf6th\&quot;, \&quot;modifiedDate\&quot;: \&quot;2019-01-03T22:45:57Z\&quot;, \&quot;emailAddress\&quot;: \&quot;john.smith@acme.com\&quot;, \&quot;firstName\&quot;: \&quot;John\&quot;, \&quot;lastName\&quot;: \&quot;Smith\&quot;, \&quot;isDeleted\&quot;: true} // remove lead gf4543gf6th&lt;br&gt;{\&quot;objectId\&quot;: \&quot;63473hjg53h\&quot;, \&quot;modifiedDate\&quot;: \&quot;2019-01-03T23:45:57+01:00\&quot;, \&quot;emailAddress\&quot;: \&quot;bob.smith@acme.com\&quot;, \&quot;firstName\&quot;: \&quot;Bob\&quot;, \&quot;lastName\&quot;: \&quot;Smith\&quot;, \&quot;convertedToDealId\&quot;: \&quot;dkfj8dfgf87\&quot;, \&quot;convertedToContactId\&quot;: \&quot;87grhn74hg6\&quot;, \&quot;convertedToAccountId\&quot;: \&quot;6sjk47jf78d\&quot;} // lead 63473hjg53h converted to account 6sjk47jf78d, contact 87grhn74hg6 and deal dkfj8dfgf87&lt;/code&gt;&lt;h2&gt;Deal Object&lt;/h2&gt;&lt;p&gt;A deal in Gong represents a qualified opportunity or contract in a specific account.&lt;/p&gt;&lt;p&gt;The Deal JSON object includes the following fields:&lt;/p&gt;&lt;table&gt;    &lt;thead&gt;        &lt;tr&gt;            &lt;th&gt;Name&lt;/th&gt;            &lt;th&gt;Description&lt;/th&gt;            &lt;th&gt;Data Type&lt;/th&gt;            &lt;th&gt;Mandatory&lt;/th&gt;        &lt;/tr&gt;    &lt;/thead&gt;    &lt;tbody&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;accountId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;            &lt;p&gt;The ID of the account the deal is associated with in the CRM&lt;/p&gt;            &lt;div class&#x3D;&#x27;public-api-info&#x27;&gt;                &lt;p&gt;An account with the same objectId must be uploaded first in order for the deal to be processed. The accountId needs to match an Account with the same value in its objectId.&lt;/p&gt;            &lt;/div&gt;            &lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;ownerId&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;            &lt;p&gt;The ID of the owning User in the CRM&lt;/p&gt;            &lt;div class&#x3D;&#x27;public-api-info&#x27;&gt;                &lt;p&gt;This field is a reference to a CRM user which must be mapped to a Gong user via \&quot;/map/users\&quot; API and the Gong user must be set to record or import calls, otherwise the deal will not be processed&lt;/p&gt;            &lt;/div&gt;            &lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;name&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The deal’s name&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;createdDate&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The deal’s creation date and time (ISO-8601 datetime without milliseconds)&lt;/td&gt;            &lt;td&gt;datetime&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;estimatedCloseDate&lt;/span&gt;*&lt;b&gt;(Deprecated)&lt;/b&gt;&lt;/td&gt;            &lt;td&gt;&lt;b&gt;Deprecated&lt;/b&gt;. Please use &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;closeDate&lt;/span&gt; instead&lt;/td&gt;            &lt;td&gt;date&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;actualCloseDate&lt;/span&gt;*&lt;b&gt;(Deprecated)&lt;/b&gt;&lt;/td&gt;            &lt;td&gt;&lt;b&gt;Deprecated&lt;/b&gt;. Please use &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;closeDate&lt;/span&gt; instead&lt;/td&gt;            &lt;td&gt;date&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;closeDate&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The deal’s close date (ISO-8601), without time e.g. \&quot;2021-05-19\&quot;&lt;/td&gt;            &lt;td&gt;date&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;isOpen&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;Indicates if the Deal’s status is Open or Closed&lt;/td&gt;            &lt;td&gt;boolean&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;isWon&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;Indicates if the Deal’s status is Won or Lost&lt;/td&gt;            &lt;td&gt;boolean&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;stage&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The value of this field must be equal to the internalName of one of the stages uploaded via \&quot;/stages\&quot; API&lt;/td&gt;            &lt;td&gt;string&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;estimatedAmount&lt;/span&gt;**&lt;b&gt;(Deprecated)&lt;/b&gt;&lt;/td&gt;            &lt;td&gt;&lt;b&gt;Deprecated&lt;/b&gt;. Please use &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;amount&lt;/span&gt; instead&lt;/td&gt;            &lt;td&gt;currency&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;actualAmount&lt;/span&gt;**&lt;b&gt;(Deprecated)&lt;/b&gt;&lt;/td&gt;            &lt;td&gt;&lt;b&gt;Deprecated&lt;/b&gt;. Please use &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;amount&lt;/span&gt; instead&lt;/td&gt;            &lt;td&gt;currency&lt;/td&gt;            &lt;td&gt;N&lt;/td&gt;        &lt;/tr&gt;        &lt;tr&gt;            &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;amount&lt;/span&gt;&lt;/td&gt;            &lt;td&gt;The deal’s amount in the currency unit&lt;/td&gt;            &lt;td&gt;currency&lt;/td&gt;            &lt;td&gt;Y&lt;/td&gt;        &lt;/tr&gt;    &lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;* Either &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;estimatedCloseDate&lt;/span&gt; or &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;actualCloseDate&lt;/span&gt; (or both) must exist in the JSON&lt;br&gt;** Either &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;estimatedAmount&lt;/span&gt; or &lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;actualAmount&lt;/span&gt; (or both) must exist in the JSON&lt;/p&gt;&lt;h3&gt;Example&lt;/h3&gt;&lt;h4&gt;Request&lt;/h4&gt;&lt;code&gt;POST https://api.gong.io/v2/crm/object/entities?clientRequestId&#x3D;1234&amp;integrationId&#x3D;6286478263646&amp;objectType&#x3D;DEAL&lt;/code&gt;&lt;br&gt;&lt;br&gt;&lt;code&gt;{\&quot;objectId\&quot;: \&quot;8608553\&quot;, \&quot;modifiedDate\&quot;: \&quot;2022-02-04T18:24:59Z\&quot;, \&quot;url\&quot;: \&quot;http://crm.com/deals/8608553\&quot;, \&quot;accountId\&quot;: \&quot;5ybyh6n6n65\&quot;, \&quot;ownerId\&quot;: \&quot;5486951\&quot;, \&quot;name\&quot;: \&quot;Deal name\&quot;, \&quot;createdDate\&quot;: \&quot;2022-02-04T17:57:23Z\&quot;, \&quot;closeDate\&quot;: \&quot;2022-09-04\&quot;, \&quot;isOpen\&quot;: true, \&quot;isWon\&quot;: false, \&quot;stage\&quot;: \&quot;discovery\&quot;, \&quot;amount\&quot;: 7000, \&quot;custom_field_1\&quot;: \&quot;2022-02-04T17:57:23.000Z\&quot;, \&quot;custom_field_2\&quot;: null}&lt;/code&gt;&lt;h2&gt;Additional Fields&lt;/h2&gt;&lt;p&gt;In addition to the fields required by Gong, you can also add any other field to each object if the following two conditions are met:&lt;ul&gt;    &lt;li&gt;The field name is defined in the object&#x27;s schema and has been uploaded using \&quot;/object/schema\&quot; API&lt;/li&gt;    &lt;li&gt;The field value matches the type defined in the schema&lt;/li&gt;&lt;/ul&gt;&lt;/p&gt;
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :data_file 
+  # @return [AsyncProcessingResponse]
+  describe 'upload_crm_data_using_post test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for upload_crm_schema_field_using_post
+  # Upload Object Schema (/v2/crm/object/schema)
+  # &lt;style&gt;.public-api-info {    background: rgb(222, 235, 255);}.public-api-tip {    background: rgb(227, 252, 239);}.public-api-parameter {    background: rgba(9,30,66,0.08);}.public-api-note {    background: rgb(234, 230, 255);}.public-api-important {    background: rgb(255, 250, 230);}.public-api-critical {    background: rgb(255, 235, 230);}table, th, td {  border: 1px solid gray;  border-collapse: collapse;}th, td {  padding: 5px;}th {  text-align: left;}&lt;/style&gt;&lt;p&gt;All CRM object fields in Gong must have a representative schema that describes the field (unique name, type, etc.). &lt;br&gt;Any field uploaded by the \&quot;Upload CRM objects\&quot; API (\&quot;/object/entities\&quot; path) that is not described in the schema will be stored in Gong’s raw data storage. However, it will not be parsed by Gong and it will not be available to the end user.&lt;/p&gt;&lt;p&gt;For new integrations created via \&quot;/integration/new\&quot; API, Gong creates a default schema for each object type (Contact, Account, Deal, Lead) that contains the mandatory and optional fields specified in this guide. See the &lt;b&gt;Upload CRM objects&lt;/b&gt; API section for more information.&lt;br&gt;If there are additional fields for any object type that are needed by the end user, send their schema via this API.&lt;/p&gt;&lt;p&gt;&lt;div class&#x3D;&#x27;public-api-info&#x27;&gt;The schema update request should be sent when:&lt;ul&gt;    &lt;li&gt;You have created a new integration.&lt;/li&gt;    &lt;li&gt;There are changes to the schema of any object type. You can also send a schema update request before any request to the &#x27;/object/entities&#x27; API.&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;div class&#x3D;&#x27;public-api-important&#x27;&gt;Each schema update request must contain the full schema from your CRM. Fields that were sent in previous requests and no longer exist in your CRM, should be sent in the schema request with \&quot;isDeleted&#x3D;true\&quot; (only once).&lt;/div&gt;&lt;/p&gt;&lt;p&gt;When accessed using a bearer token, this endpoint requires the scope &#x27;api:crm:schema&#x27;.&lt;/p&gt;&lt;h3&gt;Supported Field Types&lt;/h3&gt;&lt;table&gt;  &lt;thead&gt;  &lt;tr&gt;    &lt;th&gt;Field Type&lt;/th&gt;    &lt;th&gt;Format in JSON&lt;/th&gt;    &lt;th&gt;Sample Values&lt;/th&gt;  &lt;/tr&gt;  &lt;/thead&gt;  &lt;tbody&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;BOOLEAN&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;boolean&lt;/td&gt;    &lt;td&gt;true, false&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;DATE&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;string (ISO-8601 date without time)&lt;/td&gt;    &lt;td&gt;\&quot;2020-05-31\&quot;&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;DATETIME&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;string (ISO-8601 datetime without milliseconds)&lt;/td&gt;    &lt;td&gt;\&quot;2020-12-17T07:37:21+02:00\&quot;&lt;br&gt;\&quot;2020-12-17T05:37:21Z\&quot;&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;PICKLIST&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;string - one of the values in an orderedValueList&lt;/td&gt;    &lt;td&gt;\&quot;Analyst\&quot;&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;NUMBER&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;number&lt;/td&gt;    &lt;td&gt;45.66, 8453&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;PERCENT&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;number (between 0 to 100)&lt;/td&gt;    &lt;td&gt;67.3&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;CURRENCY&lt;/span&gt;*&lt;/td&gt;    &lt;td&gt;number&lt;/td&gt;    &lt;td&gt;34.68&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;PHONENUMBER&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;string&lt;/td&gt;    &lt;td&gt;\&quot;+14055766687\&quot;&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;EMAILADDRESS&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;string&lt;/td&gt;    &lt;td&gt;\&quot;john.doe@anywhere.com\&quot;&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;REFERENCE&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;string - the id of another object&lt;/td&gt;    &lt;td&gt;\&quot;48b009drax\&quot;&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;ID&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;string - the id of the object&lt;/td&gt;    &lt;td&gt;\&quot;843hf8484jr84htg\&quot;&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;STRING&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;string&lt;/td&gt;    &lt;td&gt;\&quot;whatever you want\&quot;&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;STRINGARRAY&lt;/span&gt;**&lt;/td&gt;    &lt;td&gt;array of strings&lt;/td&gt;    &lt;td&gt;[\&quot;http://customer.com\&quot;]&lt;/td&gt;  &lt;/tr&gt;  &lt;tr&gt;    &lt;td&gt;&lt;span class&#x3D;&#x27;public-api-parameter&#x27;&gt;URL&lt;/span&gt;&lt;/td&gt;    &lt;td&gt;string&lt;/td&gt;    &lt;td&gt;\&quot;https://crm.com/account/6d4r578f\&quot;&lt;/td&gt;  &lt;/tr&gt;  &lt;/tbody&gt;&lt;/table&gt;&lt;p&gt;* In the integration send a number value, and specify the correct currency symbol in the Gong UI. Currently  Gong does not support multiple currencies per company.&lt;br&gt;** Can only be used for Gong-defined fields.&lt;/p&gt;&lt;h3&gt;Example&lt;/h3&gt;&lt;h4&gt;Request&lt;/h4&gt;&lt;code&gt;POST https://api.gong.io/v2/crm/object/schema?integrationId&#x3D;6286478263646&amp;objectType&#x3D;ACCOUNT&lt;/code&gt;&lt;br&gt;&lt;br&gt;&lt;code&gt;[{\&quot;uniqueName\&quot;: \&quot;orderId\&quot;, \&quot;label\&quot;: \&quot;ID\&quot;, \&quot;type\&quot;: \&quot;ID\&quot;, \&quot;lastModified\&quot;: \&quot;2020-11-11T08:11:34+01:00\&quot;},&lt;br&gt;{\&quot;uniqueName\&quot;: \&quot;parentAccount\&quot;, \&quot;label\&quot;: \&quot;Main Account\&quot;, \&quot;type\&quot;: \&quot;REFERENCE\&quot;, \&quot;referenceTo\&quot;: \&quot;ACCOUNT\&quot;, \&quot;lastModified\&quot;: \&quot;2020-11-11T08:11:34+01:00\&quot;},&lt;br&gt;{\&quot;uniqueName\&quot;: \&quot;category\&quot;, \&quot;label\&quot;: \&quot;Category\&quot;, \&quot;type\&quot;: \&quot;PICKLIST\&quot;, \&quot;orderedValueList\&quot;: [\&quot;Analyst\&quot;, \&quot;Competitor\&quot;, \&quot;Customer\&quot;, \&quot;Integrator\&quot;, \&quot;Investor\&quot;, \&quot;Partner\&quot;, \&quot;Other\&quot;], \&quot;lastModified\&quot;: \&quot;2020-11-11T08:11:34+01:00\&quot;}, // custom field&lt;br&gt;{\&quot;uniqueName\&quot;: \&quot;industry\&quot;, \&quot;isDeleted\&quot;: true, \&quot;lastModified\&quot;: \&quot;2020-11-21T08:11:34+01:00\&quot;}] // remove custom field&lt;/code&gt;
+  # @param body fields
+  # @param integration_id Integration ID generated when creating the integration
+  # @param object_type Type of object to set the schema for (case-sensitive)
+  # @param [Hash] opts the optional parameters
+  # @return [SchemaUpdateResponse]
+  describe 'upload_crm_schema_field_using_post test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for upload_stages_using_post
+  # Upload Stages (Deprecated)
+  # &lt;style&gt;.public-api-info {    background: rgb(222, 235, 255);}.public-api-tip {    background: rgb(227, 252, 239);}.public-api-parameter {    background: rgba(9,30,66,0.08);}.public-api-note {    background: rgb(234, 230, 255);}.public-api-important {    background: rgb(255, 250, 230);}.public-api-critical {    background: rgb(255, 235, 230);}table, th, td {  border: 1px solid gray;  border-collapse: collapse;}th, td {  padding: 5px;}th {  text-align: left;}&lt;/style&gt;&lt;p&gt;This API is &lt;b&gt;Deprecated&lt;/b&gt;. Please use \&quot;/object/entities?objectType&#x3D;STAGE\&quot; API instead.&lt;/p&gt;&lt;p&gt;Update the list of stages from the CRM system.&lt;/p&gt;&lt;p&gt;This API must be called before you upload Deal objects. When you upload your Deal object, make sure that the stage field matches one of the stages you’ve uploaded using this API.&lt;/p&gt;&lt;div class&#x3D;&#x27;public-api-info&#x27;&gt;&lt;p&gt;The upload stages request should only be sent after:&lt;/p&gt;&lt;ul&gt;    &lt;li&gt;You have created a new integration.&lt;/li&gt;    &lt;li&gt;There are any changes to the list of stages in the CRM. You can also send a stages update request before any request to the &#x27;/object/entities&#x27; API.&lt;/li&gt;&lt;/ul&gt;&lt;/div&gt;&lt;p&gt;When accessed using a bearer token, this endpoint requires the scope &#x27;api:crm:schema&#x27;.&lt;/p&gt;
+  # @param body stages
+  # @param integration_id Integration ID generated when creating the integration
+  # @param [Hash] opts the optional parameters
+  # @return [SchemaUpdateResponse]
+  describe 'upload_stages_using_post test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/api/data_privacy_api_spec.rb

@@ -0,0 +1,82 @@
+=begin
+#Gong API
+
+#<h2>Overview</h2> <p> The Gong API allows you to: </p> <ol> <li> Receive the following information from Gong: <ol type=\"a\"> <li> Your company's <a href=\"#tag--Calls\">calls</a> in Gong </li> <li> Your company's <a href=\"#tag--Users\">users</a> in Gong </li> <li> Your company's user <a href=\"#tag--Stats\">stats</a> in Gong </li> <li> Your company's user <a href=\"#tag--Settings\">settings</a> in Gong </li> <li> Your company's <a href=\"#tag--Library\">libraries</a> in Gong </li> </ol></li> <li> <a href=\"#post-/v2/calls\">Upload</a> new or  <a href=\"#put-/v2/calls/-id-/media\">update</a>  call recordings in Gong, in order to support cases where you have an internal system that records  calls or obtains them from a third-party entity. </li> <li> <a href=\"#post-/v2/data-privacy/erase-data-for-email-address\">Data Privacy</a>:  Delete users and all their associated elements.</li> <li> Upload <a href=\"#tag--CRM\">CRM</a> data into Gong.  </li> </ol> <p>Base URL for all API calls is <a href=\"https://us-55616.api.gong.io\"> https://us-55616.api.gong.io </a> </p> <h2>Authentication</h2>  <p> There are two ways to retrieve credentials to the Gong Public API: </p> <ol><li>Retrieve Manually:<br> <p> In the <a href=\"https://app.gong.io/company/api\">Gong API Page</a> (you must be a technical administrator in Gong), click \"Create\" to receive an <b>Access Key</b>  and an <b>Access Key Secret</b>.<br> </p> <p> Use the Basic Authorization HTTP header (as per <a target=\"_blank\" href=\"https://www.rfc-editor.org/rfc/rfc7617.txt\">RFC</a>) to access the Public API as shown below:<br> <code>Authorization: Basic &lt;token&gt;</code><br> </p> <p> To create the basic token, combine the <b>Access Key</b> and the <b>Access Key Secret</b> with  colon (:) and then encode in Base64 as following:<br> <code>Base64(&lt;accessKey&gt; : &lt;accessKeySecret&gt;)</code><br><br> </p></li> <li>Retrieve through OAuth<br> <p> To obtain the Bearer token, follow the steps described in the <a target=\"_blank\" href=\"https://help.gong.io/hc/en-us/articles/360056677792\">Gong OAuth Guide</a>. <br></p> <p> After obtaining the token, use the Bearer Authorization HTTP header (as per <a target=\"_blank\" href=\"https://www.rfc-editor.org/rfc/rfc6750.txt\">RFC</a>) to access the Public API as shown below:<br> <code>Authorization: Bearer &lt;token&gt;</code> </p> </li></ol> <h2>Limits</h2>  <p> By default Gong limits your company's access to the service to 3 API calls per second, and 10,000 API calls per day. </p> <p> When the rate of API calls exceeds these limits an HTTP status code <b>429</b> is returned and a <b>Retry-After</b> header indicates  how many seconds to wait before making a new request. </p><p> If required, contact help@gong.io to change these limits. </p>  <h2>Cursors</h2>  <p> Some API calls that return a list are limited in the amount of records they may return, so multiple API calls may be  required to bring all records. Such an API call also returns a <b>records</b> field, which contains the number of records  in the current page, the current page number and the total number of records. </p> <p> In cases where the total number of records exceeds the number of records thus far retrieved, the <b>records</b> field will also  contain a <b>cursor</b> field which can be used to access the next page of records. To retrieve the next page, repeat the API call with  the <b>cursor</b> value as supplied by the previous API call. All other request inputs should remain the same. </p> <h2>Forward Compatibility</h2>  <p> When coding a system to accept Gong data, take into account that Gong may, without prior warning, add fields to the JSON output.  It is recommended to future proof your code so that it disregards all JSON fields you don't actually use.  </p><p></p>
+
+OpenAPI spec version: V2
+
+Generated by: https://github.com/swagger-api/swagger-codegen.git
+Swagger Codegen version: 3.0.37
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for GongAPI::DataPrivacyApi
+# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen)
+# Please update as you see appropriate
+describe 'DataPrivacyApi' do
+  before do
+    # run before each test
+    @instance = GongAPI::DataPrivacyApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of DataPrivacyApi' do
+    it 'should create an instance of DataPrivacyApi' do
+      expect(@instance).to be_instance_of(GongAPI::DataPrivacyApi)
+    end
+  end
+
+  # unit tests for find_all_references_to_email_address_using_get
+  # Retrieve all references to an email address. (/v2/data-privacy/data-for-email-address)
+  # Shows the elements in the Gong system that reference the given email address. Given an emails address, this endpoint returns details of all calls and email messages that reference this address, and any leads or contacts with this email address.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:data-privacy:read&#x27;.
+  # @param email_address The email address.
+  # @param [Hash] opts the optional parameters
+  # @return [EmailAddressReferences]
+  describe 'find_all_references_to_email_address_using_get test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for find_all_references_to_phone_number_using_get
+  # Retrieve all references to a phone number. (/v2/data-privacy/data-for-phone-number)
+  # Shows the elements in the Gong system that reference the given phone number. Given a phone number, this endpoint returns details of any leads or contacts with this phone number and their associated calls and email messages.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:data-privacy:read&#x27;.
+  # @param phone_number The phone number.  This number must start with a + (plus) sign followed by the country code, area code, and local phone number. All other non-digits are ignored.  The following are examples of permitted phone numbers: +1 425 555 2671, +1-425-555-2671, +1 425 5552671, +14255552671, +1 425 555 26 71, +1(425) 555-2671, etc.  Note: This parameter should be URL-encoded.
+  # @param [Hash] opts the optional parameters
+  # @return [PhoneNumberReferences]
+  describe 'find_all_references_to_phone_number_using_get test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for purge_email_address_using_post
+  # Delete the email address, and all associated elements (/v2/data-privacy/erase-data-for-email-address)
+  # Given an email address, this endpoint deletes from the Gong system any calls or email messages that reference this address. Email messages sent to or from the address are deleted. Calls where the email address appears (as a lead, contact, attendee or speaker) are deleted. Leads or Contacts with the email address are deleted. The deletion is not immediate, and may take several hours to complete.  This endpoint contains a data integrity protection mechanism to prevent the deletion of an abnormal number of objects. If the deletion fails please contact support at help@gong.io  Delete the data from your CRM and email system before performing this operation so that private data is not re-imported into Gong.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:data-privacy:delete&#x27;.
+  # @param email_address The email address.
+  # @param [Hash] opts the optional parameters
+  # @return [BaseResponse]
+  describe 'purge_email_address_using_post test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for purge_phone_number_using_post
+  # Delete the phone number, and all associated elements (/v2/data-privacy/erase-data-for-phone-number)
+  # Given a phone number, this endpoint deletes from the Gong system any leads or contacts with a matching phone number or mobile phone number. Email messages sent to or from these leads/contacts are deleted. Calls where the leads/contacts appear are deleted. The deletion is not immediate, and may take several hours to complete.  This endpoint contains a data integrity protection mechanism to prevent the deletion of an abnormal number of objects. If the deletion fails please contact support at help@gong.io  Delete the data from your CRM and email system before performing this operation so that private data is not re-imported into Gong.  When accessed through a Bearer token authorization method, this endpoint requires the scope &#x27;api:data-privacy:delete&#x27;.
+  # @param phone_number The phone number.  This number must start with a + (plus) sign followed by the country code, area code, and local phone number. All other non-digits are ignored.  The following are examples of permitted phone numbers: +1 425 555 2671, +1-425-555-2671, +1 425 5552671, +14255552671, +1 425 555 26 71, +1(425) 555-2671, etc.  Note: This parameter should be URL-encoded.
+  # @param [Hash] opts the optional parameters
+  # @return [BaseResponse]
+  describe 'purge_phone_number_using_post test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end