Verify Players
How EnderDash player verification works, from challenge creation through the hosted form to the decision your plugin receives.
Player verification lets a plugin gate an action behind a short hosted form. EnderDash issues a one-time link, the player opens it and submits the form, and your plugin gets back an accept or reject decision along with risk and location signals.
Use it to confirm a human is behind an account, collect a piece of onboarding info, or add an hCaptcha check before granting access.
How a verification flows
- A plugin on your server, through the EnderDash agent, opens a verification challenge for a player. It sets the title, an optional description, the form fields, and how long the link stays valid.
- EnderDash returns a one-time link on
https://verify.enderdash.com. Your plugin hands that link to the player, usually as a clickable chat message. - The player opens the link, fills the form, completes hCaptcha, and submits.
- EnderDash checks the submission, gathers risk and location signals, and sends a decision back to your plugin.
Agents only
Only an authenticated EnderDash agent can create a challenge. Players cannot start one, and a link works for a single challenge.
What players see
The hosted page renders the title, description, and fields you defined, plus a countdown to expiry. The player completes hCaptcha before the submit button works, and the submit endpoint rejects requests that do not pass validation. A challenge accepts one successful submission.
Field types
A challenge can include 1 to 8 fields and mix any of these types. Each field has an id, a label, an optional description, and a required flag.
| Type | Extra options | Notes |
|---|---|---|
text | placeholder, minLength, maxLength | Single-line text, up to 500 characters. |
number | placeholder, min, max | Numeric input. |
select | placeholder, options | A dropdown of 1 to 20 options. |
checkbox | none | A single box, useful for agreements. |
Challenge lifetime
You choose the lifetime when you create the challenge. The default is 5 minutes and the maximum is 15 minutes. After it expires the link stops working and the player needs a new one.
Risk and location signals
When a player submits, EnderDash attaches signals to the decision so your plugin can react to suspicious traffic:
- hCaptcha result
- whether the connection looks like a proxy, hosting provider, or mobile network
- coarse location from the submitter's IP, such as country, region, city, and network operator
These travel with the accept or reject decision. Your plugin decides what to do with them.
Review results
Recent verifications show up in the dashboard's Verification panel with the time, status, plugin id, decision code, latency, and proxy, hosting, or mobile risk flags. The underlying history also records challenge ids, correlation ids, decision messages, hCaptcha status, and risk details for audit and debugging workflows.
Related
- Plugin Integrations for what plugins can drive through the agent.
- Java API for the agent-side surface.
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on