Stake KIngs

Create quest instance for quest as administrator

skbet

Auto-generated from Express routes with starter metadata for core modules.

StakeKings Core API

Attach a Coinflow bank account payment method for the current user.

Attach a Coinflow payment method to the current user.

Attach a Coinflow card payment method for the current user.

Attach a Coinflow IBAN payment method for the current user.

Resolve the Coinflow withdrawer details for the current user.

Look up or create the Coinflow withdrawer record for the current user.

Initialize or refresh Coinflow KYC state for the current user.

Create or refresh Coinflow KYC for the current user.

Fetch a Coinflow session key for the current user.

Create a Coinbase Commerce charge for a structured deposit request.

Launch a provider-specific deposit flow that relies on the configured deposit structure.

Create a Luxon payment session for a structured deposit request.

Prepare a Skrill deposit session for the current user.

Prepare a Skrill deposit session for the current authenticated user.

Dispatch a deposit request to the configured cashier provider.

Initiate a deposit flow using the selected cashier provider.

Dispatch a withdrawal request to the configured cashier provider.

Initiate a withdrawal flow using the selected cashier provider.

Returns the authenticated user identity, current first package, and derived Bootcamp state without creating activity events.

Verify ownership of a package marked data.special=first and record post_first_package activity.

Confirm a newly-created first package and record onboarding activity.

Create a new staking package using the shared legacy package flow.

Update an existing staking package using the shared legacy package flow.

Returns marketplace-live packages owned by the authenticated user for the Package Dashboard table.

Returns the authenticated user’s finalized or hidden packages until result processing closes them.

Delete the authenticated player’s closed, unstaked first package only after verifying the newly-created replacement package.

Remove a closed, unstaked first package after its replacement exists.

Attach or replace the poster image for an existing staking package.

Set or replace the poster image for an existing package.

Returns a simple capability/health payload for the reward controller domain.

List calls default to limit=40 and return pagination.total. They support filtering by quest, user, result/state, and unique id. Quest instances are the per-user execution/history layer, not the quest definition itself.

Creates a started per-user quest runtime record. It cannot create completed or other terminal states.

Admin-only fetch, metadata update, or delete operations for one quest instance.

Updates identity or cached progress metadata. Generic administration cannot transition lifecycle state.

From any history row, supersedes the user's current execution without creating a replacement, removes quest-local progress, and revokes grants sourced from it. Repeated cancellation is idempotent.

Completes the current active instance through the canonical lifecycle and grants rewards. This bypasses task fulfillment only; lifecycle locking and reward idempotency remain enforced.

Returns the selected instance together with the backend-evaluated quest, prerequisites, tasks, progress, evidence, and admin overrides for its user.

Supersedes the user's current history for this quest, revokes completion grants, and starts a fresh instance with a new progress baseline. Shared activity evidence is retained for other quests.

Adds an audited completion override for one task node on an active quest instance. The original evidence remains visible.

Returns runtime-evaluated quests for the current user. Supports `available`, `all`, `active`, and `completed` modes. Completion analytics come from the backend; wording should be built on the frontend.

Returns one active row per granted badge key for the current user. If the badge catalogue entry changed later, the response still falls back to the historical reward snapshot stored on the grant row.

Returns active, unrevoked, unexpired privilege keys for the current user.

List calls default to limit=40 and support filtering by key, type, origin, and free-text search.

Creates one quest blueprint. Prerequisites and tasks are stored as grouped condition trees inside `data`, and rewards are stored as plain JSON entries in `data.rewards`.

Returns the authenticated quest display/builder contract: condition/task types, reward types, reward rules, field metadata, examples, and searchable catalogue-backed editor inputs.

Loads the current user's quest context once, reconciles automatic completion once, evaluates every quest once, and returns available, all, active, and completed lists atomically.

Admin-only fetch, update, or delete operations for one JSON-backed quest blueprint.

Updates the quest blueprint in place. Already completed users should still be treated as completed by runtime logic; changing quest requirements is for future evaluation, not historical revocation.

Completes an eligible explicit-completion quest for the authenticated user after backend task validation.

Admin-only creation of a started arbitrary-user instance. Terminal state creation requires audited repair.

Uses the quest leaderboard reward definitions to calculate winners and grants. By default this requires `quest.data.endsAt` to be in the past. Use `dryRun` to inspect the settlement report without creating grants, or `force` to bypass the end-date guard for maintenance/debugging.

Starts an eligible explicit-completion quest for the authenticated user. Identity and result are derived by the server.

Returns one session-bound current-user read model containing active badges, active privileges, and the all-quests runtime view.

Authenticate by username/email and password. Returns JWT token when successful.

Returns full session payload for current authenticated user.

regular

Debit & Credit

Apple Pay

Google Pay

Zelle

PayPal

Crypto

Skrill & Neteller

Luxon

Echeck

Bobby Firestone

quick

Withdrawals are processed in the order they are received. Processing time may vary depending on the number of requests in the queue.

We process all quick cashout requests on our end within 4 hours during business hours. Once processed, the funds are sent to your bank, and the final delivery time depends on your bank’s processing speed. Most users receive their funds the same day, but exact timing may vary by bank.

Credit & Debit

Withdrawal requests are processed on a first-come, first-served basis. Please note that even after your request is confirmed, the processing may take 3–5 business days to complete.

 We process all quick cashout requests on our end within 4 hours during business hours. Once processed, the funds are sent to your bank, and the final delivery time depends on your bank’s processing speed. Most users receive their funds the same day, but exact timing may vary by bank and generally takes 3-5 working days.

StakeKings Hall of Fame