Struct SubscriptionNotificationTarget 

pub struct SubscriptionNotificationTarget {
    pub include_subscription_ids: Option<Vec<String>>,
    pub include_email_tokens: Option<Vec<String>>,
    pub include_phone_numbers: Option<Vec<String>>,
    pub include_ios_tokens: Option<Vec<String>>,
    pub include_wp_wns_uris: Option<Vec<String>>,
    pub include_amazon_reg_ids: Option<Vec<String>>,
    pub include_chrome_reg_ids: Option<Vec<String>>,
    pub include_chrome_web_reg_ids: Option<Vec<String>>,
    pub include_android_reg_ids: Option<Vec<String>>,
    pub include_aliases: Option<HashMap<String, Vec<String>>>,
    pub target_channel: Option<TargetChannelType>,
}

Fields

include_subscription_ids: Option<Vec<String>>

Specific subscription ids to send your notification to. Does not require API Auth Key. Not compatible with any other targeting parameters. Example: ["1dd608f2-c6a1-11e3-851d-000c2940e62c"] Limit of 2,000 entries per REST API call

include_email_tokens: Option<Vec<String>>

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

include_phone_numbers: Option<Vec<String>>

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

include_ios_tokens: Option<Vec<String>>

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

include_wp_wns_uris: Option<Vec<String>>

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

include_amazon_reg_ids: Option<Vec<String>>

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

include_chrome_reg_ids: Option<Vec<String>>

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

include_chrome_web_reg_ids: Option<Vec<String>>

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

include_android_reg_ids: Option<Vec<String>>

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

include_aliases: Option<HashMap<String, Vec<String>>>

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: { "external_id": ["exId1", "extId2"], "internal_label": ["id1", "id2"] } 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.

target_channel: Option<TargetChannelType>

Implementations

impl SubscriptionNotificationTarget

pub fn new() -> SubscriptionNotificationTarget

Trait Implementations

impl Clone for SubscriptionNotificationTarget

fn clone(&self) -> SubscriptionNotificationTarget

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for SubscriptionNotificationTarget

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for SubscriptionNotificationTarget

fn default() -> SubscriptionNotificationTarget

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for SubscriptionNotificationTarget

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl PartialEq for SubscriptionNotificationTarget

fn eq(&self, other: &SubscriptionNotificationTarget) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl Serialize for SubscriptionNotificationTarget

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for SubscriptionNotificationTarget