Create loyalty rules using API

Which profile fields must be filled. Keys: profile_picture, name, location, nft_portfolio, about, email, twitter, discord, telegram, evm, solana, sui, ton, imx. If omitted, a default set is checked (bio, avatar, X, Discord, email).

Points for the referred user.

Points for the referrer.

Currency for referrer reward.

Require referred users to achieve points.

Required points when achievePoints is true.

Require complete profile.

Require Twitter connection.

Require Discord connection.

Require email connection.

Points for each check-in.

Enable streak tracking for consecutive check-ins.

Optional array of streak milestones and rewards.

Apply a higher reward to verified (blue-check) accounts.

Multiplier applied when enableVerifiedMultiplier is true (e.g. 1.5).

Require users to also join specific Discord servers.

Servers (and optionally channels/roles) users must join.

Which wallet type the user must connect (e.g. evm, solana).

URL of the X post to engage with.

Twitter user ID of the post author.

Require liking the post.

Require reposting.

Require commenting.

Twitter OAuth credentials (top-level field).

Text that must be included in the tweet.

Require users to submit post link (default: true).

Require post to include media.

X account to follow.

Twitter user ID of the account.

OAuth credentials for Twitter (top-level field).

Text that must appear in the user's bio, display name, or comment.

(drip_x_text_in_comment) Only reward posts that pass quality/sentiment checks.

(drip_x_text_in_comment) Minimum follower count to qualify.

Tiered rewards by the user's follower count.

Tiered rewards by post view/impression count.

Only reward posts that pass quality/sentiment checks.

Minimum follower count to qualify.

Optional top-level flag to track progress. mediaUrl (top-level) can supply a media reference.

Twitter user ID of the account whose posts are monitored for reposts.

Account that posted the tweet.

Twitter user ID.

OAuth credentials (top-level field).

Twitter user ID of the account whose posts are monitored for comments.

Hashtag to search for in recent posts.

Twitter user ID of the project account whose like qualifies the user.

OAuth credentials for Twitter (top-level field).

Multiply the reward by the tweet's impression count.

Servers and roles to verify. Each item uses id and roles.

Servers the user must join. Only the server id is required for this type.

Server id and the channels whose messages count. Each channel can specify text to match and emojis reactions.

Optional tiered rewards based on message count.

Server id plus the roles to grant. roles is required for this type.

ID of the Telegram channel the user must join.

ID of the Telegram channel whose messages count.

Optional tiered rewards based on message count.

TikTok profile URL to follow (e.g. https://www.tiktok.com/@username). Despite the field name, this holds the TikTok URL.

Text to check in post.

Require post link submission.

IMPRESSIONS_COUNT or ELIGIBLE_POST.

Text or hashtag the post must include.

Only reward posts that pass quality checks.

Minimum follower count to qualify.

Instagram profile URL to follow (e.g. https://www.instagram.com/username). Despite the field name, this holds the Instagram URL.

YouTube channel ID the user must subscribe to.

Optional Google API integration ID (top-level field) used for verification.

YouTube video ID the user must comment on.

Optional Google API integration ID (top-level field) used for verification.

ID of the Reddit post users must comment on.

Full URL of the Reddit post.

Steam application ID the user must wishlist.

Shopify store domain (top-level field).

Shopify admin API access token (top-level field).

Range-based rewards by purchase amount.

Collections to track (top-level field).

Only reward users who have never sold the token.

Optional tiered rewards.

Collections to track (top-level field).

Only reward existing users.

Only reward users who never sold the token.

Optional tiered rewards.

Collections to track (top-level field).

Only reward existing users.

Reward only one token ownership per contract.

Tiered rewards by number of tokens held.

Filter by specific sale currency.

Currency address when hasSaleCurrency is true.

Optional tiered rewards.

Reward based on USD value held rather than token count.

Apply a multiplier per holding tier instead of fixed points.

Tiered rewards by amount held.

any, relay, or lifi.

Relay referrer ID when provider is relay.

Source-token filter: { mode: "any" | "specific", chain, tokens, trackAmount }.

Destination-token filter: { mode: "any" | "specific", chain, tokens, trackAmount }.

Require cross-chain swaps.

Token symbols to track (e.g. ["TRUMP", "SPY"]).

Optional tiered rewards by holding amount. Falls back to top-level amount if omitted.

Contract address to monitor (top-level field).

Event signature to track.

everyEvent or specify conditions.

Event parameter filters.

Address parameter name in event.

ID of the Stratus function to run (top-level field).

Optional Stratus subscription ID (top-level field).

Optionally route rewards to the dApp owner. When true, rewardType must be points and network is required.

Chain for liquidity pools.

Protocol identifier (e.g., "uniswap-v2/eth-usdc").

Array of liquidity pool addresses (max 20, same network/protocol).

fixed or custom.

USD value per day (when calculationType is fixed).

Custom calculation formula (when calculationType is custom).

Repository URL. Must match https://github.com/<owner>/<repo>.

Repository URL. Must match https://github.com/<owner>/<repo>.

Target branch to count merged PRs against. Defaults to main if omitted.

Optional tiered rewards by number of merged PRs.

Placeholder text for the input field.

Minimum character length required.

Type: code, csv, or generate.

Single shared code (when promoCodeType is code).

CSV URL with unique codes (when promoCodeType is csv).

Number of codes to generate (when promoCodeType is generate).

Only allow new users (last 6 hours) to redeem.

URL the user clicks.

Delay (1–600 s) before the reward is granted.

Platform shown for the link (e.g. X, Discord, or Custom).

Label on the action button.

Question text.

Answer options with isCorrect flag. Exactly one choice must be correct.

Poll question text.

Answer choices.

Allow users to vote multiple times.

Snapshot proposal(s) to track. One proposal per rule.

Partner site URL. Must match the partner auth domain.

Label on the action button.

Base points amount.

Track completion progress (top-level field).

Range-based rewards with custom amounts.

Multiply reward by number of actions.

Description of what the external rule tracks.

CSV URL with wallet addresses and point amounts (top-level field).

Track processing progress.

Tiered rewards by rank/threshold for the chosen metric.

Data window for the metric: daily, weekly, or monthly. Leave empty for all-time.

Optional filter limiting to dApps deployed within this window.

Routes rewards to the dApp owner. Immutable after creation.

Blockchain network for the rule (required when isDappRule is true).

Array of reward ranges.

Minimum value for this range.

Maximum value (use Number.MAX_SAFE_INTEGER for unlimited).

Points awarded for this range.

Optional badge for this range.

Maximum points users can earn in the interval.

Interval period: daily, weekly, monthly.

manual (user must claim) or auto (auto-rewarded).

For multipliers/badges: permanent (never removed) or dynamic (removed if requirements not met).

When airdrop becomes effective.

When airdrop ends.