FlareKey Docs

Appearance

Integrations ​

Integrations gate a free, short-lived license key behind one or more Linkvertise / LootLabs / work.ink links, chained into a checkpoint sequence called a reward. Visitors complete the checkpoints to unlock the key. The ad revenue from those services goes to your own publisher account on that service, not FlareKey. Every mechanic on the pages in this section (link format, anti-bypass API, postback API, key-validation API) is taken from each provider's own official documentation, not guessed. This feature is split across two dashboard pages: Integrations (linking accounts) and Rewards (building the actual gate).

  • Integration: credentials for one external account (Linkvertise Publisher ID, LootLabs API token, or a work.ink link). Created once on /dashboard/integrations, reused across rewards.
  • Reward: the shareable gate link, built on /dashboard/provider from your linked integrations - name, key validity, and the checkpoint sequence all live here.
  • Checkpoint: one step in a reward, built from an integration. A reward chains any number of checkpoints, and the same integration can be added twice (e.g. two Linkvertise checkpoints back to back).
  • By default checkpoints run strictly in order - a visitor cannot skip ahead or replay a finished one. Turning on User Select Mode instead shows every checkpoint as an alternative and lets the visitor pick any ONE to unlock the key.
  • The key is only generated after the reward's checkpoint requirement is met.
  • Reward settings: Expiry on first use (the key's countdown starts on its first real verify instead of at issuance), One-time use keys (blocks HWID resets once bound), HWID Limit (max devices per key), Salt (a random per-reward string with a generate button), Theme (a cosmetic accent color for the public checkpoint/reveal pages).
  • Streak System: turns the one-time reveal page into a standing keys page instead - visitors can hold multiple keys (up to a limit you set), renew an expired key for free, and claim a time bonus on a cooldown.

Providers ​

ProviderWhat it is
LinkvertiseReal API confirmed from Linkvertise's own FullScript API and Anti-Bypassing documentation.
Work.inkDifferent model from every other provider here: work.ink has no link-creation API, so you create the link by hand on work.ink's own dashboard first.
LootLabsReal Content Locker API confirmed from LootLabs' own docs.
ShrinkearnReal shortener API confirmed live against shrinkearn.com.
Cuty.ioReal shortener API confirmed live against cuty.io.
ShrtFlyReal shortener API confirmed against ShrtFly's own docs page.
SafelinkuReal REST API confirmed against safelinku.com's own docs.
Exe.io / Clk.sh / Short-jambo / GPLinksThese four run on the same underlying shortener platform, confirmed by their nearly identical Developer API shape - the setup steps are the same for all four.
Ouo.ioRequest shape confirmed from Ouo.io's own Quick Link tools page.

Linkvertise ​

Real API confirmed from Linkvertise's own FullScript API and Anti-Bypassing documentation.

  1. Sign in at linkvertise.com and open your Creator dashboard.
  2. Go to the "FullScript API" section. Your Publisher ID is shown there - a numeric ID, e.g. 123456.
  3. In FlareKey, open Integrations, click + New Integration, choose Linkvertise, paste the Publisher ID, then Create.
  4. Optional, for stronger verification: in the Linkvertise dashboard go to Settings, enable "Anti-Bypassing", and copy the token shown into the connection's Anti-Bypass token field.
  5. Add the integration as a checkpoint on a reward from the Rewards page. Keep the Linkvertise Anti-Bypass token configured so the provider's own return proof remains authoritative.
  • Known limitation: Linkvertise's Anti-Bypass API sits behind Cloudflare's bot protection and has returned a block page to server-to-server requests during testing. The native Anti-Bypass token is still required for Linkvertise completion proof; if the provider API is unavailable, the checkpoint fails closed rather than silently trusting a return URL.

Work.ink ​

Different model from every other provider here: work.ink has no link-creation API, so you create the link by hand on work.ink's own dashboard first.

  1. In FlareKey, open Integrations, click + New Integration, choose Work.ink, give it a label only (leave the link field blank), then Create.
  2. Open the new connection's card and copy its Return URL. It looks like this: https://flarekey.xyz/api/lockers/workink-return/<connectionId>?token={TOKEN}
  3. In your work.ink dashboard, create a Key System / Custom Redirect link and set its redirect URL to the exact Return URL you copied, keeping {TOKEN} in place literally - work.ink substitutes the real token into that placeholder itself.
  4. Copy the work.ink link work.ink gives you back (e.g. https://work.ink/abc/xyz), paste it into the "Your work.ink link" field on the connection's card, then Save link.
  5. Add the integration as a checkpoint on a reward from the Rewards page. Completion is verified for real against work.ink's own token API.
  • work.ink has no publisher-level API key at all - the token embedded in the Return URL is the only credential involved, and work.ink makes it single-use automatically.

LootLabs ​

Real Content Locker API confirmed from LootLabs' own docs.

  1. Sign in at lootlabs.gg and open your panel.
  2. Go to API and generate/copy your API token.
  3. In FlareKey, open Integrations, click + New Integration, choose LootLabs, paste the API token, then Create. LootLabs has no separate publisher ID - the token is the only credential its API uses.
  4. Add the integration as a checkpoint on a reward. FlareKey calls LootLabs' real Content Locker API on every visit, using the Ad tasks (1-5) setting you chose when linking the integration - the more tasks, the more the visitor has to complete and the more you earn.
  5. Optional, for stronger verification: in the LootLabs panel go to Advanced and set your postback URL to https://flarekey.xyz/api/lockers/webhook/lootlabs/<connectionId&gt; (shown on the connection's card). LootLabs will notify FlareKey the moment a visitor completes it.
  • Completion is verified server-side against LootLabs' Content Locker API on every visit, so a visitor cannot skip the tasks by editing the return URL.
  • The Ad tasks (1-5) setting controls how many steps the visitor completes and, correspondingly, how much you earn per unlock.

Shrinkearn ​

Real shortener API confirmed live against shrinkearn.com.

  1. Sign in at shrinkearn.com and go to Tools -> Developers API.
  2. Copy your API token shown there.
  3. In FlareKey, open Integrations, click + New Integration, choose Shrinkearn, paste the API token, then Create. Shrinkearn has no separate publisher ID - the token is the only credential its API uses.
  4. Add the integration as a checkpoint on a reward - no further setup needed.
  • Shrinkearn is a link shortener, so each checkpoint is one shortened hop the visitor passes through before the key is unlocked.
  • The API token is the only credential; there is no separate publisher ID to configure.

Cuty.io ​

Real shortener API confirmed live against cuty.io.

  1. Sign in at cuty.io and go to Tools -> Developer API.
  2. Copy your API token shown there - the "Legacy" Developer API. Cuty also offers a newer Full API / Quick API, not used here.
  3. In FlareKey, open Integrations, click + New Integration, choose Cuty.io, paste the API token, then Create.
  4. Add the integration as a checkpoint on a reward - no further setup needed.
  • Use the Legacy Developer API token, not the newer Full/Quick API. FlareKey's cuty.io adapter is built against the legacy shape.
  • Each checkpoint is one cuty.io hop; chain more checkpoints for more revenue per unlock.

ShrtFly ​

Real shortener API confirmed against ShrtFly's own docs page.

  1. Sign in at shrtfly.com and go to your Developer API tools section.
  2. Copy your API token shown there.
  3. In FlareKey, open Integrations, click + New Integration, choose ShrtFly, paste the API token, then Create.
  4. Add the integration as a checkpoint on a reward - no further setup needed.
  • ShrtFly's response shape is confirmed different from Shrinkearn/Cuty despite an identical request format - FlareKey already accounts for this, nothing extra to configure on your end.

Safelinku ​

Real REST API confirmed against safelinku.com's own docs.

  1. Sign in at safelinku.com and go to Tools -> Api -> Rest API.
  2. Copy your API token shown there.
  3. In FlareKey, open Integrations, click + New Integration, choose Safelinku, paste the API token, then Create.
  4. Add the integration as a checkpoint on a reward - no further setup needed.
  • Safelinku uses a standard REST API token; paste it once and every checkpoint built from this integration reuses it.
  • Completion is confirmed on the return trip, so the key only issues after the visitor actually passes through the link.

These four run on the same underlying shortener platform, confirmed by their nearly identical Developer API shape - the setup steps are the same for all four.

  1. Sign in at the provider's site (exe.io, clk.sh, short-jambo.com, or gplinks.com) and go to Tools -> Developer(s) API.
  2. Copy your API token shown there.
  3. In FlareKey, open Integrations, click + New Integration, choose the matching provider, paste the API token, then Create.
  4. Add the integration as a checkpoint on a reward - no further setup needed. Confirmed live for all four including GPLinks.
  • All four providers share the same request shape, so a token from any one of them is configured identically.
  • Pick the provider whose payout and audience fit your region; the checkpoint behavior is the same across all four.

Ouo.io ​

Request shape confirmed from Ouo.io's own Quick Link tools page.

  1. Sign in at ouo.io and go to Tools -> Quick Link.
  2. Copy the key shown in the example URL there - the part right after /api/, before the ?. For example, in http://ouo.io/api/14dVpIgS?s=..., the key is 14dVpIgS.
  3. In FlareKey, open Integrations, click + New Integration, choose Ouo.io, paste that key, then Create.
  4. Add the integration as a checkpoint on a reward.
  • Ouo.io's API has returned a Cloudflare challenge page to requests from this server's environment during testing - the same issue Linkvertise's Anti-Bypass API has. If a checkpoint using Ouo.io fails, this is the first place to check.

FlareKey documentation

2026 FlareKey