gong_api 1.0.0 → 1.1.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (361) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile +1 -7
  3. data/Gemfile.lock +69 -0
  4. data/README.md +72 -15
  5. data/config.json +3 -3
  6. data/docs/CallsApi.md +5 -5
  7. data/docs/UsersApi.md +5 -5
  8. data/gong_api.gemspec +6 -4
  9. data/lib/gong_api/api/auditing_api.rb +1 -1
  10. data/lib/gong_api/api/calls_api.rb +8 -8
  11. data/lib/gong_api/api/crm_api.rb +1 -1
  12. data/lib/gong_api/api/data_privacy_api.rb +1 -1
  13. data/lib/gong_api/api/engagement_in_beta_phase_api.rb +1 -1
  14. data/lib/gong_api/api/library_api.rb +1 -1
  15. data/lib/gong_api/api/meetings_in_beta_phase_api.rb +1 -1
  16. data/lib/gong_api/api/permissions_api.rb +1 -1
  17. data/lib/gong_api/api/settings_api.rb +1 -1
  18. data/lib/gong_api/api/stats_api.rb +1 -1
  19. data/lib/gong_api/api/users_api.rb +6 -6
  20. data/lib/gong_api/api_client.rb +1 -1
  21. data/lib/gong_api/api_error.rb +1 -2
  22. data/lib/gong_api/configuration.rb +2 -3
  23. data/lib/gong_api/models/actor.rb +1 -1
  24. data/lib/gong_api/models/aggregate_activity.rb +1 -1
  25. data/lib/gong_api/models/aggregate_activity_with_dates.rb +1 -1
  26. data/lib/gong_api/models/answer.rb +1 -1
  27. data/lib/gong_api/models/answered_scorecard.rb +1 -1
  28. data/lib/gong_api/models/answered_scorecards.rb +1 -1
  29. data/lib/gong_api/models/answered_scorecards_filter.rb +1 -1
  30. data/lib/gong_api/models/association_object.rb +1 -1
  31. data/lib/gong_api/models/async_processing_response.rb +1 -1
  32. data/lib/gong_api/models/base_response.rb +1 -1
  33. data/lib/gong_api/models/call.rb +1 -1
  34. data/lib/gong_api/models/call_access_details.rb +1 -1
  35. data/lib/gong_api/models/call_access_with_permission_level.rb +1 -1
  36. data/lib/gong_api/models/call_basic_data.rb +1 -1
  37. data/lib/gong_api/models/call_collaboration.rb +1 -1
  38. data/lib/gong_api/models/call_content.rb +1 -1
  39. data/lib/gong_api/models/call_context.rb +1 -1
  40. data/lib/gong_api/models/call_interaction.rb +1 -1
  41. data/lib/gong_api/models/call_participant.rb +1 -1
  42. data/lib/gong_api/models/call_reference.rb +1 -1
  43. data/lib/gong_api/models/call_transcript.rb +1 -1
  44. data/lib/gong_api/models/call_transcripts.rb +1 -1
  45. data/lib/gong_api/models/call_upload_context.rb +1 -1
  46. data/lib/gong_api/models/call_users_access_dto.rb +1 -1
  47. data/lib/gong_api/models/calls.rb +1 -1
  48. data/lib/gong_api/models/calls_access_details_response.rb +1 -1
  49. data/lib/gong_api/models/calls_access_get_dto.rb +1 -1
  50. data/lib/gong_api/models/calls_filter.rb +1 -1
  51. data/lib/gong_api/models/calls_request_filter_with_owners.rb +1 -1
  52. data/lib/gong_api/models/calls_response.rb +1 -1
  53. data/lib/gong_api/models/calls_users_access_add_dto.rb +1 -1
  54. data/lib/gong_api/models/calls_users_access_delete_dto.rb +1 -1
  55. data/lib/gong_api/models/coaching_access_with_permission_level.rb +1 -1
  56. data/lib/gong_api/models/collaboration.rb +1 -1
  57. data/lib/gong_api/models/comment.rb +1 -1
  58. data/lib/gong_api/models/company_users_aggregate_activity_response.rb +1 -1
  59. data/lib/gong_api/models/company_users_intercation_stats_response.rb +1 -1
  60. data/lib/gong_api/models/content.rb +1 -1
  61. data/lib/gong_api/models/content_selector.rb +1 -1
  62. data/lib/gong_api/models/content_shared_event.rb +1 -1
  63. data/lib/gong_api/models/content_viewed_event.rb +1 -1
  64. data/lib/gong_api/models/context_field.rb +1 -1
  65. data/lib/gong_api/models/crm_party_context_field.rb +1 -1
  66. data/lib/gong_api/models/custom_action_event.rb +1 -1
  67. data/lib/gong_api/models/customer_data.rb +1 -1
  68. data/lib/gong_api/models/customer_data_object.rb +1 -1
  69. data/lib/gong_api/models/customer_engagement.rb +1 -1
  70. data/lib/gong_api/models/daily_activity_with_dates.rb +1 -1
  71. data/lib/gong_api/models/deals_access_with_permission_level.rb +1 -1
  72. data/lib/gong_api/models/delete_meeting_request.rb +1 -1
  73. data/lib/gong_api/models/email_address_references.rb +1 -1
  74. data/lib/gong_api/models/email_message.rb +1 -1
  75. data/lib/gong_api/models/emails_access_with_permission_level.rb +1 -1
  76. data/lib/gong_api/models/error_response.rb +1 -1
  77. data/lib/gong_api/models/event_accepted_response.rb +1 -1
  78. data/lib/gong_api/models/exposed_fields.rb +1 -1
  79. data/lib/gong_api/models/external_call_object.rb +8 -8
  80. data/lib/gong_api/models/external_crm_call_object.rb +11 -11
  81. data/lib/gong_api/models/external_crm_party_object.rb +11 -11
  82. data/lib/gong_api/models/external_party_object.rb +8 -8
  83. data/lib/gong_api/models/external_system.rb +1 -1
  84. data/lib/gong_api/models/external_system_object.rb +1 -1
  85. data/lib/gong_api/models/forecast_access_with_permission_level.rb +1 -1
  86. data/lib/gong_api/models/generic_crm_integration.rb +1 -1
  87. data/lib/gong_api/models/generic_crm_registration_request.rb +1 -1
  88. data/lib/gong_api/models/generic_deal_stage_request.rb +1 -1
  89. data/lib/gong_api/models/generic_property.rb +1 -1
  90. data/lib/gong_api/models/generic_schema_field_request.rb +1 -1
  91. data/lib/gong_api/models/get_generic_crm_objects_response.rb +1 -1
  92. data/lib/gong_api/models/id_media_body.rb +1 -1
  93. data/lib/gong_api/models/insights_access_with_permission_level.rb +1 -1
  94. data/lib/gong_api/models/integration_status_request.rb +1 -1
  95. data/lib/gong_api/models/integration_status_response.rb +1 -1
  96. data/lib/gong_api/models/interaction.rb +1 -1
  97. data/lib/gong_api/models/interaction_stat.rb +1 -1
  98. data/lib/gong_api/models/interaction_stats.rb +1 -1
  99. data/lib/gong_api/models/library_call.rb +1 -1
  100. data/lib/gong_api/models/library_folder.rb +1 -1
  101. data/lib/gong_api/models/library_folder_access.rb +1 -1
  102. data/lib/gong_api/models/library_folder_list_of_calls_response.rb +1 -1
  103. data/lib/gong_api/models/library_response.rb +1 -1
  104. data/lib/gong_api/models/line_error_response.rb +1 -1
  105. data/lib/gong_api/models/list_generic_crm_integrations_response.rb +1 -1
  106. data/lib/gong_api/models/list_selected_fields_response.rb +1 -1
  107. data/lib/gong_api/models/log_entry.rb +1 -1
  108. data/lib/gong_api/models/logs_response.rb +1 -1
  109. data/lib/gong_api/models/manual_association_response.rb +1 -1
  110. data/lib/gong_api/models/manual_associations_basic_data.rb +1 -1
  111. data/lib/gong_api/models/map_users_body.rb +1 -1
  112. data/lib/gong_api/models/media.rb +1 -1
  113. data/lib/gong_api/models/meeting.rb +1 -1
  114. data/lib/gong_api/models/meeting_invitee.rb +1 -1
  115. data/lib/gong_api/models/meetings_error_response.rb +1 -1
  116. data/lib/gong_api/models/monologue.rb +1 -1
  117. data/lib/gong_api/models/multiple_users_request_with_creation_dates.rb +1 -1
  118. data/lib/gong_api/models/multiple_users_with_dates.rb +1 -1
  119. data/lib/gong_api/models/new_call_adding_request.rb +1 -1
  120. data/lib/gong_api/models/new_call_adding_response.rb +1 -1
  121. data/lib/gong_api/models/new_call_recording_response.rb +1 -1
  122. data/lib/gong_api/models/new_meeting_request.rb +1 -1
  123. data/lib/gong_api/models/new_meeting_response.rb +1 -1
  124. data/lib/gong_api/models/object_entities_body.rb +1 -1
  125. data/lib/gong_api/models/occurrences.rb +1 -1
  126. data/lib/gong_api/models/party.rb +1 -1
  127. data/lib/gong_api/models/party_context.rb +1 -1
  128. data/lib/gong_api/models/party_context_field.rb +1 -1
  129. data/lib/gong_api/models/party_upload_context.rb +1 -1
  130. data/lib/gong_api/models/permission_profile_dto.rb +1 -1
  131. data/lib/gong_api/models/permission_profile_response.rb +1 -1
  132. data/lib/gong_api/models/permission_profile_users_response.rb +1 -1
  133. data/lib/gong_api/models/permission_profiles_response.rb +1 -1
  134. data/lib/gong_api/models/phone_number_references.rb +1 -1
  135. data/lib/gong_api/models/point_of_interest.rb +1 -1
  136. data/lib/gong_api/models/points_of_interest.rb +1 -1
  137. data/lib/gong_api/models/question.rb +1 -1
  138. data/lib/gong_api/models/questions.rb +1 -1
  139. data/lib/gong_api/models/records.rb +1 -1
  140. data/lib/gong_api/models/register_generic_crm_response.rb +1 -1
  141. data/lib/gong_api/models/request_answered_scorecards_filter.rb +1 -1
  142. data/lib/gong_api/models/request_calls_access_get_dto.rb +1 -1
  143. data/lib/gong_api/models/request_calls_filter.rb +1 -1
  144. data/lib/gong_api/models/request_calls_request_filter_with_owners_content_selector.rb +1 -1
  145. data/lib/gong_api/models/request_multiple_users_request_with_creation_dates.rb +1 -1
  146. data/lib/gong_api/models/request_multiple_users_with_dates.rb +1 -1
  147. data/lib/gong_api/models/request_status_response.rb +1 -1
  148. data/lib/gong_api/models/request_with_time_period_multiple_users_with_dates.rb +1 -1
  149. data/lib/gong_api/models/schema_update_response.rb +1 -1
  150. data/lib/gong_api/models/scorecard.rb +1 -1
  151. data/lib/gong_api/models/scorecards.rb +1 -1
  152. data/lib/gong_api/models/sentence.rb +1 -1
  153. data/lib/gong_api/models/settings.rb +1 -1
  154. data/lib/gong_api/models/settings_history.rb +1 -1
  155. data/lib/gong_api/models/sharer.rb +1 -1
  156. data/lib/gong_api/models/snippet.rb +1 -1
  157. data/lib/gong_api/models/speaker.rb +1 -1
  158. data/lib/gong_api/models/speakers_timeline.rb +1 -1
  159. data/lib/gong_api/models/specific_call.rb +1 -1
  160. data/lib/gong_api/models/speech_segment.rb +1 -1
  161. data/lib/gong_api/models/spoken_language.rb +1 -1
  162. data/lib/gong_api/models/structure.rb +1 -1
  163. data/lib/gong_api/models/topic.rb +1 -1
  164. data/lib/gong_api/models/tracker.rb +1 -1
  165. data/lib/gong_api/models/tracker_phrases.rb +1 -1
  166. data/lib/gong_api/models/update_meeting_request.rb +1 -1
  167. data/lib/gong_api/models/update_meeting_response.rb +1 -1
  168. data/lib/gong_api/models/user.rb +1 -1
  169. data/lib/gong_api/models/user_access_details.rb +1 -1
  170. data/lib/gong_api/models/user_activity.rb +1 -1
  171. data/lib/gong_api/models/user_aggregate_by_period_activities.rb +1 -1
  172. data/lib/gong_api/models/user_day_by_day_activity.rb +1 -1
  173. data/lib/gong_api/models/user_integration_status.rb +1 -1
  174. data/lib/gong_api/models/user_metadata.rb +1 -1
  175. data/lib/gong_api/models/user_settings_history.rb +1 -1
  176. data/lib/gong_api/models/user_simple_metadata.rb +1 -1
  177. data/lib/gong_api/models/users_aggregate_by_period_activity.rb +1 -1
  178. data/lib/gong_api/models/users_day_by_day_activity.rb +1 -1
  179. data/lib/gong_api/models/users_metadata.rb +1 -1
  180. data/lib/gong_api/models/video.rb +1 -1
  181. data/lib/gong_api/models/workspace_metadata.rb +1 -1
  182. data/lib/gong_api/models/workspaces_metadata.rb +1 -1
  183. data/lib/gong_api/version.rb +2 -2
  184. data/lib/gong_api.rb +1 -1
  185. data/spec/api/auditing_api_spec.rb +1 -1
  186. data/spec/api/calls_api_spec.rb +3 -3
  187. data/spec/api/crm_api_spec.rb +1 -1
  188. data/spec/api/data_privacy_api_spec.rb +1 -1
  189. data/spec/api/engagement_in_beta_phase_api_spec.rb +1 -1
  190. data/spec/api/library_api_spec.rb +1 -1
  191. data/spec/api/meetings_in_beta_phase_api_spec.rb +1 -1
  192. data/spec/api/permissions_api_spec.rb +1 -1
  193. data/spec/api/settings_api_spec.rb +1 -1
  194. data/spec/api/stats_api_spec.rb +1 -1
  195. data/spec/api/users_api_spec.rb +3 -3
  196. data/spec/api_client_spec.rb +1 -1
  197. data/spec/configuration_spec.rb +1 -1
  198. data/spec/models/actor_spec.rb +1 -1
  199. data/spec/models/aggregate_activity_spec.rb +1 -1
  200. data/spec/models/aggregate_activity_with_dates_spec.rb +1 -1
  201. data/spec/models/answer_spec.rb +1 -1
  202. data/spec/models/answered_scorecard_spec.rb +1 -1
  203. data/spec/models/answered_scorecards_filter_spec.rb +1 -1
  204. data/spec/models/answered_scorecards_spec.rb +1 -1
  205. data/spec/models/association_object_spec.rb +1 -1
  206. data/spec/models/async_processing_response_spec.rb +1 -1
  207. data/spec/models/base_response_spec.rb +1 -1
  208. data/spec/models/call_access_details_spec.rb +1 -1
  209. data/spec/models/call_access_with_permission_level_spec.rb +1 -1
  210. data/spec/models/call_basic_data_spec.rb +1 -1
  211. data/spec/models/call_collaboration_spec.rb +1 -1
  212. data/spec/models/call_content_spec.rb +1 -1
  213. data/spec/models/call_context_spec.rb +1 -1
  214. data/spec/models/call_interaction_spec.rb +1 -1
  215. data/spec/models/call_participant_spec.rb +1 -1
  216. data/spec/models/call_reference_spec.rb +1 -1
  217. data/spec/models/call_spec.rb +1 -1
  218. data/spec/models/call_transcript_spec.rb +1 -1
  219. data/spec/models/call_transcripts_spec.rb +1 -1
  220. data/spec/models/call_upload_context_spec.rb +1 -1
  221. data/spec/models/call_users_access_dto_spec.rb +1 -1
  222. data/spec/models/calls_access_details_response_spec.rb +1 -1
  223. data/spec/models/calls_access_get_dto_spec.rb +1 -1
  224. data/spec/models/calls_filter_spec.rb +1 -1
  225. data/spec/models/calls_request_filter_with_owners_spec.rb +1 -1
  226. data/spec/models/calls_response_spec.rb +1 -1
  227. data/spec/models/calls_spec.rb +1 -1
  228. data/spec/models/calls_users_access_add_dto_spec.rb +1 -1
  229. data/spec/models/calls_users_access_delete_dto_spec.rb +1 -1
  230. data/spec/models/coaching_access_with_permission_level_spec.rb +1 -1
  231. data/spec/models/collaboration_spec.rb +1 -1
  232. data/spec/models/comment_spec.rb +1 -1
  233. data/spec/models/company_users_aggregate_activity_response_spec.rb +1 -1
  234. data/spec/models/company_users_intercation_stats_response_spec.rb +1 -1
  235. data/spec/models/content_selector_spec.rb +1 -1
  236. data/spec/models/content_shared_event_spec.rb +1 -1
  237. data/spec/models/content_spec.rb +1 -1
  238. data/spec/models/content_viewed_event_spec.rb +1 -1
  239. data/spec/models/context_field_spec.rb +1 -1
  240. data/spec/models/crm_party_context_field_spec.rb +1 -1
  241. data/spec/models/custom_action_event_spec.rb +1 -1
  242. data/spec/models/customer_data_object_spec.rb +1 -1
  243. data/spec/models/customer_data_spec.rb +1 -1
  244. data/spec/models/customer_engagement_spec.rb +1 -1
  245. data/spec/models/daily_activity_with_dates_spec.rb +1 -1
  246. data/spec/models/deals_access_with_permission_level_spec.rb +1 -1
  247. data/spec/models/delete_meeting_request_spec.rb +1 -1
  248. data/spec/models/email_address_references_spec.rb +1 -1
  249. data/spec/models/email_message_spec.rb +1 -1
  250. data/spec/models/emails_access_with_permission_level_spec.rb +1 -1
  251. data/spec/models/error_response_spec.rb +1 -1
  252. data/spec/models/event_accepted_response_spec.rb +1 -1
  253. data/spec/models/exposed_fields_spec.rb +1 -1
  254. data/spec/models/external_call_object_spec.rb +1 -1
  255. data/spec/models/external_crm_call_object_spec.rb +1 -1
  256. data/spec/models/external_crm_party_object_spec.rb +1 -1
  257. data/spec/models/external_party_object_spec.rb +1 -1
  258. data/spec/models/external_system_object_spec.rb +1 -1
  259. data/spec/models/external_system_spec.rb +1 -1
  260. data/spec/models/forecast_access_with_permission_level_spec.rb +1 -1
  261. data/spec/models/generic_crm_integration_spec.rb +1 -1
  262. data/spec/models/generic_crm_registration_request_spec.rb +1 -1
  263. data/spec/models/generic_deal_stage_request_spec.rb +1 -1
  264. data/spec/models/generic_property_spec.rb +1 -1
  265. data/spec/models/generic_schema_field_request_spec.rb +1 -1
  266. data/spec/models/get_generic_crm_objects_response_spec.rb +1 -1
  267. data/spec/models/id_media_body_spec.rb +1 -1
  268. data/spec/models/insights_access_with_permission_level_spec.rb +1 -1
  269. data/spec/models/integration_status_request_spec.rb +1 -1
  270. data/spec/models/integration_status_response_spec.rb +1 -1
  271. data/spec/models/interaction_spec.rb +1 -1
  272. data/spec/models/interaction_stat_spec.rb +1 -1
  273. data/spec/models/interaction_stats_spec.rb +1 -1
  274. data/spec/models/library_call_spec.rb +1 -1
  275. data/spec/models/library_folder_access_spec.rb +1 -1
  276. data/spec/models/library_folder_list_of_calls_response_spec.rb +1 -1
  277. data/spec/models/library_folder_spec.rb +1 -1
  278. data/spec/models/library_response_spec.rb +1 -1
  279. data/spec/models/line_error_response_spec.rb +1 -1
  280. data/spec/models/list_generic_crm_integrations_response_spec.rb +1 -1
  281. data/spec/models/list_selected_fields_response_spec.rb +1 -1
  282. data/spec/models/log_entry_spec.rb +1 -1
  283. data/spec/models/logs_response_spec.rb +1 -1
  284. data/spec/models/manual_association_response_spec.rb +1 -1
  285. data/spec/models/manual_associations_basic_data_spec.rb +1 -1
  286. data/spec/models/map_users_body_spec.rb +1 -1
  287. data/spec/models/media_spec.rb +1 -1
  288. data/spec/models/meeting_invitee_spec.rb +1 -1
  289. data/spec/models/meeting_spec.rb +1 -1
  290. data/spec/models/meetings_error_response_spec.rb +1 -1
  291. data/spec/models/monologue_spec.rb +1 -1
  292. data/spec/models/multiple_users_request_with_creation_dates_spec.rb +1 -1
  293. data/spec/models/multiple_users_with_dates_spec.rb +1 -1
  294. data/spec/models/new_call_adding_request_spec.rb +1 -1
  295. data/spec/models/new_call_adding_response_spec.rb +1 -1
  296. data/spec/models/new_call_recording_response_spec.rb +1 -1
  297. data/spec/models/new_meeting_request_spec.rb +1 -1
  298. data/spec/models/new_meeting_response_spec.rb +1 -1
  299. data/spec/models/object_entities_body_spec.rb +1 -1
  300. data/spec/models/occurrences_spec.rb +1 -1
  301. data/spec/models/party_context_field_spec.rb +1 -1
  302. data/spec/models/party_context_spec.rb +1 -1
  303. data/spec/models/party_spec.rb +1 -1
  304. data/spec/models/party_upload_context_spec.rb +1 -1
  305. data/spec/models/permission_profile_dto_spec.rb +1 -1
  306. data/spec/models/permission_profile_response_spec.rb +1 -1
  307. data/spec/models/permission_profile_users_response_spec.rb +1 -1
  308. data/spec/models/permission_profiles_response_spec.rb +1 -1
  309. data/spec/models/phone_number_references_spec.rb +1 -1
  310. data/spec/models/point_of_interest_spec.rb +1 -1
  311. data/spec/models/points_of_interest_spec.rb +1 -1
  312. data/spec/models/question_spec.rb +1 -1
  313. data/spec/models/questions_spec.rb +1 -1
  314. data/spec/models/records_spec.rb +1 -1
  315. data/spec/models/register_generic_crm_response_spec.rb +1 -1
  316. data/spec/models/request_answered_scorecards_filter_spec.rb +1 -1
  317. data/spec/models/request_calls_access_get_dto_spec.rb +1 -1
  318. data/spec/models/request_calls_filter_spec.rb +1 -1
  319. data/spec/models/request_calls_request_filter_with_owners_content_selector_spec.rb +1 -1
  320. data/spec/models/request_multiple_users_request_with_creation_dates_spec.rb +1 -1
  321. data/spec/models/request_multiple_users_with_dates_spec.rb +1 -1
  322. data/spec/models/request_status_response_spec.rb +1 -1
  323. data/spec/models/request_with_time_period_multiple_users_with_dates_spec.rb +1 -1
  324. data/spec/models/schema_update_response_spec.rb +1 -1
  325. data/spec/models/scorecard_spec.rb +1 -1
  326. data/spec/models/scorecards_spec.rb +1 -1
  327. data/spec/models/sentence_spec.rb +1 -1
  328. data/spec/models/settings_history_spec.rb +1 -1
  329. data/spec/models/settings_spec.rb +1 -1
  330. data/spec/models/sharer_spec.rb +1 -1
  331. data/spec/models/snippet_spec.rb +1 -1
  332. data/spec/models/speaker_spec.rb +1 -1
  333. data/spec/models/speakers_timeline_spec.rb +1 -1
  334. data/spec/models/specific_call_spec.rb +1 -1
  335. data/spec/models/speech_segment_spec.rb +1 -1
  336. data/spec/models/spoken_language_spec.rb +1 -1
  337. data/spec/models/structure_spec.rb +1 -1
  338. data/spec/models/topic_spec.rb +1 -1
  339. data/spec/models/tracker_phrases_spec.rb +1 -1
  340. data/spec/models/tracker_spec.rb +1 -1
  341. data/spec/models/update_meeting_request_spec.rb +1 -1
  342. data/spec/models/update_meeting_response_spec.rb +1 -1
  343. data/spec/models/user_access_details_spec.rb +1 -1
  344. data/spec/models/user_activity_spec.rb +1 -1
  345. data/spec/models/user_aggregate_by_period_activities_spec.rb +1 -1
  346. data/spec/models/user_day_by_day_activity_spec.rb +1 -1
  347. data/spec/models/user_integration_status_spec.rb +1 -1
  348. data/spec/models/user_metadata_spec.rb +1 -1
  349. data/spec/models/user_settings_history_spec.rb +1 -1
  350. data/spec/models/user_simple_metadata_spec.rb +1 -1
  351. data/spec/models/user_spec.rb +1 -1
  352. data/spec/models/users_aggregate_by_period_activity_spec.rb +1 -1
  353. data/spec/models/users_day_by_day_activity_spec.rb +1 -1
  354. data/spec/models/users_metadata_spec.rb +1 -1
  355. data/spec/models/video_spec.rb +1 -1
  356. data/spec/models/workspace_metadata_spec.rb +1 -1
  357. data/spec/models/workspaces_metadata_spec.rb +1 -1
  358. data/spec/spec_helper.rb +1 -1
  359. metadata +35 -9
  360. data/git_push.sh +0 -55
  361. data/spec/base_object_spec.rb +0 -109
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
data/spec/spec_helper.rb CHANGED
@@ -1,7 +1,7 @@
1
1
  =begin
2
2
  #Gong API
3
3
 
4
- #<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>
4
+
5
5
 
6
6
  OpenAPI spec version: V2
7
7
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: gong_api
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.0.0
4
+ version: 1.1.1
5
5
  platform: ruby
6
6
  authors:
7
- - OpTonal Inc.
7
+ - Matija Čupić
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2023-01-20 00:00:00.000000000 Z
11
+ date: 2025-10-22 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: typhoeus
@@ -70,14 +70,43 @@ dependencies:
70
70
  - - ">="
71
71
  - !ruby/object:Gem::Version
72
72
  version: 3.6.0
73
+ - !ruby/object:Gem::Dependency
74
+ name: rubocop
75
+ requirement: !ruby/object:Gem::Requirement
76
+ requirements:
77
+ - - ">="
78
+ - !ruby/object:Gem::Version
79
+ version: '0'
80
+ type: :development
81
+ prerelease: false
82
+ version_requirements: !ruby/object:Gem::Requirement
83
+ requirements:
84
+ - - ">="
85
+ - !ruby/object:Gem::Version
86
+ version: '0'
87
+ - !ruby/object:Gem::Dependency
88
+ name: rubocop-rspec
89
+ requirement: !ruby/object:Gem::Requirement
90
+ requirements:
91
+ - - ">="
92
+ - !ruby/object:Gem::Version
93
+ version: '0'
94
+ type: :development
95
+ prerelease: false
96
+ version_requirements: !ruby/object:Gem::Requirement
97
+ requirements:
98
+ - - ">="
99
+ - !ruby/object:Gem::Version
100
+ version: '0'
73
101
  description: A Ruby Swagger API client for Gong
74
102
  email:
75
- - matija@optonal.com
103
+ - matteeyah@gmail.com
76
104
  executables: []
77
105
  extensions: []
78
106
  extra_rdoc_files: []
79
107
  files:
80
108
  - Gemfile
109
+ - Gemfile.lock
81
110
  - README.md
82
111
  - Rakefile
83
112
  - config.json
@@ -252,7 +281,6 @@ files:
252
281
  - docs/Video.md
253
282
  - docs/WorkspaceMetadata.md
254
283
  - docs/WorkspacesMetadata.md
255
- - git_push.sh
256
284
  - gong-swagger.json
257
285
  - gong_api.gemspec
258
286
  - lib/gong_api.rb
@@ -443,7 +471,6 @@ files:
443
471
  - spec/api/stats_api_spec.rb
444
472
  - spec/api/users_api_spec.rb
445
473
  - spec/api_client_spec.rb
446
- - spec/base_object_spec.rb
447
474
  - spec/configuration_spec.rb
448
475
  - spec/models/actor_spec.rb
449
476
  - spec/models/aggregate_activity_spec.rb
@@ -606,7 +633,7 @@ files:
606
633
  - spec/models/workspace_metadata_spec.rb
607
634
  - spec/models/workspaces_metadata_spec.rb
608
635
  - spec/spec_helper.rb
609
- homepage: https://gitlab.com/optonal/gong-api
636
+ homepage: https://github.com/matteeyah/gong-api
610
637
  licenses:
611
638
  - MIT
612
639
  metadata: {}
@@ -625,7 +652,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
625
652
  - !ruby/object:Gem::Version
626
653
  version: '0'
627
654
  requirements: []
628
- rubygems_version: 3.3.7
655
+ rubygems_version: 3.4.6
629
656
  signing_key:
630
657
  specification_version: 4
631
658
  summary: A Ruby Swagger API client for Gong
@@ -642,7 +669,6 @@ test_files:
642
669
  - spec/api/calls_api_spec.rb
643
670
  - spec/api/auditing_api_spec.rb
644
671
  - spec/api_client_spec.rb
645
- - spec/base_object_spec.rb
646
672
  - spec/configuration_spec.rb
647
673
  - spec/models/async_processing_response_spec.rb
648
674
  - spec/models/external_crm_call_object_spec.rb
data/git_push.sh DELETED
@@ -1,55 +0,0 @@
1
- #!/bin/sh
2
- #
3
- # Generated by: https://github.com/swagger-api/swagger-codegen.git
4
- #
5
- # ref: https://help.github.com/articles/adding-an-existing-project-to-github-using-the-command-line/
6
- #
7
- # Usage example: /bin/sh ./git_push.sh wing328 swagger-petstore-perl "minor update"
8
-
9
- git_user_id=$1
10
- git_repo_id=$2
11
- release_note=$3
12
-
13
- if [ "$git_user_id" = "" ]; then
14
- git_user_id="GIT_USER_ID"
15
- echo "[INFO] No command line input provided. Set \$git_user_id to $git_user_id"
16
- fi
17
-
18
- if [ "$git_repo_id" = "" ]; then
19
- git_repo_id="GIT_REPO_ID"
20
- echo "[INFO] No command line input provided. Set \$git_repo_id to $git_repo_id"
21
- fi
22
-
23
- if [ "$release_note" = "" ]; then
24
- release_note="Minor update"
25
- echo "[INFO] No command line input provided. Set \$release_note to $release_note"
26
- fi
27
-
28
- # Initialize the local directory as a Git repository
29
- git init
30
-
31
- # Adds the files in the local repository and stages them for commit.
32
- git add .
33
-
34
- # Commits the tracked changes and prepares them to be pushed to a remote repository.
35
- git commit -m "$release_note"
36
-
37
- # Sets the new remote
38
- git_remote=`git remote`
39
- if [ "$git_remote" = "" ]; then # git remote not defined
40
-
41
- if [ "$GIT_TOKEN" = "" ]; then
42
- echo "[INFO] \$GIT_TOKEN (environment variable) is not set. Using the git credential in your environment."
43
- git remote add origin https://github.com/${git_user_id}/${git_repo_id}.git
44
- else
45
- git remote add origin https://${git_user_id}:${GIT_TOKEN}@github.com/${git_user_id}/${git_repo_id}.git
46
- fi
47
-
48
- fi
49
-
50
- git pull origin master
51
-
52
- # Pushes (Forces) the changes in the local repository up to the remote repository
53
- echo "Git pushing to https://github.com/${git_user_id}/${git_repo_id}.git"
54
- git push origin master 2>&1 | grep -v 'To https'
55
-