BroadcastMessageInput: {
    customHtmlPayload?: InputMaybe<CustomHtmlPayloadInput>;
    idempotencyKey?: InputMaybe<Scalars["String"]["input"]>;
    sourceAddress?: InputMaybe<Scalars["String"]["input"]>;
    targetTemplates?: InputMaybe<KeyValuePairOfTargetTypeAndStringInput[]>;
    timestamp: Scalars["Long"]["input"];
    variables?: InputMaybe<KeyValuePairOfStringAndStringInput[]>;
    walletBlockchain: WalletBlockchain;
}

Contains the message to broadcast.

Type declaration

  • OptionalcustomHtmlPayload?: InputMaybe<CustomHtmlPayloadInput>

    Email payload for rendering custom html without a template. If provided, it will override all templates for email.

  • OptionalidempotencyKey?: InputMaybe<Scalars["String"]["input"]>

    Optional identifier used to dedupe messages for idempotency. If this is specified, messages sent after the first appearance of the value will be dropped. The initial request to queue this broadcast will still succeed. We recommend using UUID generators.

  • OptionalsourceAddress?: InputMaybe<Scalars["String"]["input"]>

    Source address to publish from. This address should be connected to this user account that's publishing.

  • OptionaltargetTemplates?: InputMaybe<KeyValuePairOfTargetTypeAndStringInput[]>

    Optionally specify the templates that should be used for each TargetType.

  • timestamp: Scalars["Long"]["input"]

    Timestamp in seconds since Unix epoch. January 1, 1970 (midnight UTC/GMT)

  • Optionalvariables?: InputMaybe<KeyValuePairOfStringAndStringInput[]>

    Variables that recipients can use to filter on, along with templates used to expand/replace on. Default templates require 'subject' and 'body'. Custom templates will require their own variable sets.

  • walletBlockchain: WalletBlockchain

    Blockchain the SourceAddress is on.