Any yes-or-no fact your backend can look up about one of its own users. Common actions are a first purchase or deposit, a completed signup or onboarding, a level or rank reached in a game, and an active subscription. You define up to twenty actions per registered app, and each one is available in the builder as an App Verified custom giveaway task.
App Verified Tasks
Verify Custom Giveaway TasksWith Your Own App
When your own backend can confirm an action, your Discord giveaway can require it. Register your app once, and every completion comes back as a signed answer from your service, checked the moment the entrant returns.
An App Verified task is a Discord giveaway task your own app confirms. During the task, the entrant is redirected to your service. Your service signs them in, checks the action against your own records, and sends the browser back with a cryptographically signed yes or no. A yes completes the task on the spot.
The actions are yours to define. You register your app in the dashboard, name up to twenty actions it can confirm, and each one is available in the giveaway builder from then on. A first purchase. A completed onboarding. A level reached in your game. If your backend can look it up, a giveaway can require it.
How an App Verified Task Works
From registering your app to a confirmed entry
- 1
Register your app once
In your dashboard's Developer section you register the app that will answer for your tasks: a name, the Verify URL entrants are sent to, and a signing mode. Signing works over a shared secret shown once at creation, or over an Ed25519 key pair if your stack prefers public-key signatures. You can rotate the shared secret or deactivate the app at any time.
Then you name the actions the app can confirm, up to twenty per app, each with a label your team will recognize in the builder. The Verified Actions developer guide documents the whole exchange for whoever builds the endpoint, with a copy-paste reference implementation. It also includes a skill file you can paste into an AI coding agent to have the endpoint written for you.
- 2
Attach an action to a giveaway
In the giveaway builder, add a custom task, pick the App Verified method, and select the app and the action. From there it behaves like any task in the giveaway: it carries its own entry value, sits next to the catalog tasks on the entry page, and shows entrants the name, icon, and instructions you gave it.
- 3
Your app answers a signed request
When an entrant starts the task, ScopliDrop redirects them to your Verify URL with a signed request token naming the action to check and a participant id that matches the answer back to the task. Your service signs the user in with its own login, checks the action against its own records, and redirects the browser back with a signed yes or no.
Every request is minted for one answer. The response has to be signed with the registered key, match the participant it was minted for, and arrive within its validity window, or it is rejected. A replayed or tampered answer never touches an entry.
- 4
The task completes itself
A yes completes the task the moment the entrant lands back on the entry page, with nothing for you to review. A no shows them a clear retry message naming your app, so they can finish the action and try again. From there the giveaway carries the entry like any other, all the way to the draw.
For your developers, the dashboard keeps a log of the app's recent handshakes with a precise outcome code on each, including any failure code your app attached to a no. A misconfigured signature or an expired answer is visible at a glance instead of being a silent failure.
What Hosts Build With It
Three setups where your own records decide who qualifies
Entries only your customers can earn
Point an action at an event your backend already records: a first deposit, a completed order, an active subscription. The giveaway becomes a promotion where entering means becoming a customer.
A giveaway that rewards reaching level ten
Game backends know exactly what each player has done. An action on a level, a rank, or a completed quest turns your Discord giveaway into a play incentive, with the game itself confirming who qualified.
Signups that finish onboarding
A signup task can be gamed with a throwaway account. Rewarding a finished onboarding, a verified profile, or a first project instead sends the entries to users who reached the moment your product starts mattering to them.
And whatever your backend can answer. To check whether an action idea fits before your team wires it up, ask us in the ScopliDrop community Discord.
The Certainty of a Native Check, for Actions Only You Can See
The case for a signed answer
Tasks that happen outside Discord usually leave a gap between doing the action and proving it. A submitted handle still needs a review pass, and a timed link visit confirms attention, not completion. App Verified closes that gap, because the system of record for the action is the one giving the answer.
The answer cannot be forged. ScopliDrop signs the request that reaches your app, and your app signs the response that comes back. Each handshake is accepted exactly once, so a replayed or tampered answer is rejected outright.
That turns a giveaway into a rewards channel for your product itself. Deposits, orders, activations, milestones. The prize goes only to people your own records confirmed, and the win condition is exactly the behavior you wanted to drive.
Combine It With
Where the confirmed entries come from and where they go next
App Verified Questions
What your app can verify, what the integration takes, and what keeps it honest
Related Features
Custom Tasks
Name it, pick an icon, collect the data you need, or have your own app verify completion.
Explore Custom TasksTask Verification
How every task gets verified, from instant Discord checks to video codes.
Explore Task VerificationIf Your Backend Can Confirm It, Reward It
Register your app once, define the actions, and every giveaway you run can require them. Signed both ways, accepted exactly once, confirmed instantly.