onesignal 2.2.0 → 5.1.0.pre.beta1

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 (211) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +42 -65
  3. data/docs/BasicNotification.md +18 -18
  4. data/docs/BasicNotificationAllOf.md +9 -7
  5. data/docs/CreateNotificationSuccessResponse.md +1 -3
  6. data/docs/DefaultApi.md +364 -874
  7. data/docs/{ExportPlayersRequestBody.md → ExportSubscriptionsRequestBody.md} +2 -2
  8. data/docs/{ExportPlayersSuccessResponse.md → ExportSubscriptionsSuccessResponse.md} +2 -2
  9. data/docs/Filter.md +10 -2
  10. data/docs/{Notification200Errors.md → FilterExpression.md} +9 -9
  11. data/docs/GenericError.md +6 -2
  12. data/docs/{DeletePlayerSuccessResponse.md → GenericSuccessBoolResponse.md} +2 -2
  13. data/docs/{GetNotificationRequestBody.md → GetNotificationHistoryRequestBody.md} +2 -2
  14. data/docs/GetSegmentsSuccessResponse.md +24 -0
  15. data/docs/{StringMap.md → LanguageStringMap.md} +2 -2
  16. data/docs/Notification.md +18 -18
  17. data/docs/NotificationTarget.md +9 -11
  18. data/docs/NotificationWithMeta.md +18 -18
  19. data/docs/{InlineResponse202.md → PropertiesBody.md} +2 -2
  20. data/docs/PropertiesDeltas.md +2 -2
  21. data/docs/PropertiesObject.md +2 -2
  22. data/docs/Purchase.md +1 -1
  23. data/docs/RateLimitError.md +20 -0
  24. data/docs/Segment.md +1 -1
  25. data/docs/SegmentData.md +30 -0
  26. data/docs/{SubscriptionObject.md → Subscription.md} +7 -7
  27. data/docs/SubscriptionBody.md +18 -0
  28. data/docs/SubscriptionNotificationTarget.md +38 -0
  29. data/docs/TransferSubscriptionRequestBody.md +1 -1
  30. data/docs/UpdateLiveActivityRequest.md +14 -4
  31. data/docs/UpdateLiveActivitySuccessResponse.md +2 -4
  32. data/docs/User.md +3 -5
  33. data/docs/{InlineResponse200.md → UserIdentityBody.md} +3 -3
  34. data/docs/WebButton.md +24 -0
  35. data/lib/onesignal/api/default_api.rb +382 -890
  36. data/lib/onesignal/api_client.rb +2 -2
  37. data/lib/onesignal/api_error.rb +1 -1
  38. data/lib/onesignal/configuration.rb +5 -5
  39. data/lib/onesignal/models/app.rb +1 -1
  40. data/lib/onesignal/models/basic_notification.rb +49 -47
  41. data/lib/onesignal/models/basic_notification_all_of.rb +29 -17
  42. data/lib/onesignal/models/basic_notification_all_of_android_background_layout.rb +1 -1
  43. data/lib/onesignal/models/button.rb +1 -1
  44. data/lib/onesignal/models/create_notification_success_response.rb +5 -13
  45. data/lib/onesignal/models/create_segment_conflict_response.rb +1 -1
  46. data/lib/onesignal/models/create_segment_success_response.rb +1 -1
  47. data/lib/onesignal/models/create_user_conflict_response.rb +1 -1
  48. data/lib/onesignal/models/create_user_conflict_response_errors_inner.rb +1 -1
  49. data/lib/onesignal/models/create_user_conflict_response_errors_items_meta.rb +1 -1
  50. data/lib/onesignal/models/delivery_data.rb +1 -1
  51. data/lib/onesignal/models/export_events_success_response.rb +1 -1
  52. data/lib/onesignal/models/{export_players_request_body.rb → export_subscriptions_request_body.rb} +4 -4
  53. data/lib/onesignal/models/{export_players_success_response.rb → export_subscriptions_success_response.rb} +4 -4
  54. data/lib/onesignal/models/filter.rb +44 -14
  55. data/lib/onesignal/models/{notification200_errors.rb → filter_expression.rb} +4 -4
  56. data/lib/onesignal/models/generic_error.rb +26 -8
  57. data/lib/onesignal/models/{update_player_success_response.rb → generic_success_bool_response.rb} +4 -4
  58. data/lib/onesignal/models/{get_notification_request_body.rb → get_notification_history_request_body.rb} +4 -4
  59. data/lib/onesignal/models/{player_slice.rb → get_segments_success_response.rb} +16 -12
  60. data/lib/onesignal/models/{string_map.rb → language_string_map.rb} +4 -4
  61. data/lib/onesignal/models/notification.rb +49 -47
  62. data/lib/onesignal/models/notification_all_of.rb +1 -1
  63. data/lib/onesignal/models/notification_history_success_response.rb +1 -1
  64. data/lib/onesignal/models/notification_slice.rb +1 -1
  65. data/lib/onesignal/models/notification_target.rb +24 -34
  66. data/lib/onesignal/models/notification_with_meta.rb +49 -47
  67. data/lib/onesignal/models/notification_with_meta_all_of.rb +1 -1
  68. data/lib/onesignal/models/operator.rb +1 -1
  69. data/lib/onesignal/models/outcome_data.rb +1 -1
  70. data/lib/onesignal/models/outcomes_data.rb +1 -1
  71. data/lib/onesignal/models/platform_delivery_data.rb +1 -1
  72. data/lib/onesignal/models/platform_delivery_data_email_all_of.rb +1 -1
  73. data/lib/onesignal/models/platform_delivery_data_sms_all_of.rb +1 -1
  74. data/lib/onesignal/models/{inline_response202.rb → properties_body.rb} +4 -4
  75. data/lib/onesignal/models/properties_deltas.rb +3 -3
  76. data/lib/onesignal/models/properties_object.rb +3 -3
  77. data/lib/onesignal/models/purchase.rb +2 -2
  78. data/lib/onesignal/models/{rate_limiter_error.rb → rate_limit_error.rb} +17 -8
  79. data/lib/onesignal/models/segment.rb +2 -2
  80. data/lib/onesignal/models/{begin_live_activity_request.rb → segment_data.rb} +69 -27
  81. data/lib/onesignal/models/segment_notification_target.rb +1 -1
  82. data/lib/onesignal/models/{subscription_object.rb → subscription.rb} +9 -9
  83. data/lib/onesignal/models/{inline_response201.rb → subscription_body.rb} +5 -5
  84. data/lib/onesignal/models/{player_notification_target.rb → subscription_notification_target.rb} +25 -35
  85. data/lib/onesignal/models/transfer_subscription_request_body.rb +26 -2
  86. data/lib/onesignal/models/update_live_activity_request.rb +59 -22
  87. data/lib/onesignal/models/update_live_activity_success_response.rb +8 -17
  88. data/lib/onesignal/models/update_user_request.rb +1 -1
  89. data/lib/onesignal/models/user.rb +6 -15
  90. data/lib/onesignal/models/{inline_response200.rb → user_identity_body.rb} +5 -5
  91. data/lib/onesignal/models/{create_player_success_response.rb → web_button.rb} +40 -17
  92. data/lib/onesignal/version.rb +2 -2
  93. data/lib/onesignal.rb +16 -34
  94. data/onesignal.gemspec +1 -1
  95. data/spec/api/default_api_spec.rb +82 -174
  96. data/spec/api_client_spec.rb +1 -1
  97. data/spec/configuration_spec.rb +1 -1
  98. data/spec/models/app_spec.rb +1 -1
  99. data/spec/models/basic_notification_all_of_android_background_layout_spec.rb +1 -1
  100. data/spec/models/basic_notification_all_of_spec.rb +13 -7
  101. data/spec/models/basic_notification_spec.rb +14 -14
  102. data/spec/models/button_spec.rb +1 -1
  103. data/spec/models/create_notification_success_response_spec.rb +1 -7
  104. data/spec/models/create_segment_conflict_response_spec.rb +1 -1
  105. data/spec/models/create_segment_success_response_spec.rb +1 -1
  106. data/spec/models/create_user_conflict_response_errors_inner_spec.rb +1 -1
  107. data/spec/models/create_user_conflict_response_errors_items_meta_spec.rb +1 -1
  108. data/spec/models/create_user_conflict_response_spec.rb +1 -1
  109. data/spec/models/delivery_data_spec.rb +1 -1
  110. data/spec/models/export_events_success_response_spec.rb +1 -1
  111. data/spec/models/{export_players_request_body_spec.rb → export_subscriptions_request_body_spec.rb} +7 -7
  112. data/spec/models/{export_players_success_response_spec.rb → export_subscriptions_success_response_spec.rb} +7 -7
  113. data/spec/models/{notification200_errors_spec.rb → filter_expression_spec.rb} +3 -3
  114. data/spec/models/filter_spec.rb +25 -1
  115. data/spec/models/generic_error_spec.rb +13 -1
  116. data/spec/models/{delete_player_success_response_spec.rb → generic_success_bool_response_spec.rb} +7 -7
  117. data/spec/models/{get_notification_request_body_spec.rb → get_notification_history_request_body_spec.rb} +7 -7
  118. data/spec/models/{player_slice_spec.rb → get_segments_success_response_spec.rb} +8 -8
  119. data/spec/models/{string_map_spec.rb → language_string_map_spec.rb} +7 -7
  120. data/spec/models/notification_all_of_spec.rb +1 -1
  121. data/spec/models/notification_history_success_response_spec.rb +1 -1
  122. data/spec/models/notification_slice_spec.rb +1 -1
  123. data/spec/models/notification_spec.rb +14 -14
  124. data/spec/models/notification_target_spec.rb +2 -8
  125. data/spec/models/notification_with_meta_all_of_spec.rb +1 -1
  126. data/spec/models/notification_with_meta_spec.rb +14 -14
  127. data/spec/models/operator_spec.rb +1 -1
  128. data/spec/models/outcome_data_spec.rb +1 -1
  129. data/spec/models/outcomes_data_spec.rb +1 -1
  130. data/spec/models/platform_delivery_data_email_all_of_spec.rb +1 -1
  131. data/spec/models/platform_delivery_data_sms_all_of_spec.rb +1 -1
  132. data/spec/models/platform_delivery_data_spec.rb +1 -1
  133. data/spec/models/{inline_response202_spec.rb → properties_body_spec.rb} +7 -7
  134. data/spec/models/properties_deltas_spec.rb +1 -1
  135. data/spec/models/properties_object_spec.rb +1 -1
  136. data/spec/models/purchase_spec.rb +1 -1
  137. data/spec/models/{generic_error_errors_inner_spec.rb → rate_limit_error_spec.rb} +9 -9
  138. data/spec/models/{filter_expressions_spec.rb → segment_data_spec.rb} +24 -20
  139. data/spec/models/segment_notification_target_spec.rb +1 -1
  140. data/spec/models/segment_spec.rb +1 -1
  141. data/spec/models/{inline_response201_spec.rb → subscription_body_spec.rb} +7 -7
  142. data/spec/models/{player_notification_target_spec.rb → subscription_notification_target_spec.rb} +8 -14
  143. data/spec/models/{subscription_object_spec.rb → subscription_spec.rb} +7 -7
  144. data/spec/models/transfer_subscription_request_body_spec.rb +1 -1
  145. data/spec/models/update_live_activity_request_spec.rb +32 -6
  146. data/spec/models/update_live_activity_success_response_spec.rb +2 -8
  147. data/spec/models/update_user_request_spec.rb +1 -1
  148. data/spec/models/{user_identity_response_spec.rb → user_identity_body_spec.rb} +7 -7
  149. data/spec/models/user_spec.rb +1 -7
  150. data/spec/models/{create_player_success_response_spec.rb → web_button_spec.rb} +21 -9
  151. data/spec/spec_helper.rb +1 -1
  152. metadata +97 -171
  153. data/Gemfile.lock +0 -74
  154. data/docs/BeginLiveActivityRequest.md +0 -20
  155. data/docs/CancelNotificationSuccessResponse.md +0 -18
  156. data/docs/CreatePlayerSuccessResponse.md +0 -20
  157. data/docs/CreateSubscriptionRequestBody.md +0 -20
  158. data/docs/DeletePlayerNotFoundResponse.md +0 -18
  159. data/docs/DeleteSegmentNotFoundResponse.md +0 -18
  160. data/docs/DeleteSegmentSuccessResponse.md +0 -18
  161. data/docs/FilterExpressions.md +0 -26
  162. data/docs/InlineResponse2003.md +0 -18
  163. data/docs/InlineResponse201.md +0 -18
  164. data/docs/InvalidIdentifierError.md +0 -20
  165. data/docs/Player.md +0 -70
  166. data/docs/PlayerNotificationTarget.md +0 -40
  167. data/docs/PlayerNotificationTargetIncludeAliases.md +0 -18
  168. data/docs/PlayerSlice.md +0 -24
  169. data/docs/UpdatePlayerSuccessResponse.md +0 -18
  170. data/docs/UpdatePlayerTagsRequestBody.md +0 -18
  171. data/docs/UpdatePlayerTagsSuccessResponse.md +0 -18
  172. data/docs/UpdateSubscriptionRequestBody.md +0 -18
  173. data/docs/UserIdentityRequestBody.md +0 -18
  174. data/docs/UserIdentityResponse.md +0 -18
  175. data/docs/UserSubscriptionOptions.md +0 -18
  176. data/lib/onesignal/models/cancel_notification_success_response.rb +0 -219
  177. data/lib/onesignal/models/create_subscription_request_body.rb +0 -228
  178. data/lib/onesignal/models/delete_player_not_found_response.rb +0 -219
  179. data/lib/onesignal/models/delete_player_success_response.rb +0 -219
  180. data/lib/onesignal/models/delete_segment_not_found_response.rb +0 -219
  181. data/lib/onesignal/models/delete_segment_success_response.rb +0 -219
  182. data/lib/onesignal/models/filter_expressions.rb +0 -336
  183. data/lib/onesignal/models/generic_error_errors_inner.rb +0 -228
  184. data/lib/onesignal/models/inline_response2003.rb +0 -221
  185. data/lib/onesignal/models/invalid_identifier_error.rb +0 -234
  186. data/lib/onesignal/models/player.rb +0 -494
  187. data/lib/onesignal/models/player_notification_target_include_aliases.rb +0 -221
  188. data/lib/onesignal/models/update_player_tags_request_body.rb +0 -220
  189. data/lib/onesignal/models/update_player_tags_success_response.rb +0 -219
  190. data/lib/onesignal/models/update_subscription_request_body.rb +0 -219
  191. data/lib/onesignal/models/user_identity_request_body.rb +0 -221
  192. data/lib/onesignal/models/user_identity_response.rb +0 -221
  193. data/lib/onesignal/models/user_subscription_options.rb +0 -219
  194. data/spec/models/begin_live_activity_request_spec.rb +0 -40
  195. data/spec/models/cancel_notification_success_response_spec.rb +0 -34
  196. data/spec/models/create_subscription_request_body_spec.rb +0 -40
  197. data/spec/models/delete_player_not_found_response_spec.rb +0 -34
  198. data/spec/models/delete_segment_not_found_response_spec.rb +0 -34
  199. data/spec/models/delete_segment_success_response_spec.rb +0 -34
  200. data/spec/models/inline_response2003_spec.rb +0 -34
  201. data/spec/models/inline_response200_spec.rb +0 -34
  202. data/spec/models/invalid_identifier_error_spec.rb +0 -40
  203. data/spec/models/player_notification_target_include_aliases_spec.rb +0 -34
  204. data/spec/models/player_spec.rb +0 -190
  205. data/spec/models/rate_limiter_error_spec.rb +0 -34
  206. data/spec/models/update_player_success_response_spec.rb +0 -34
  207. data/spec/models/update_player_tags_request_body_spec.rb +0 -34
  208. data/spec/models/update_player_tags_success_response_spec.rb +0 -34
  209. data/spec/models/update_subscription_request_body_spec.rb +0 -34
  210. data/spec/models/user_identity_request_body_spec.rb +0 -34
  211. data/spec/models/user_subscription_options_spec.rb +0 -34
@@ -1,4 +1,4 @@
1
- # OneSignal::ExportPlayersRequestBody
1
+ # OneSignal::ExportSubscriptionsRequestBody
2
2
 
3
3
  ## Properties
4
4
 
@@ -13,7 +13,7 @@
13
13
  ```ruby
14
14
  require 'onesignal'
15
15
 
16
- instance = OneSignal::ExportPlayersRequestBody.new(
16
+ instance = OneSignal::ExportSubscriptionsRequestBody.new(
17
17
  extra_fields: null,
18
18
  last_active_since: null,
19
19
  segment_name: null
@@ -1,4 +1,4 @@
1
- # OneSignal::ExportPlayersSuccessResponse
1
+ # OneSignal::ExportSubscriptionsSuccessResponse
2
2
 
3
3
  ## Properties
4
4
 
@@ -11,7 +11,7 @@
11
11
  ```ruby
12
12
  require 'onesignal'
13
13
 
14
- instance = OneSignal::ExportPlayersSuccessResponse.new(
14
+ instance = OneSignal::ExportSubscriptionsSuccessResponse.new(
15
15
  csv_file_url: null
16
16
  )
17
17
  ```
data/docs/Filter.md CHANGED
@@ -4,10 +4,14 @@
4
4
 
5
5
  | Name | Type | Description | Notes |
6
6
  | ---- | ---- | ----------- | ----- |
7
- | **field** | **String** | Name of the field to use as the first operand in the filter expression. | |
7
+ | **field** | **String** | Required. Name of the field to use as the first operand in the filter expression. | [optional] |
8
8
  | **key** | **String** | If `field` is `tag`, this field is *required* to specify `key` inside the tags. | [optional] |
9
9
  | **value** | **String** | Constant value to use as the second operand in the filter expression. This value is *required* when the relation operator is a binary operator. | [optional] |
10
- | **relation** | **String** | Operator of a filter expression. | |
10
+ | **hours_ago** | **String** | If `field` is session-related, this is *required* to specify the number of hours before or after the user's session. | [optional] |
11
+ | **radius** | **Float** | If `field` is `location`, this will specify the radius in meters from a provided location point. Use with `lat` and `long`. | [optional] |
12
+ | **lat** | **Float** | If `field` is `location`, this is *required* to specify the user's latitude. | [optional] |
13
+ | **long** | **Float** | If `field` is `location`, this is *required* to specify the user's longitude. | [optional] |
14
+ | **relation** | **String** | Required. Operator of a filter expression. | [optional] |
11
15
 
12
16
  ## Example
13
17
 
@@ -18,6 +22,10 @@ instance = OneSignal::Filter.new(
18
22
  field: null,
19
23
  key: null,
20
24
  value: null,
25
+ hours_ago: null,
26
+ radius: null,
27
+ lat: null,
28
+ long: null,
21
29
  relation: null
22
30
  )
23
31
  ```
@@ -1,4 +1,4 @@
1
- # OneSignal::Notification200Errors
1
+ # OneSignal::FilterExpression
2
2
 
3
3
  ## Class instance methods
4
4
 
@@ -11,11 +11,11 @@ Returns the list of classes defined in oneOf.
11
11
  ```ruby
12
12
  require 'onesignal'
13
13
 
14
- OneSignal::Notification200Errors.openapi_one_of
14
+ OneSignal::FilterExpression.openapi_one_of
15
15
  # =>
16
16
  # [
17
- # :'Array<String>',
18
- # :'InvalidIdentifierError'
17
+ # :'Filter',
18
+ # :'Operator'
19
19
  # ]
20
20
  ```
21
21
 
@@ -28,10 +28,10 @@ Find the appropriate object from the `openapi_one_of` list and casts the data in
28
28
  ```ruby
29
29
  require 'onesignal'
30
30
 
31
- OneSignal::Notification200Errors.build(data)
32
- # => #<Array<String>:0x00007fdd4aab02a0>
31
+ OneSignal::FilterExpression.build(data)
32
+ # => #<Filter:0x00007fdd4aab02a0>
33
33
 
34
- OneSignal::Notification200Errors.build(data_that_doesnt_match)
34
+ OneSignal::FilterExpression.build(data_that_doesnt_match)
35
35
  # => nil
36
36
  ```
37
37
 
@@ -43,7 +43,7 @@ OneSignal::Notification200Errors.build(data_that_doesnt_match)
43
43
 
44
44
  #### Return type
45
45
 
46
- - `Array<String>`
47
- - `InvalidIdentifierError`
46
+ - `Filter`
47
+ - `Operator`
48
48
  - `nil` (if no type matches)
49
49
 
data/docs/GenericError.md CHANGED
@@ -4,7 +4,9 @@
4
4
 
5
5
  | Name | Type | Description | Notes |
6
6
  | ---- | ---- | ----------- | ----- |
7
- | **errors** | [**Array&lt;GenericErrorErrorsInner&gt;**](GenericErrorErrorsInner.md) | | [optional] |
7
+ | **errors** | **Object** | | [optional] |
8
+ | **success** | **Boolean** | | [optional] |
9
+ | **reference** | **Object** | | [optional] |
8
10
 
9
11
  ## Example
10
12
 
@@ -12,7 +14,9 @@
12
14
  require 'onesignal'
13
15
 
14
16
  instance = OneSignal::GenericError.new(
15
- errors: null
17
+ errors: null,
18
+ success: null,
19
+ reference: null
16
20
  )
17
21
  ```
18
22
 
@@ -1,4 +1,4 @@
1
- # OneSignal::DeletePlayerSuccessResponse
1
+ # OneSignal::GenericSuccessBoolResponse
2
2
 
3
3
  ## Properties
4
4
 
@@ -11,7 +11,7 @@
11
11
  ```ruby
12
12
  require 'onesignal'
13
13
 
14
- instance = OneSignal::DeletePlayerSuccessResponse.new(
14
+ instance = OneSignal::GenericSuccessBoolResponse.new(
15
15
  success: null
16
16
  )
17
17
  ```
@@ -1,4 +1,4 @@
1
- # OneSignal::GetNotificationRequestBody
1
+ # OneSignal::GetNotificationHistoryRequestBody
2
2
 
3
3
  ## Properties
4
4
 
@@ -13,7 +13,7 @@
13
13
  ```ruby
14
14
  require 'onesignal'
15
15
 
16
- instance = OneSignal::GetNotificationRequestBody.new(
16
+ instance = OneSignal::GetNotificationHistoryRequestBody.new(
17
17
  events: null,
18
18
  email: null,
19
19
  app_id: null
@@ -0,0 +1,24 @@
1
+ # OneSignal::GetSegmentsSuccessResponse
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **total_count** | **Integer** | The number of Segments in the response. | [optional] |
8
+ | **offset** | **Integer** | Set with the offset query parameter. Default 0. | [optional] |
9
+ | **limit** | **Integer** | Maximum number of Segments returned. Default 300. | [optional] |
10
+ | **segments** | [**Array&lt;SegmentData&gt;**](SegmentData.md) | An array containing the Segment information. | [optional] |
11
+
12
+ ## Example
13
+
14
+ ```ruby
15
+ require 'onesignal'
16
+
17
+ instance = OneSignal::GetSegmentsSuccessResponse.new(
18
+ total_count: null,
19
+ offset: null,
20
+ limit: null,
21
+ segments: null
22
+ )
23
+ ```
24
+
@@ -1,4 +1,4 @@
1
- # OneSignal::StringMap
1
+ # OneSignal::LanguageStringMap
2
2
 
3
3
  ## Properties
4
4
 
@@ -53,7 +53,7 @@
53
53
  ```ruby
54
54
  require 'onesignal'
55
55
 
56
- instance = OneSignal::StringMap.new(
56
+ instance = OneSignal::LanguageStringMap.new(
57
57
  en: null,
58
58
  ar: null,
59
59
  bs: null,
data/docs/Notification.md CHANGED
@@ -6,17 +6,16 @@
6
6
  | ---- | ---- | ----------- | ----- |
7
7
  | **included_segments** | **Array&lt;String&gt;** | The segment names you want to target. Users in these segments will receive a notification. This targeting parameter is only compatible with excluded_segments. Example: [\&quot;Active Users\&quot;, \&quot;Inactive Users\&quot;] | [optional] |
8
8
  | **excluded_segments** | **Array&lt;String&gt;** | Segment that will be excluded when sending. Users in these segments will not receive a notification, even if they were included in included_segments. This targeting parameter is only compatible with included_segments. Example: [\&quot;Active Users\&quot;, \&quot;Inactive Users\&quot;] | [optional] |
9
- | **include_player_ids** | **Array&lt;String&gt;** | Specific playerids to send your notification to. _Does not require API Auth Key. Do not combine with other targeting parameters. Not compatible with any other targeting parameters. Example: [\&quot;1dd608f2-c6a1-11e3-851d-000c2940e62c\&quot;] Limit of 2,000 entries per REST API call | [optional] |
10
- | **include_external_user_ids** | **Array&lt;String&gt;** | Target specific devices by custom user IDs assigned via API. Not compatible with any other targeting parameters Example: [\&quot;custom-id-assigned-by-api\&quot;] REQUIRED: REST API Key Authentication Limit of 2,000 entries per REST API call. Note: If targeting push, email, or sms subscribers with same ids, use with channel_for_external_user_ids to indicate you are sending a push or email or sms. | [optional] |
9
+ | **include_subscription_ids** | **Array&lt;String&gt;** | Specific subscription ids to send your notification to. _Does not require API Auth Key._ Not compatible with any other targeting parameters. Example: [\&quot;1dd608f2-c6a1-11e3-851d-000c2940e62c\&quot;] Limit of 2,000 entries per REST API call | [optional] |
11
10
  | **include_email_tokens** | **Array&lt;String&gt;** | Recommended for Sending Emails - Target specific email addresses. If an email does not correspond to an existing user, a new user will be created. Example: nick@catfac.ts Limit of 2,000 entries per REST API call | [optional] |
12
11
  | **include_phone_numbers** | **Array&lt;String&gt;** | Recommended for Sending SMS - Target specific phone numbers. The phone number should be in the E.164 format. Phone number should be an existing subscriber on OneSignal. Refer our docs to learn how to add phone numbers to OneSignal. Example phone number: +1999999999 Limit of 2,000 entries per REST API call | [optional] |
13
- | **include_ios_tokens** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using iOS device tokens. Warning: Only works with Production tokens. All non-alphanumeric characters must be removed from each token. If a token does not correspond to an existing user, a new user will be created. Example: ce777617da7f548fe7a9ab6febb56cf39fba6d38203... Limit of 2,000 entries per REST API call | [optional] |
14
- | **include_wp_wns_uris** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Windows URIs. If a token does not correspond to an existing user, a new user will be created. Example: http://s.notify.live.net/u/1/bn1/HmQAAACPaLDr-... Limit of 2,000 entries per REST API call | [optional] |
15
- | **include_amazon_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Amazon ADM registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: amzn1.adm-registration.v1.XpvSSUk0Rc3hTVVV... Limit of 2,000 entries per REST API call | [optional] |
16
- | **include_chrome_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Chrome App registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
17
- | **include_chrome_web_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Chrome Web Push registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
18
- | **include_android_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Android device registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
19
- | **include_aliases** | [**PlayerNotificationTargetIncludeAliases**](PlayerNotificationTargetIncludeAliases.md) | | [optional] |
12
+ | **include_ios_tokens** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using iOS device tokens. Warning: Only works with Production tokens. All non-alphanumeric characters must be removed from each token. If a token does not correspond to an existing user, a new user will be created. Example: ce777617da7f548fe7a9ab6febb56cf39fba6d38203... Limit of 2,000 entries per REST API call | [optional] |
13
+ | **include_wp_wns_uris** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Windows URIs. If a token does not correspond to an existing user, a new user will be created. Example: http://s.notify.live.net/u/1/bn1/HmQAAACPaLDr-... Limit of 2,000 entries per REST API call | [optional] |
14
+ | **include_amazon_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Amazon ADM registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: amzn1.adm-registration.v1.XpvSSUk0Rc3hTVVV... Limit of 2,000 entries per REST API call | [optional] |
15
+ | **include_chrome_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Chrome App registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
16
+ | **include_chrome_web_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Chrome Web Push registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
17
+ | **include_android_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Android device registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
18
+ | **include_aliases** | **Hash&lt;String, Array&lt;String&gt;&gt;** | Target specific users by aliases assigned via API. An alias can be an external_id, onesignal_id, or a custom alias. Accepts an object where keys are alias labels and values are arrays of alias IDs to include Example usage: { \&quot;external_id\&quot;: [\&quot;exId1\&quot;, \&quot;extId2\&quot;], \&quot;internal_label\&quot;: [\&quot;id1\&quot;, \&quot;id2\&quot;] } Not compatible with any other targeting parameters. REQUIRED: REST API Key Authentication Limit of 2,000 entries per REST API call Note: If targeting push, email, or sms subscribers with same ids, use with target_channel to indicate you are sending a push or email or sms. | [optional] |
20
19
  | **target_channel** | **String** | | [optional] |
21
20
  | **id** | **String** | | [optional] |
22
21
  | **value** | **Integer** | | [optional][readonly] |
@@ -32,13 +31,12 @@
32
31
  | **is_wp_wns** | **Boolean** | Indicates whether to send to all devices registered under your app&#39;s Windows platform. | [optional] |
33
32
  | **is_adm** | **Boolean** | Indicates whether to send to all devices registered under your app&#39;s Amazon Fire platform. | [optional] |
34
33
  | **is_chrome** | **Boolean** | This flag is not used for web push Please see isChromeWeb for sending to web push users. This flag only applies to Google Chrome Apps &amp; Extensions. Indicates whether to send to all devices registered under your app&#39;s Google Chrome Apps &amp; Extension platform. | [optional] |
35
- | **channel_for_external_user_ids** | **String** | Indicates if the message type when targeting with include_external_user_ids for cases where an email, sms, and/or push subscribers have the same external user id. Example: Use the string \&quot;push\&quot; to indicate you are sending a push notification or the string \&quot;email\&quot;for sending emails or \&quot;sms\&quot;for sending SMS. | [optional] |
36
34
  | **app_id** | **String** | Required: Your OneSignal Application ID, which can be found in Keys &amp; IDs. It is a UUID and looks similar to 8250eaf6-1a58-489e-b136-7c74a864b434. | |
37
35
  | **external_id** | **String** | [DEPRECATED] Correlation and idempotency key. A request received with this parameter will first look for another notification with the same external_id. If one exists, a notification will not be sent, and result of the previous operation will instead be returned. Therefore, if you plan on using this feature, it&#39;s important to use a good source of randomness to generate the UUID passed here. This key is only idempotent for 30 days. After 30 days, the notification could be removed from our system and a notification with the same external_id will be sent again. See Idempotent Notification Requests for more details writeOnly: true | [optional] |
38
36
  | **idempotency_key** | **String** | Correlation and idempotency key. A request received with this parameter will first look for another notification with the same idempotency key. If one exists, a notification will not be sent, and result of the previous operation will instead be returned. Therefore, if you plan on using this feature, it&#39;s important to use a good source of randomness to generate the UUID passed here. This key is only idempotent for 30 days. After 30 days, the notification could be removed from our system and a notification with the same idempotency key will be sent again. See Idempotent Notification Requests for more details writeOnly: true | [optional] |
39
- | **contents** | [**StringMap**](StringMap.md) | | [optional] |
40
- | **headings** | [**StringMap**](StringMap.md) | | [optional] |
41
- | **subtitle** | [**StringMap**](StringMap.md) | | [optional] |
37
+ | **contents** | [**LanguageStringMap**](LanguageStringMap.md) | | [optional] |
38
+ | **headings** | [**LanguageStringMap**](LanguageStringMap.md) | | [optional] |
39
+ | **subtitle** | [**LanguageStringMap**](LanguageStringMap.md) | | [optional] |
42
40
  | **data** | **Object** | Channel: Push Notifications Platform: Huawei A custom map of data that is passed back to your app. Same as using Additional Data within the dashboard. Can use up to 2048 bytes of data. Example: {\&quot;abc\&quot;: 123, \&quot;foo\&quot;: \&quot;bar\&quot;, \&quot;event_performed\&quot;: true, \&quot;amount\&quot;: 12.1} | [optional] |
43
41
  | **huawei_msg_type** | **String** | Channel: Push Notifications Platform: Huawei Use \&quot;data\&quot; or \&quot;message\&quot; depending on the type of notification you are sending. More details in Data &amp; Background Notifications. | [optional] |
44
42
  | **url** | **String** | Channel: Push Notifications Platform: All The URL to open in the browser when a user clicks on the notification. Note: iOS needs https or updated NSAppTransportSecurity in plist This field supports inline substitutions. Omit if including web_url or app_url Example: https://onesignal.com | [optional] |
@@ -55,7 +53,7 @@
55
53
  | **chrome_big_picture** | **String** | Channel: Push Notifications Platform: ChromeApp Large picture to display below the notification text. Must be a local URL. | [optional] |
56
54
  | **chrome_web_image** | **String** | Channel: Push Notifications Platform: Chrome 56+ Sets the web push notification&#39;s large image to be shown below the notification&#39;s title and text. Please see Web Push Notification Icons. | [optional] |
57
55
  | **buttons** | [**Array&lt;Button&gt;**](Button.md) | Channel: Push Notifications Platform: iOS 8.0+, Android 4.1+, and derivatives like Amazon Buttons to add to the notification. Icon only works for Android. Buttons show in reverse order of array position i.e. Last item in array shows as first button on device. Example: [{\&quot;id\&quot;: \&quot;id2\&quot;, \&quot;text\&quot;: \&quot;second button\&quot;, \&quot;icon\&quot;: \&quot;ic_menu_share\&quot;}, {\&quot;id\&quot;: \&quot;id1\&quot;, \&quot;text\&quot;: \&quot;first button\&quot;, \&quot;icon\&quot;: \&quot;ic_menu_send\&quot;}] | [optional] |
58
- | **web_buttons** | [**Array&lt;Button&gt;**](Button.md) | Channel: Push Notifications Platform: Chrome 48+ Add action buttons to the notification. The id field is required. Example: [{\&quot;id\&quot;: \&quot;like-button\&quot;, \&quot;text\&quot;: \&quot;Like\&quot;, \&quot;icon\&quot;: \&quot;http://i.imgur.com/N8SN8ZS.png\&quot;, \&quot;url\&quot;: \&quot;https://yoursite.com\&quot;}, {\&quot;id\&quot;: \&quot;read-more-button\&quot;, \&quot;text\&quot;: \&quot;Read more\&quot;, \&quot;icon\&quot;: \&quot;http://i.imgur.com/MIxJp1L.png\&quot;, \&quot;url\&quot;: \&quot;https://yoursite.com\&quot;}] | [optional] |
56
+ | **web_buttons** | [**Array&lt;WebButton&gt;**](WebButton.md) | Channel: Push Notifications Platform: Chrome 48+ Add action buttons to the notification. The id field is required. Example: [{\&quot;id\&quot;: \&quot;like-button\&quot;, \&quot;text\&quot;: \&quot;Like\&quot;, \&quot;icon\&quot;: \&quot;http://i.imgur.com/N8SN8ZS.png\&quot;, \&quot;url\&quot;: \&quot;https://yoursite.com\&quot;}, {\&quot;id\&quot;: \&quot;read-more-button\&quot;, \&quot;text\&quot;: \&quot;Read more\&quot;, \&quot;icon\&quot;: \&quot;http://i.imgur.com/MIxJp1L.png\&quot;, \&quot;url\&quot;: \&quot;https://yoursite.com\&quot;}] | [optional] |
59
57
  | **ios_category** | **String** | Channel: Push Notifications Platform: iOS Category APS payload, use with registerUserNotificationSettings:categories in your Objective-C / Swift code. Example: calendar category which contains actions like accept and decline iOS 10+ This will trigger your UNNotificationContentExtension whose ID matches this category. | [optional] |
60
58
  | **android_channel_id** | **String** | Channel: Push Notifications Platform: Android The Android Oreo Notification Category to send the notification under. See the Category documentation on creating one and getting it&#39;s id. | [optional] |
61
59
  | **huawei_channel_id** | **String** | Channel: Push Notifications Platform: Huawei The Android Oreo Notification Category to send the notification under. See the Category documentation on creating one and getting it&#39;s id. | [optional] |
@@ -101,6 +99,8 @@
101
99
  | **thread_id** | **String** | Channel: Push Notifications Platform: iOS 12+ This parameter is supported in iOS 12 and above. It allows you to group related notifications together. If two notifications have the same thread-id, they will both be added to the same group. | [optional] |
102
100
  | **summary_arg** | **String** | Channel: Push Notifications Platform: iOS 12+ When using thread_id to create grouped notifications in iOS 12+, you can also control the summary. For example, a grouped notification can say \&quot;12 more notifications from John Doe\&quot;. The summary_arg lets you set the name of the person/thing the notifications are coming from, and will show up as \&quot;X more notifications from summary_arg\&quot; | [optional] |
103
101
  | **summary_arg_count** | **Integer** | Channel: Push Notifications Platform: iOS 12+ When using thread_id, you can also control the count of the number of notifications in the group. For example, if the group already has 12 notifications, and you send a new notification with summary_arg_count &#x3D; 2, the new total will be 14 and the summary will be \&quot;14 more notifications from summary_arg\&quot; | [optional] |
102
+ | **ios_relevance_score** | **Float** | Channel: Push Notifications Platform: iOS 15+ A score to be set per notification to indicate how it should be displayed when grouped. Use a float between 0-1. | [optional] |
103
+ | **ios_interruption_level** | **String** | Channel: Push Notifications Platform: iOS 15+ Focus Modes and Interruption Levels indicate the priority and delivery timing of a notification, to \&quot;interrupt\&quot; the user. Can choose from options: [&#39;active&#39;, &#39;passive&#39;, &#39;time_sensitive&#39;, &#39;critical&#39;]. Default is active. | [optional] |
104
104
  | **email_subject** | **String** | Channel: Email Required. The subject of the email. | [optional] |
105
105
  | **email_body** | **String** | Channel: Email Required unless template_id is set. HTML suported The body of the email you wish to send. Typically, customers include their own HTML templates here. Must include [unsubscribe_url] in an &lt;a&gt; tag somewhere in the email. Note: any malformed HTML content will be sent to users. Please double-check your HTML is valid. | [optional] |
106
106
  | **email_from_name** | **String** | Channel: Email The name the email is from. If not specified, will default to \&quot;from name\&quot; set in the OneSignal Dashboard Email Settings. | [optional] |
@@ -109,7 +109,7 @@
109
109
  | **include_unsubscribed** | **Boolean** | Channel: Email Default is &#x60;false&#x60;. This field is used to send transactional notifications. If set to &#x60;true&#x60;, this notification will also be sent to unsubscribed emails. If a &#x60;template_id&#x60; is provided, the &#x60;include_unsubscribed&#x60; value from the template will be inherited. If you are using a third-party ESP, this field requires the ESP&#39;s list of unsubscribed emails to be cleared. | [optional] |
110
110
  | **sms_from** | **String** | Channel: SMS Phone Number used to send SMS. Should be a registered Twilio phone number in E.164 format. | [optional] |
111
111
  | **sms_media_urls** | **Array&lt;String&gt;** | Channel: SMS URLs for the media files to be attached to the SMS content. Limit: 10 media urls with a total max. size of 5MBs. | [optional] |
112
- | **filters** | [**Array&lt;Filter&gt;**](Filter.md) | | [optional] |
112
+ | **filters** | [**Array&lt;FilterExpression&gt;**](FilterExpression.md) | | [optional] |
113
113
  | **custom_data** | **Object** | Channel: All JSON object that can be used as a source of message personalization data for fields that support tag variable substitution. Push, SMS: Can accept up to 2048 bytes of valid JSON. Email: Can accept up to 10000 bytes of valid JSON. Example: {\&quot;order_id\&quot;: 123, \&quot;currency\&quot;: \&quot;USD\&quot;, \&quot;amount\&quot;: 25} | [optional] |
114
114
  | **send_after** | **Time** | Channel: All Schedule notification for future delivery. API defaults to UTC -1100 Examples: All examples are the exact same date &amp; time. \&quot;Thu Sep 24 2015 14:00:00 GMT-0700 (PDT)\&quot; \&quot;September 24th 2015, 2:00:00 pm UTC-07:00\&quot; \&quot;2015-09-24 14:00:00 GMT-0700\&quot; \&quot;Sept 24 2015 14:00:00 GMT-0700\&quot; \&quot;Thu Sep 24 2015 14:00:00 GMT-0700 (Pacific Daylight Time)\&quot; Note: SMS currently only supports send_after parameter. | [optional] |
115
115
 
@@ -121,8 +121,7 @@ require 'onesignal'
121
121
  instance = OneSignal::Notification.new(
122
122
  included_segments: null,
123
123
  excluded_segments: null,
124
- include_player_ids: null,
125
- include_external_user_ids: null,
124
+ include_subscription_ids: null,
126
125
  include_email_tokens: null,
127
126
  include_phone_numbers: null,
128
127
  include_ios_tokens: null,
@@ -147,7 +146,6 @@ instance = OneSignal::Notification.new(
147
146
  is_wp_wns: null,
148
147
  is_adm: null,
149
148
  is_chrome: null,
150
- channel_for_external_user_ids: null,
151
149
  app_id: null,
152
150
  external_id: null,
153
151
  idempotency_key: null,
@@ -216,6 +214,8 @@ instance = OneSignal::Notification.new(
216
214
  thread_id: null,
217
215
  summary_arg: null,
218
216
  summary_arg_count: null,
217
+ ios_relevance_score: null,
218
+ ios_interruption_level: null,
219
219
  email_subject: null,
220
220
  email_body: null,
221
221
  email_from_name: null,
@@ -6,17 +6,16 @@
6
6
  | ---- | ---- | ----------- | ----- |
7
7
  | **included_segments** | **Array&lt;String&gt;** | The segment names you want to target. Users in these segments will receive a notification. This targeting parameter is only compatible with excluded_segments. Example: [\&quot;Active Users\&quot;, \&quot;Inactive Users\&quot;] | [optional] |
8
8
  | **excluded_segments** | **Array&lt;String&gt;** | Segment that will be excluded when sending. Users in these segments will not receive a notification, even if they were included in included_segments. This targeting parameter is only compatible with included_segments. Example: [\&quot;Active Users\&quot;, \&quot;Inactive Users\&quot;] | [optional] |
9
- | **include_player_ids** | **Array&lt;String&gt;** | Specific playerids to send your notification to. _Does not require API Auth Key. Do not combine with other targeting parameters. Not compatible with any other targeting parameters. Example: [\&quot;1dd608f2-c6a1-11e3-851d-000c2940e62c\&quot;] Limit of 2,000 entries per REST API call | [optional] |
10
- | **include_external_user_ids** | **Array&lt;String&gt;** | Target specific devices by custom user IDs assigned via API. Not compatible with any other targeting parameters Example: [\&quot;custom-id-assigned-by-api\&quot;] REQUIRED: REST API Key Authentication Limit of 2,000 entries per REST API call. Note: If targeting push, email, or sms subscribers with same ids, use with channel_for_external_user_ids to indicate you are sending a push or email or sms. | [optional] |
9
+ | **include_subscription_ids** | **Array&lt;String&gt;** | Specific subscription ids to send your notification to. _Does not require API Auth Key._ Not compatible with any other targeting parameters. Example: [\&quot;1dd608f2-c6a1-11e3-851d-000c2940e62c\&quot;] Limit of 2,000 entries per REST API call | [optional] |
11
10
  | **include_email_tokens** | **Array&lt;String&gt;** | Recommended for Sending Emails - Target specific email addresses. If an email does not correspond to an existing user, a new user will be created. Example: nick@catfac.ts Limit of 2,000 entries per REST API call | [optional] |
12
11
  | **include_phone_numbers** | **Array&lt;String&gt;** | Recommended for Sending SMS - Target specific phone numbers. The phone number should be in the E.164 format. Phone number should be an existing subscriber on OneSignal. Refer our docs to learn how to add phone numbers to OneSignal. Example phone number: +1999999999 Limit of 2,000 entries per REST API call | [optional] |
13
- | **include_ios_tokens** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using iOS device tokens. Warning: Only works with Production tokens. All non-alphanumeric characters must be removed from each token. If a token does not correspond to an existing user, a new user will be created. Example: ce777617da7f548fe7a9ab6febb56cf39fba6d38203... Limit of 2,000 entries per REST API call | [optional] |
14
- | **include_wp_wns_uris** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Windows URIs. If a token does not correspond to an existing user, a new user will be created. Example: http://s.notify.live.net/u/1/bn1/HmQAAACPaLDr-... Limit of 2,000 entries per REST API call | [optional] |
15
- | **include_amazon_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Amazon ADM registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: amzn1.adm-registration.v1.XpvSSUk0Rc3hTVVV... Limit of 2,000 entries per REST API call | [optional] |
16
- | **include_chrome_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Chrome App registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
17
- | **include_chrome_web_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Chrome Web Push registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
18
- | **include_android_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Android device registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
19
- | **include_aliases** | [**PlayerNotificationTargetIncludeAliases**](PlayerNotificationTargetIncludeAliases.md) | | [optional] |
12
+ | **include_ios_tokens** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using iOS device tokens. Warning: Only works with Production tokens. All non-alphanumeric characters must be removed from each token. If a token does not correspond to an existing user, a new user will be created. Example: ce777617da7f548fe7a9ab6febb56cf39fba6d38203... Limit of 2,000 entries per REST API call | [optional] |
13
+ | **include_wp_wns_uris** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Windows URIs. If a token does not correspond to an existing user, a new user will be created. Example: http://s.notify.live.net/u/1/bn1/HmQAAACPaLDr-... Limit of 2,000 entries per REST API call | [optional] |
14
+ | **include_amazon_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Amazon ADM registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: amzn1.adm-registration.v1.XpvSSUk0Rc3hTVVV... Limit of 2,000 entries per REST API call | [optional] |
15
+ | **include_chrome_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Chrome App registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
16
+ | **include_chrome_web_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Chrome Web Push registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
17
+ | **include_android_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Android device registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
18
+ | **include_aliases** | **Hash&lt;String, Array&lt;String&gt;&gt;** | Target specific users by aliases assigned via API. An alias can be an external_id, onesignal_id, or a custom alias. Accepts an object where keys are alias labels and values are arrays of alias IDs to include Example usage: { \&quot;external_id\&quot;: [\&quot;exId1\&quot;, \&quot;extId2\&quot;], \&quot;internal_label\&quot;: [\&quot;id1\&quot;, \&quot;id2\&quot;] } Not compatible with any other targeting parameters. REQUIRED: REST API Key Authentication Limit of 2,000 entries per REST API call Note: If targeting push, email, or sms subscribers with same ids, use with target_channel to indicate you are sending a push or email or sms. | [optional] |
20
19
  | **target_channel** | **String** | | [optional] |
21
20
 
22
21
  ## Example
@@ -27,8 +26,7 @@ require 'onesignal'
27
26
  instance = OneSignal::NotificationTarget.new(
28
27
  included_segments: null,
29
28
  excluded_segments: null,
30
- include_player_ids: null,
31
- include_external_user_ids: null,
29
+ include_subscription_ids: null,
32
30
  include_email_tokens: null,
33
31
  include_phone_numbers: null,
34
32
  include_ios_tokens: null,
@@ -6,17 +6,16 @@
6
6
  | ---- | ---- | ----------- | ----- |
7
7
  | **included_segments** | **Array&lt;String&gt;** | The segment names you want to target. Users in these segments will receive a notification. This targeting parameter is only compatible with excluded_segments. Example: [\&quot;Active Users\&quot;, \&quot;Inactive Users\&quot;] | [optional] |
8
8
  | **excluded_segments** | **Array&lt;String&gt;** | Segment that will be excluded when sending. Users in these segments will not receive a notification, even if they were included in included_segments. This targeting parameter is only compatible with included_segments. Example: [\&quot;Active Users\&quot;, \&quot;Inactive Users\&quot;] | [optional] |
9
- | **include_player_ids** | **Array&lt;String&gt;** | Specific playerids to send your notification to. _Does not require API Auth Key. Do not combine with other targeting parameters. Not compatible with any other targeting parameters. Example: [\&quot;1dd608f2-c6a1-11e3-851d-000c2940e62c\&quot;] Limit of 2,000 entries per REST API call | [optional] |
10
- | **include_external_user_ids** | **Array&lt;String&gt;** | Target specific devices by custom user IDs assigned via API. Not compatible with any other targeting parameters Example: [\&quot;custom-id-assigned-by-api\&quot;] REQUIRED: REST API Key Authentication Limit of 2,000 entries per REST API call. Note: If targeting push, email, or sms subscribers with same ids, use with channel_for_external_user_ids to indicate you are sending a push or email or sms. | [optional] |
9
+ | **include_subscription_ids** | **Array&lt;String&gt;** | Specific subscription ids to send your notification to. _Does not require API Auth Key._ Not compatible with any other targeting parameters. Example: [\&quot;1dd608f2-c6a1-11e3-851d-000c2940e62c\&quot;] Limit of 2,000 entries per REST API call | [optional] |
11
10
  | **include_email_tokens** | **Array&lt;String&gt;** | Recommended for Sending Emails - Target specific email addresses. If an email does not correspond to an existing user, a new user will be created. Example: nick@catfac.ts Limit of 2,000 entries per REST API call | [optional] |
12
11
  | **include_phone_numbers** | **Array&lt;String&gt;** | Recommended for Sending SMS - Target specific phone numbers. The phone number should be in the E.164 format. Phone number should be an existing subscriber on OneSignal. Refer our docs to learn how to add phone numbers to OneSignal. Example phone number: +1999999999 Limit of 2,000 entries per REST API call | [optional] |
13
- | **include_ios_tokens** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using iOS device tokens. Warning: Only works with Production tokens. All non-alphanumeric characters must be removed from each token. If a token does not correspond to an existing user, a new user will be created. Example: ce777617da7f548fe7a9ab6febb56cf39fba6d38203... Limit of 2,000 entries per REST API call | [optional] |
14
- | **include_wp_wns_uris** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Windows URIs. If a token does not correspond to an existing user, a new user will be created. Example: http://s.notify.live.net/u/1/bn1/HmQAAACPaLDr-... Limit of 2,000 entries per REST API call | [optional] |
15
- | **include_amazon_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Amazon ADM registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: amzn1.adm-registration.v1.XpvSSUk0Rc3hTVVV... Limit of 2,000 entries per REST API call | [optional] |
16
- | **include_chrome_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Chrome App registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
17
- | **include_chrome_web_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Chrome Web Push registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
18
- | **include_android_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_player_ids or include_external_user_ids instead. Target using Android device registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
19
- | **include_aliases** | [**PlayerNotificationTargetIncludeAliases**](PlayerNotificationTargetIncludeAliases.md) | | [optional] |
12
+ | **include_ios_tokens** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using iOS device tokens. Warning: Only works with Production tokens. All non-alphanumeric characters must be removed from each token. If a token does not correspond to an existing user, a new user will be created. Example: ce777617da7f548fe7a9ab6febb56cf39fba6d38203... Limit of 2,000 entries per REST API call | [optional] |
13
+ | **include_wp_wns_uris** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Windows URIs. If a token does not correspond to an existing user, a new user will be created. Example: http://s.notify.live.net/u/1/bn1/HmQAAACPaLDr-... Limit of 2,000 entries per REST API call | [optional] |
14
+ | **include_amazon_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Amazon ADM registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: amzn1.adm-registration.v1.XpvSSUk0Rc3hTVVV... Limit of 2,000 entries per REST API call | [optional] |
15
+ | **include_chrome_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Chrome App registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
16
+ | **include_chrome_web_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Chrome Web Push registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
17
+ | **include_android_reg_ids** | **Array&lt;String&gt;** | Not Recommended: Please consider using include_subscription_ids or include_aliases instead. Target using Android device registration IDs. If a token does not correspond to an existing user, a new user will be created. Example: APA91bEeiUeSukAAUdnw3O2RB45FWlSpgJ7Ji_... Limit of 2,000 entries per REST API call | [optional] |
18
+ | **include_aliases** | **Hash&lt;String, Array&lt;String&gt;&gt;** | Target specific users by aliases assigned via API. An alias can be an external_id, onesignal_id, or a custom alias. Accepts an object where keys are alias labels and values are arrays of alias IDs to include Example usage: { \&quot;external_id\&quot;: [\&quot;exId1\&quot;, \&quot;extId2\&quot;], \&quot;internal_label\&quot;: [\&quot;id1\&quot;, \&quot;id2\&quot;] } Not compatible with any other targeting parameters. REQUIRED: REST API Key Authentication Limit of 2,000 entries per REST API call Note: If targeting push, email, or sms subscribers with same ids, use with target_channel to indicate you are sending a push or email or sms. | [optional] |
20
19
  | **target_channel** | **String** | | [optional] |
21
20
  | **id** | **String** | | [optional] |
22
21
  | **value** | **Integer** | | [optional][readonly] |
@@ -32,13 +31,12 @@
32
31
  | **is_wp_wns** | **Boolean** | Indicates whether to send to all devices registered under your app&#39;s Windows platform. | [optional] |
33
32
  | **is_adm** | **Boolean** | Indicates whether to send to all devices registered under your app&#39;s Amazon Fire platform. | [optional] |
34
33
  | **is_chrome** | **Boolean** | This flag is not used for web push Please see isChromeWeb for sending to web push users. This flag only applies to Google Chrome Apps &amp; Extensions. Indicates whether to send to all devices registered under your app&#39;s Google Chrome Apps &amp; Extension platform. | [optional] |
35
- | **channel_for_external_user_ids** | **String** | Indicates if the message type when targeting with include_external_user_ids for cases where an email, sms, and/or push subscribers have the same external user id. Example: Use the string \&quot;push\&quot; to indicate you are sending a push notification or the string \&quot;email\&quot;for sending emails or \&quot;sms\&quot;for sending SMS. | [optional] |
36
34
  | **app_id** | **String** | Required: Your OneSignal Application ID, which can be found in Keys &amp; IDs. It is a UUID and looks similar to 8250eaf6-1a58-489e-b136-7c74a864b434. | |
37
35
  | **external_id** | **String** | [DEPRECATED] Correlation and idempotency key. A request received with this parameter will first look for another notification with the same external_id. If one exists, a notification will not be sent, and result of the previous operation will instead be returned. Therefore, if you plan on using this feature, it&#39;s important to use a good source of randomness to generate the UUID passed here. This key is only idempotent for 30 days. After 30 days, the notification could be removed from our system and a notification with the same external_id will be sent again. See Idempotent Notification Requests for more details writeOnly: true | [optional] |
38
36
  | **idempotency_key** | **String** | Correlation and idempotency key. A request received with this parameter will first look for another notification with the same idempotency key. If one exists, a notification will not be sent, and result of the previous operation will instead be returned. Therefore, if you plan on using this feature, it&#39;s important to use a good source of randomness to generate the UUID passed here. This key is only idempotent for 30 days. After 30 days, the notification could be removed from our system and a notification with the same idempotency key will be sent again. See Idempotent Notification Requests for more details writeOnly: true | [optional] |
39
- | **contents** | [**StringMap**](StringMap.md) | | [optional] |
40
- | **headings** | [**StringMap**](StringMap.md) | | [optional] |
41
- | **subtitle** | [**StringMap**](StringMap.md) | | [optional] |
37
+ | **contents** | [**LanguageStringMap**](LanguageStringMap.md) | | [optional] |
38
+ | **headings** | [**LanguageStringMap**](LanguageStringMap.md) | | [optional] |
39
+ | **subtitle** | [**LanguageStringMap**](LanguageStringMap.md) | | [optional] |
42
40
  | **data** | **Object** | Channel: Push Notifications Platform: Huawei A custom map of data that is passed back to your app. Same as using Additional Data within the dashboard. Can use up to 2048 bytes of data. Example: {\&quot;abc\&quot;: 123, \&quot;foo\&quot;: \&quot;bar\&quot;, \&quot;event_performed\&quot;: true, \&quot;amount\&quot;: 12.1} | [optional] |
43
41
  | **huawei_msg_type** | **String** | Channel: Push Notifications Platform: Huawei Use \&quot;data\&quot; or \&quot;message\&quot; depending on the type of notification you are sending. More details in Data &amp; Background Notifications. | [optional] |
44
42
  | **url** | **String** | Channel: Push Notifications Platform: All The URL to open in the browser when a user clicks on the notification. Note: iOS needs https or updated NSAppTransportSecurity in plist This field supports inline substitutions. Omit if including web_url or app_url Example: https://onesignal.com | [optional] |
@@ -55,7 +53,7 @@
55
53
  | **chrome_big_picture** | **String** | Channel: Push Notifications Platform: ChromeApp Large picture to display below the notification text. Must be a local URL. | [optional] |
56
54
  | **chrome_web_image** | **String** | Channel: Push Notifications Platform: Chrome 56+ Sets the web push notification&#39;s large image to be shown below the notification&#39;s title and text. Please see Web Push Notification Icons. | [optional] |
57
55
  | **buttons** | [**Array&lt;Button&gt;**](Button.md) | Channel: Push Notifications Platform: iOS 8.0+, Android 4.1+, and derivatives like Amazon Buttons to add to the notification. Icon only works for Android. Buttons show in reverse order of array position i.e. Last item in array shows as first button on device. Example: [{\&quot;id\&quot;: \&quot;id2\&quot;, \&quot;text\&quot;: \&quot;second button\&quot;, \&quot;icon\&quot;: \&quot;ic_menu_share\&quot;}, {\&quot;id\&quot;: \&quot;id1\&quot;, \&quot;text\&quot;: \&quot;first button\&quot;, \&quot;icon\&quot;: \&quot;ic_menu_send\&quot;}] | [optional] |
58
- | **web_buttons** | [**Array&lt;Button&gt;**](Button.md) | Channel: Push Notifications Platform: Chrome 48+ Add action buttons to the notification. The id field is required. Example: [{\&quot;id\&quot;: \&quot;like-button\&quot;, \&quot;text\&quot;: \&quot;Like\&quot;, \&quot;icon\&quot;: \&quot;http://i.imgur.com/N8SN8ZS.png\&quot;, \&quot;url\&quot;: \&quot;https://yoursite.com\&quot;}, {\&quot;id\&quot;: \&quot;read-more-button\&quot;, \&quot;text\&quot;: \&quot;Read more\&quot;, \&quot;icon\&quot;: \&quot;http://i.imgur.com/MIxJp1L.png\&quot;, \&quot;url\&quot;: \&quot;https://yoursite.com\&quot;}] | [optional] |
56
+ | **web_buttons** | [**Array&lt;WebButton&gt;**](WebButton.md) | Channel: Push Notifications Platform: Chrome 48+ Add action buttons to the notification. The id field is required. Example: [{\&quot;id\&quot;: \&quot;like-button\&quot;, \&quot;text\&quot;: \&quot;Like\&quot;, \&quot;icon\&quot;: \&quot;http://i.imgur.com/N8SN8ZS.png\&quot;, \&quot;url\&quot;: \&quot;https://yoursite.com\&quot;}, {\&quot;id\&quot;: \&quot;read-more-button\&quot;, \&quot;text\&quot;: \&quot;Read more\&quot;, \&quot;icon\&quot;: \&quot;http://i.imgur.com/MIxJp1L.png\&quot;, \&quot;url\&quot;: \&quot;https://yoursite.com\&quot;}] | [optional] |
59
57
  | **ios_category** | **String** | Channel: Push Notifications Platform: iOS Category APS payload, use with registerUserNotificationSettings:categories in your Objective-C / Swift code. Example: calendar category which contains actions like accept and decline iOS 10+ This will trigger your UNNotificationContentExtension whose ID matches this category. | [optional] |
60
58
  | **android_channel_id** | **String** | Channel: Push Notifications Platform: Android The Android Oreo Notification Category to send the notification under. See the Category documentation on creating one and getting it&#39;s id. | [optional] |
61
59
  | **huawei_channel_id** | **String** | Channel: Push Notifications Platform: Huawei The Android Oreo Notification Category to send the notification under. See the Category documentation on creating one and getting it&#39;s id. | [optional] |
@@ -101,6 +99,8 @@
101
99
  | **thread_id** | **String** | Channel: Push Notifications Platform: iOS 12+ This parameter is supported in iOS 12 and above. It allows you to group related notifications together. If two notifications have the same thread-id, they will both be added to the same group. | [optional] |
102
100
  | **summary_arg** | **String** | Channel: Push Notifications Platform: iOS 12+ When using thread_id to create grouped notifications in iOS 12+, you can also control the summary. For example, a grouped notification can say \&quot;12 more notifications from John Doe\&quot;. The summary_arg lets you set the name of the person/thing the notifications are coming from, and will show up as \&quot;X more notifications from summary_arg\&quot; | [optional] |
103
101
  | **summary_arg_count** | **Integer** | Channel: Push Notifications Platform: iOS 12+ When using thread_id, you can also control the count of the number of notifications in the group. For example, if the group already has 12 notifications, and you send a new notification with summary_arg_count &#x3D; 2, the new total will be 14 and the summary will be \&quot;14 more notifications from summary_arg\&quot; | [optional] |
102
+ | **ios_relevance_score** | **Float** | Channel: Push Notifications Platform: iOS 15+ A score to be set per notification to indicate how it should be displayed when grouped. Use a float between 0-1. | [optional] |
103
+ | **ios_interruption_level** | **String** | Channel: Push Notifications Platform: iOS 15+ Focus Modes and Interruption Levels indicate the priority and delivery timing of a notification, to \&quot;interrupt\&quot; the user. Can choose from options: [&#39;active&#39;, &#39;passive&#39;, &#39;time_sensitive&#39;, &#39;critical&#39;]. Default is active. | [optional] |
104
104
  | **email_subject** | **String** | Channel: Email Required. The subject of the email. | [optional] |
105
105
  | **email_body** | **String** | Channel: Email Required unless template_id is set. HTML suported The body of the email you wish to send. Typically, customers include their own HTML templates here. Must include [unsubscribe_url] in an &lt;a&gt; tag somewhere in the email. Note: any malformed HTML content will be sent to users. Please double-check your HTML is valid. | [optional] |
106
106
  | **email_from_name** | **String** | Channel: Email The name the email is from. If not specified, will default to \&quot;from name\&quot; set in the OneSignal Dashboard Email Settings. | [optional] |
@@ -109,7 +109,7 @@
109
109
  | **include_unsubscribed** | **Boolean** | Channel: Email Default is &#x60;false&#x60;. This field is used to send transactional notifications. If set to &#x60;true&#x60;, this notification will also be sent to unsubscribed emails. If a &#x60;template_id&#x60; is provided, the &#x60;include_unsubscribed&#x60; value from the template will be inherited. If you are using a third-party ESP, this field requires the ESP&#39;s list of unsubscribed emails to be cleared. | [optional] |
110
110
  | **sms_from** | **String** | Channel: SMS Phone Number used to send SMS. Should be a registered Twilio phone number in E.164 format. | [optional] |
111
111
  | **sms_media_urls** | **Array&lt;String&gt;** | Channel: SMS URLs for the media files to be attached to the SMS content. Limit: 10 media urls with a total max. size of 5MBs. | [optional] |
112
- | **filters** | [**Array&lt;Filter&gt;**](Filter.md) | | [optional] |
112
+ | **filters** | [**Array&lt;FilterExpression&gt;**](FilterExpression.md) | | [optional] |
113
113
  | **custom_data** | **Object** | Channel: All JSON object that can be used as a source of message personalization data for fields that support tag variable substitution. Push, SMS: Can accept up to 2048 bytes of valid JSON. Email: Can accept up to 10000 bytes of valid JSON. Example: {\&quot;order_id\&quot;: 123, \&quot;currency\&quot;: \&quot;USD\&quot;, \&quot;amount\&quot;: 25} | [optional] |
114
114
  | **successful** | **Integer** | Number of notifications that were successfully delivered. | [optional] |
115
115
  | **failed** | **Integer** | Number of notifications that could not be delivered due to those devices being unsubscribed. | [optional] |
@@ -131,8 +131,7 @@ require 'onesignal'
131
131
  instance = OneSignal::NotificationWithMeta.new(
132
132
  included_segments: null,
133
133
  excluded_segments: null,
134
- include_player_ids: null,
135
- include_external_user_ids: null,
134
+ include_subscription_ids: null,
136
135
  include_email_tokens: null,
137
136
  include_phone_numbers: null,
138
137
  include_ios_tokens: null,
@@ -157,7 +156,6 @@ instance = OneSignal::NotificationWithMeta.new(
157
156
  is_wp_wns: null,
158
157
  is_adm: null,
159
158
  is_chrome: null,
160
- channel_for_external_user_ids: null,
161
159
  app_id: null,
162
160
  external_id: null,
163
161
  idempotency_key: null,
@@ -226,6 +224,8 @@ instance = OneSignal::NotificationWithMeta.new(
226
224
  thread_id: null,
227
225
  summary_arg: null,
228
226
  summary_arg_count: null,
227
+ ios_relevance_score: null,
228
+ ios_interruption_level: null,
229
229
  email_subject: null,
230
230
  email_body: null,
231
231
  email_from_name: null,
@@ -1,4 +1,4 @@
1
- # OneSignal::InlineResponse202
1
+ # OneSignal::PropertiesBody
2
2
 
3
3
  ## Properties
4
4
 
@@ -11,7 +11,7 @@
11
11
  ```ruby
12
12
  require 'onesignal'
13
13
 
14
- instance = OneSignal::InlineResponse202.new(
14
+ instance = OneSignal::PropertiesBody.new(
15
15
  properties: null
16
16
  )
17
17
  ```
@@ -4,8 +4,8 @@
4
4
 
5
5
  | Name | Type | Description | Notes |
6
6
  | ---- | ---- | ----------- | ----- |
7
- | **session_time** | **Float** | | [optional] |
8
- | **session_count** | **Float** | | [optional] |
7
+ | **session_time** | **Integer** | | [optional] |
8
+ | **session_count** | **Integer** | | [optional] |
9
9
  | **purchases** | [**Array&lt;Purchase&gt;**](Purchase.md) | | [optional] |
10
10
 
11
11
  ## Example
@@ -10,8 +10,8 @@
10
10
  | **lat** | **Float** | | [optional] |
11
11
  | **long** | **Float** | | [optional] |
12
12
  | **country** | **String** | | [optional] |
13
- | **first_active** | **Float** | | [optional] |
14
- | **last_active** | **Float** | | [optional] |
13
+ | **first_active** | **Integer** | | [optional] |
14
+ | **last_active** | **Integer** | | [optional] |
15
15
  | **amount_spent** | **Float** | | [optional] |
16
16
  | **purchases** | [**Array&lt;Purchase&gt;**](Purchase.md) | | [optional] |
17
17
  | **ip** | **String** | | [optional] |
data/docs/Purchase.md CHANGED
@@ -7,7 +7,7 @@
7
7
  | **sku** | **String** | The unique identifier of the purchased item. | |
8
8
  | **amount** | **String** | The amount, in USD, spent purchasing the item. | |
9
9
  | **iso** | **String** | The 3-letter ISO 4217 currency code. Required for correct storage and conversion of amount. | |
10
- | **count** | **Float** | | [optional] |
10
+ | **count** | **Integer** | | [optional] |
11
11
 
12
12
  ## Example
13
13
 
@@ -0,0 +1,20 @@
1
+ # OneSignal::RateLimitError
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **errors** | **Array&lt;String&gt;** | | [optional] |
8
+ | **limit** | **String** | | [optional] |
9
+
10
+ ## Example
11
+
12
+ ```ruby
13
+ require 'onesignal'
14
+
15
+ instance = OneSignal::RateLimitError.new(
16
+ errors: null,
17
+ limit: null
18
+ )
19
+ ```
20
+
data/docs/Segment.md CHANGED
@@ -6,7 +6,7 @@
6
6
  | ---- | ---- | ----------- | ----- |
7
7
  | **id** | **String** | UUID of the segment. If left empty, it will be assigned automaticaly. | [optional] |
8
8
  | **name** | **String** | Name of the segment. You&#39;ll see this name on the Web UI. | |
9
- | **filters** | [**Array&lt;FilterExpressions&gt;**](FilterExpressions.md) | Filter or operators the segment will have. For a list of available filters with details, please see Send to Users Based on Filters. | |
9
+ | **filters** | [**Array&lt;FilterExpression&gt;**](FilterExpression.md) | Filter or operators the segment will have. For a list of available filters with details, please see Send to Users Based on Filters. | |
10
10
 
11
11
  ## Example
12
12
 
@@ -0,0 +1,30 @@
1
+ # OneSignal::SegmentData
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **id** | **String** | The segment ID | [optional] |
8
+ | **name** | **String** | The segment name | [optional] |
9
+ | **created_at** | **String** | Date segment created | [optional] |
10
+ | **updated_at** | **String** | Date segment last updated | [optional] |
11
+ | **app_id** | **String** | The app id | [optional] |
12
+ | **read_only** | **Boolean** | Is the segment read only? | [optional] |
13
+ | **is_active** | **Boolean** | Is the segment active? | [optional] |
14
+
15
+ ## Example
16
+
17
+ ```ruby
18
+ require 'onesignal'
19
+
20
+ instance = OneSignal::SegmentData.new(
21
+ id: null,
22
+ name: null,
23
+ created_at: null,
24
+ updated_at: null,
25
+ app_id: null,
26
+ read_only: null,
27
+ is_active: null
28
+ )
29
+ ```
30
+