Pay users to try your app.
We verify it automatically.

What is this, really?

Think of it like this: a tasker on RegoLoop sees your campaign — "Sign up on Tunaa and get ₦4,500". They tap "Accept". RegoLoop gives them a unique link with a secret code baked in, like:

https://yourapp.com/signup?rgt=a3f9c2b1e4d7f6c8...

When they sign up through that link, your app reads the rgt code and sends it to RegoLoop in the background. RegoLoop sees it, confirms the tasker completed the action, and releases their payout — all in seconds. You don't have to check screenshots. You don't have to approve anything. It just works.

The 4 steps

Here's everything that happens, end to end.

// Add this to your signup page — runs when the page loads
const rgt = new URLSearchParams(window.location.search).get("rgt")
if (rgt) {
  sessionStorage.setItem("rgt", rgt)
}

// Then when the user submits the signup form, include it:
const formData = {
  email:    "...",
  password: "...",
  rgt:      sessionStorage.getItem("rgt") || "",  // ← include this
}

// Node.js / Express example
// Install: npm install axios

const axios = require("axios")

app.post("/webhook/user-registered", async (req, res) => {
  const { userId, rgt } = req.body

  // Only fire if user arrived via a RegoLoop referral link
  if (!rgt) return res.json({ ok: true })

  try {
    await axios.post(
      "https://api.regoloop.com/api/v1/sdk/v1/campaigns/events/",
      {
        feature:      "signup",      // must match your campaign setting
        device_token: rgt,           // the token from the ?rgt= URL param
        platform:     "web",
        event_time:   new Date().toISOString(),
      },
      {
        headers: {
          Authorization: process.env.REGOLOOP_LIVE_KEY,
          "Content-Type": "application/json",
        },
        timeout: 10000,
      }
    )
  } catch (err) {
    // Never let this break your registration flow
    console.error("RegoLoop SDK error:", err.message)
  }

  res.json({ ok: true })
})

Test it before going live

Use your test key instead of your live key while you're building. Test events don't trigger real payouts, so you can fire as many as you need to confirm everything is wired correctly.

Here's how to fire a test event manually from your terminal (no code needed):

curl -X POST https://api.regoloop.com/api/v1/sdk/v1/campaigns/events/ \
  -H "Authorization: RT-test-yourbrand-xxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "feature":      "signup",
    "device_token": "paste-the-device-token-from-the-taskers-submission",
    "platform":     "web",
    "event_time":   "2026-04-27T10:00:00Z"
  }'

Where does the device token come from?

When a tasker accepts your campaign, RegoLoop generates a unique token just for them. This token is embedded in their referral link as ?rgt=. You don't need to generate or store it — it comes from the URL.

For testing, accept your own campaign from a second account (a test tasker account). On the submissions page, open that submission — you'll see the full referral link and can copy the token directly.

Environment variables you need

Add these to your server's .env file:

# Your RegoLoop API keys (get these from the SDK page on your campaign)
REGOLOOP_LIVE_KEY=RT-live-yourbrand-xxxxxxxxxxxxxxxx
REGOLOOP_TEST_KEY=RT-test-yourbrand-xxxxxxxxxxxxxxxx

# The base URL (don't change this)
REGOLOOP_API_URL=https://api.regoloop.com/api/v1

Common questions