onesignal 2.2.1 → 5.1.0.pre.beta1

data/spec/api/default_api_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT
@@ -32,28 +32,41 @@ describe 'DefaultApi' do
     end
   end
 
-  # unit tests for begin_live_activity
-  # Start Live Activity
-  # Starts a Live Activity
-  # @param app_id The OneSignal App ID for your app.  Available in Keys & IDs.
-  # @param activity_id Live Activity record ID
-  # @param begin_live_activity_request 
+  # unit tests for cancel_notification
+  # Stop a scheduled or currently outgoing notification
+  # Used to stop a scheduled or currently outgoing notification
+  # @param app_id 
+  # @param notification_id 
   # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'begin_live_activity test' do
+  # @return [GenericSuccessBoolResponse]
+  describe 'cancel_notification test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
   end
 
-  # unit tests for cancel_notification
-  # Stop a scheduled or currently outgoing notification
-  # Used to stop a scheduled or currently outgoing notification
+  # unit tests for create_alias
+  # Upserts one or more Aliases to an existing User identified by (:alias_label, :alias_id).
   # @param app_id 
-  # @param notification_id 
+  # @param alias_label 
+  # @param alias_id 
+  # @param user_identity_body 
   # @param [Hash] opts the optional parameters
-  # @return [CancelNotificationSuccessResponse]
-  describe 'cancel_notification test' do
+  # @return [UserIdentityBody]
+  describe 'create_alias test' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  # unit tests for create_alias_by_subscription
+  # Upserts one or more Aliases for the User identified by :subscription_id.
+  # @param app_id 
+  # @param subscription_id 
+  # @param user_identity_body 
+  # @param [Hash] opts the optional parameters
+  # @return [UserIdentityBody]
+  describe 'create_alias_by_subscription test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
@@ -83,26 +96,14 @@ describe 'DefaultApi' do
     end
   end
 
-  # unit tests for create_player
-  # Add a device
-  # Register a new device to one of your OneSignal apps 🚧 Don't use this This API endpoint is designed to be used from our open source Mobile and Web Push SDKs. It is not designed for developers to use it directly, unless instructed to do so by OneSignal support. If you use this method instead of our SDKs, many OneSignal features such as conversion tracking, timezone tracking, language detection, and rich-push won't work out of the box. It will also make it harder to identify possible setup issues. This method is used to register a new device with OneSignal. If a device is already registered with the specified identifier, then this will update the existing device record instead of creating a new one. The returned player is a player / user ID. Use the returned ID to send push notifications to this specific user later, or to include this player when sending to a set of users. 🚧 iOS Must set test_type to 1 when building your iOS app as development. Omit this field in your production app builds. 
-  # @param player 
-  # @param [Hash] opts the optional parameters
-  # @return [CreatePlayerSuccessResponse]
-  describe 'create_player test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for create_segments
-  # Create Segments
-  # Create segments visible and usable in the dashboard and API - Required: OneSignal Paid Plan The Create Segment method is used when you want your server to programmatically create a segment instead of using the OneSignal Dashboard UI. Just like creating Segments from the dashboard you can pass in filters with multiple \"AND\" or \"OR\" operator's. 🚧 Does Not Update Segments This endpoint will only create segments, it does not edit or update currently created Segments. You will need to use the Delete Segments endpoint and re-create it with this endpoint to edit. 
+  # unit tests for create_segment
+  # Create Segment
+  # Create a segment visible and usable in the dashboard and API - Required: OneSignal Paid Plan The Create Segment method is used when you want your server to programmatically create a segment instead of using the OneSignal Dashboard UI. Just like creating Segments from the dashboard you can pass in filters with multiple \"AND\" or \"OR\" operator's. 🚧 Does Not Update Segments This endpoint will only create segments, it does not edit or update currently created Segments. You will need to use the Delete Segment endpoint and re-create it with this endpoint to edit. 
   # @param app_id The OneSignal App ID for your app.  Available in Keys & IDs.
   # @param [Hash] opts the optional parameters
   # @option opts [Segment] :segment 
   # @return [CreateSegmentSuccessResponse]
-  describe 'create_segments test' do
+  describe 'create_segment test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
@@ -113,9 +114,9 @@ describe 'DefaultApi' do
   # @param app_id 
   # @param alias_label 
   # @param alias_id 
-  # @param create_subscription_request_body 
+  # @param subscription_body 
   # @param [Hash] opts the optional parameters
-  # @return [InlineResponse201]
+  # @return [SubscriptionBody]
   describe 'create_subscription test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -141,34 +142,21 @@ describe 'DefaultApi' do
   # @param alias_id 
   # @param alias_label_to_delete 
   # @param [Hash] opts the optional parameters
-  # @return [InlineResponse200]
+  # @return [UserIdentityBody]
   describe 'delete_alias test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
   end
 
-  # unit tests for delete_player
-  # Delete a user record
-  # Delete player - Required: Used to delete a single, specific Player ID record from a specific OneSignal app. 
-  # @param app_id The OneSignal App ID for your app.  Available in Keys & IDs.
-  # @param player_id The OneSignal player_id
-  # @param [Hash] opts the optional parameters
-  # @return [DeletePlayerSuccessResponse]
-  describe 'delete_player test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for delete_segments
-  # Delete Segments
-  # Delete segments (not user devices) - Required: OneSignal Paid Plan You can delete a segment under your app by calling this API. You must provide an API key in the Authorization header that has admin access on the app. The segment_id can be found in the URL of the segment when viewing it in the dashboard. 
+  # unit tests for delete_segment
+  # Delete Segment
+  # Delete a segment (not user devices) - Required: OneSignal Paid Plan You can delete a segment under your app by calling this API. You must provide an API key in the Authorization header that has admin access on the app. The segment_id can be found in the URL of the segment when viewing it in the dashboard. 
   # @param app_id The OneSignal App ID for your app.  Available in Keys & IDs.
   # @param segment_id The segment_id can be found in the URL of the segment when viewing it in the dashboard.
   # @param [Hash] opts the optional parameters
-  # @return [DeleteSegmentSuccessResponse]
-  describe 'delete_segments test' do
+  # @return [GenericSuccessBoolResponse]
+  describe 'delete_segment test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
@@ -199,20 +187,6 @@ describe 'DefaultApi' do
     end
   end
 
-  # unit tests for end_live_activity
-  # Stop Live Activity
-  # Stops a Live Activity
-  # @param app_id The OneSignal App ID for your app.  Available in Keys & IDs.
-  # @param activity_id Live Activity record ID
-  # @param subscription_id Subscription ID
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'end_live_activity test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for export_events
   # Export CSV of Events
   # Generate a compressed CSV report of all of the events data for a notification. This will return a URL immediately upon success but it may take several minutes for the CSV to become available at that URL depending on the volume of data. Only one export can be in-progress per OneSignal account at any given time.
@@ -226,52 +200,39 @@ describe 'DefaultApi' do
     end
   end
 
-  # unit tests for export_players
-  # Export CSV of Players
+  # unit tests for export_subscriptions
+  # Export CSV of Subscriptions
   # Generate a compressed CSV export of all of your current user data This method can be used to generate a compressed CSV export of all of your current user data. It is a much faster alternative than retrieving this data using the /players API endpoint. The file will be compressed using GZip. The file may take several minutes to generate depending on the number of users in your app. The URL generated will be available for 3 days and includes random v4 uuid as part of the resource name to be unguessable. 🚧 403 Error Responses          You can test if it is complete by making a GET request to the csv_file_url value. This file may take time to generate depending on how many device records are being pulled. If the file is not ready, a 403 error will be returned. Otherwise the file itself will be returned. 🚧 Requires Authentication Key Requires your OneSignal App's REST API Key, available in Keys & IDs. 🚧 Concurrent Exports Only one concurrent export is allowed per OneSignal account. Please ensure you have successfully downloaded the .csv.gz file before exporting another app. CSV File Format: - Default Columns:   | Field | Details |   | --- | --- |   | id | OneSignal Player Id |   | identifier | Push Token |   | session_count | Number of times they visited the app or site   | language | Device language code |   | timezone | Number of seconds away from UTC. Example: -28800 |   | game_version | Version of your mobile app gathered from Android Studio versionCode in your App/build.gradle and iOS uses kCFBundleVersionKey in Xcode. |   | device_os | Device Operating System Version. Example: 80 = Chrome 80, 9 = Android 9 |   | device_type | Device Operating System Type |   | device_model | Device Hardware String Code. Example: Mobile Web Subscribers will have `Linux armv` |   | ad_id | Based on the Google Advertising Id for Android, identifierForVendor for iOS. OptedOut means user turned off Advertising tracking on the device. |   | tags | Current OneSignal Data Tags on the device. |   | last_active | Date and time the user last opened the mobile app or visited the site. |   | playtime | Total amount of time in seconds the user had the mobile app open. |   | amount_spent |  Mobile only - amount spent in USD on In-App Purchases. |    | created_at | Date and time the device record was created in OneSignal. Mobile - first time they opened the app with OneSignal SDK. Web - first time the user subscribed to the site. |   | invalid_identifier | t = unsubscribed, f = subscibed |   | badge_count | Current number of badges on the device | - Extra Columns:   | Field | Details |   | --- | --- |   | external_user_id | Your User Id set on the device |   | notification_types | Notification types |   | location | Location points (Latitude and Longitude) set on the device. |   | country | Country code |   | rooted | Android device rooted or not |   | ip | IP Address of the device if being tracked. See Handling Personal Data. |   | web_auth | Web Only authorization key. |   | web_p256 | Web Only p256 key. | 
   # @param app_id The app ID that you want to export devices from
   # @param [Hash] opts the optional parameters
-  # @option opts [ExportPlayersRequestBody] :export_players_request_body 
-  # @return [ExportPlayersSuccessResponse]
-  describe 'export_players test' do
+  # @option opts [ExportSubscriptionsRequestBody] :export_subscriptions_request_body 
+  # @return [ExportSubscriptionsSuccessResponse]
+  describe 'export_subscriptions test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
   end
 
-  # unit tests for fetch_aliases
-  # Lists all Aliases for the User identified by :subscription_id.
-  # @param app_id 
-  # @param subscription_id 
-  # @param [Hash] opts the optional parameters
-  # @return [UserIdentityResponse]
-  describe 'fetch_aliases test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for fetch_user
-  # Returns the User’s properties, Aliases, and Subscriptions.
+  # unit tests for get_aliases
+  # Lists all Aliases for the User identified by (:alias_label, :alias_id).
   # @param app_id 
   # @param alias_label 
   # @param alias_id 
   # @param [Hash] opts the optional parameters
-  # @return [User]
-  describe 'fetch_user test' do
+  # @return [UserIdentityBody]
+  describe 'get_aliases test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
   end
 
-  # unit tests for fetch_user_identity
-  # Lists all Aliases for the User identified by (:alias_label, :alias_id).
+  # unit tests for get_aliases_by_subscription
+  # Lists all Aliases for the User identified by :subscription_id.
   # @param app_id 
-  # @param alias_label 
-  # @param alias_id 
+  # @param subscription_id 
   # @param [Hash] opts the optional parameters
-  # @return [InlineResponse200]
-  describe 'fetch_user_identity test' do
+  # @return [UserIdentityBody]
+  describe 'get_aliases_by_subscription test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
@@ -300,18 +261,6 @@ describe 'DefaultApi' do
     end
   end
 
-  # unit tests for get_eligible_iams
-  # Manifest of In-App Messages the Subscription is eligible to display by the SDK.
-  # @param app_id 
-  # @param subscription_id 
-  # @param [Hash] opts the optional parameters
-  # @return [InlineResponse2003]
-  describe 'get_eligible_iams test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for get_notification
   # View notification
   # View the details of a single notification and outcomes associated with it
@@ -329,7 +278,7 @@ describe 'DefaultApi' do
   # Notification History
   # -> View the devices sent a message - OneSignal Paid Plan Required This method will return all devices that were sent the given notification_id of an Email or Push Notification if used within 7 days of the date sent. After 7 days of the sending date, the message history data will be unavailable. After a successful response is received, the destination url may be polled until the file becomes available. Most exports are done in ~1-3 minutes, so setting a poll interval of 10 seconds should be adequate. For use cases that are not meant to be consumed by a script, an email will be sent to the supplied email address. 🚧 Requirements A OneSignal Paid Plan. Turn on Send History via OneSignal API in Settings -> Analytics. Cannot get data before this was turned on. Must be called within 7 days after sending the message. Messages targeting under 1000 recipients will not have \"sent\" events recorded, but will show \"clicked\" events. Requires your OneSignal App's REST API Key, available in Keys & IDs.
   # @param notification_id The \"id\" of the message found in the Notification object
-  # @param get_notification_request_body 
+  # @param get_notification_history_request_body 
   # @param [Hash] opts the optional parameters
   # @return [NotificationHistorySuccessResponse]
   describe 'get_notification_history test' do
@@ -370,69 +319,55 @@ describe 'DefaultApi' do
     end
   end
 
-  # unit tests for get_player
-  # View device
-  # View the details of an existing device in one of your OneSignal apps
-  # @param app_id Your app_id for this device
-  # @param player_id Player's OneSignal ID
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :email_auth_hash Email - Only required if you have enabled Identity Verification and device_type is email (11).
-  # @return [Player]
-  describe 'get_player test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_players
-  # View devices
-  # View the details of multiple devices in one of your OneSignal apps Unavailable for Apps Over 80,000 Users For performance reasons, this method is not available for larger apps. Larger apps should use the CSV export API endpoint, which is much more performant. 
-  # @param app_id The app ID that you want to view players from
+  # unit tests for get_segments
+  # Get Segments
+  # Returns an array of segments from an app.
+  # @param app_id The OneSignal App ID for your app.  Available in Keys & IDs.
   # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :limit How many devices to return. Max is 300. Default is 300
-  # @option opts [Integer] :offset Result offset. Default is 0. Results are sorted by id;
-  # @return [PlayerSlice]
-  describe 'get_players test' do
+  # @option opts [Integer] :offset Segments are listed in ascending order of created_at date. offset will omit that number of segments from the beginning of the list. Eg offset 5, will remove the 5 earliest created Segments.
+  # @option opts [Integer] :limit The amount of Segments in the response. Maximum 300.
+  # @return [GetSegmentsSuccessResponse]
+  describe 'get_segments test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
   end
 
-  # unit tests for identify_user_by_alias
-  # Upserts one or more Aliases to an existing User identified by (:alias_label, :alias_id).
+  # unit tests for get_user
+  # Returns the User’s properties, Aliases, and Subscriptions.
   # @param app_id 
   # @param alias_label 
   # @param alias_id 
-  # @param user_identity_request_body 
   # @param [Hash] opts the optional parameters
-  # @return [InlineResponse200]
-  describe 'identify_user_by_alias test' do
+  # @return [User]
+  describe 'get_user test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
   end
 
-  # unit tests for identify_user_by_subscription_id
-  # Upserts one or more Aliases for the User identified by :subscription_id.
+  # unit tests for transfer_subscription
+  # Transfers this Subscription to the User identified by the identity in the payload.
   # @param app_id 
   # @param subscription_id 
-  # @param user_identity_request_body 
+  # @param transfer_subscription_request_body 
   # @param [Hash] opts the optional parameters
-  # @return [UserIdentityResponse]
-  describe 'identify_user_by_subscription_id test' do
+  # @return [UserIdentityBody]
+  describe 'transfer_subscription test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
   end
 
-  # unit tests for transfer_subscription
-  # Transfers this Subscription to the User identified by the identity in the payload.
-  # @param app_id 
-  # @param subscription_id 
-  # @param transfer_subscription_request_body 
+  # unit tests for unsubscribe_email_with_token
+  # Unsubscribe with token
+  # Unsubscribe an email with a token when using your own custom email unsubscribe landing page
+  # @param app_id The OneSignal App ID for your app.  Available in Keys & IDs.
+  # @param notification_id The id of the message found in the creation notification POST response, View Notifications GET response, or URL within the Message Report.
+  # @param token The unsubscribe token that is generated via liquid syntax in {{subscription.unsubscribe_token}} when personalizing an email.
   # @param [Hash] opts the optional parameters
-  # @return [UserIdentityResponse]
-  describe 'transfer_subscription test' do
+  # @return [GenericSuccessBoolResponse]
+  describe 'unsubscribe_email_with_token test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
@@ -465,38 +400,11 @@ describe 'DefaultApi' do
     end
   end
 
-  # unit tests for update_player
-  # Edit device
-  # Update an existing device in one of your OneSignal apps
-  # @param player_id Player's OneSignal ID
-  # @param player 
-  # @param [Hash] opts the optional parameters
-  # @return [UpdatePlayerSuccessResponse]
-  describe 'update_player test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for update_player_tags
-  # Edit tags with external user id
-  # Update an existing device's tags in one of your OneSignal apps using the External User ID. Warning - Android SDK Data Synchronization Tags added through the Android SDK tagging methods may not update if using the API to change or update the same tag. For example, if you use SDK method sendTag(\"key\", \"value1\") then update the tag value to \"value2\" with this API endpoint. You will not be able to set the value back to \"value1\" through the SDK, you will need to change it to something different through the SDK to be reset. Recommendations if using this Endpoint on Android Mobile Apps: 1 - Do not use the same tag keys for SDK and API updates 2 - If you want to use the same key for both SDK and API updates, call the SDK getTags method first to update the device's tags. This is only applicable on the Android Mobile App SDKs. 📘 Deleting Tags To delete a tag, include its key and set its value to blank. Omitting a key/value will not delete it. For example, if I wanted to delete two existing tags rank and category while simultaneously adding a new tag class, the tags JSON would look like the following: \"tags\": {    \"rank\": \"\",    \"category\": \"\",    \"class\": \"my_new_value\" } 
-  # @param app_id The OneSignal App ID the user record is found under.
-  # @param external_user_id The External User ID mapped to teh device record in OneSignal.  Must be actively set on the device to be updated.
-  # @param [Hash] opts the optional parameters
-  # @option opts [UpdatePlayerTagsRequestBody] :update_player_tags_request_body 
-  # @return [UpdatePlayerTagsSuccessResponse]
-  describe 'update_player_tags test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   # unit tests for update_subscription
   # Updates an existing Subscription’s properties.
   # @param app_id 
   # @param subscription_id 
-  # @param update_subscription_request_body 
+  # @param subscription_body 
   # @param [Hash] opts the optional parameters
   # @return [nil]
   describe 'update_subscription test' do
@@ -512,7 +420,7 @@ describe 'DefaultApi' do
   # @param alias_id 
   # @param update_user_request 
   # @param [Hash] opts the optional parameters
-  # @return [InlineResponse202]
+  # @return [PropertiesBody]
   describe 'update_user test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers

data/spec/api_client_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT

data/spec/configuration_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT

data/spec/models/app_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT

data/spec/models/basic_notification_all_of_android_background_layout_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT

data/spec/models/basic_notification_all_of_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT
@@ -113,12 +113,6 @@ describe OneSignal::BasicNotificationAllOf do
     end
   end
 
-  describe 'test attribute "channel_for_external_user_ids"' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   describe 'test attribute "app_id"' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -527,6 +521,18 @@ describe OneSignal::BasicNotificationAllOf do
     end
   end
 
+  describe 'test attribute "ios_relevance_score"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "ios_interruption_level"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   describe 'test attribute "email_subject"' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers

data/spec/models/basic_notification_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT
@@ -37,13 +37,7 @@ describe OneSignal::BasicNotification do
     end
   end
 
-  describe 'test attribute "include_player_ids"' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  describe 'test attribute "include_external_user_ids"' do
+  describe 'test attribute "include_subscription_ids"' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
     end
@@ -201,12 +195,6 @@ describe OneSignal::BasicNotification do
     end
   end
 
-  describe 'test attribute "channel_for_external_user_ids"' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   describe 'test attribute "app_id"' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -615,6 +603,18 @@ describe OneSignal::BasicNotification do
     end
   end
 
+  describe 'test attribute "ios_relevance_score"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "ios_interruption_level"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
   describe 'test attribute "email_subject"' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers

data/spec/models/button_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT

data/spec/models/create_notification_success_response_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT
@@ -31,12 +31,6 @@ describe OneSignal::CreateNotificationSuccessResponse do
     end
   end
 
-  describe 'test attribute "recipients"' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
   describe 'test attribute "external_id"' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers

data/spec/models/create_segment_conflict_response_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT

data/spec/models/create_segment_success_response_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT

data/spec/models/create_user_conflict_response_errors_inner_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT

data/spec/models/create_user_conflict_response_errors_items_meta_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT

data/spec/models/create_user_conflict_response_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT

data/spec/models/delivery_data_spec.rb

@@ -3,7 +3,7 @@
 
 #A powerful way to send personalized messages at scale and build effective customer engagement strategies. Learn more at onesignal.com
 
-The version of the OpenAPI document: 1.4.1
+The version of the OpenAPI document: 5.1.0
 Contact: devrel@onesignal.com
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 6.0.0-SNAPSHOT