Overview

The NEX Developer Platform gives you stable webhook URLs, request filtering, API keys, and purchase-triggered content delivery — without running your own ingress layer.

Typical flow: store or game server → NEX webhook proxy → filters → auto-delivery → Discord or your backend.

Create an account

Sign up at developer.nexrbx.com/login
Verify your email from the inbox message
Open the dashboard

Create your first webhook

From Webhooks → Create Webhook, set a name and target URL (for example a Discord webhook). NEX assigns a public proxy URL:

https://nexrbx.com/api/webhooks/p/YOUR_PUBLIC_ID

POST JSON to that URL from Roblox (HttpService) or any backend. See Webhook proxies for forwarding behaviour and analytics.

Recommended project layout

Roblox experience

ServerScriptService/
- NexWebhook.server.lua
ReplicatedStorage/
- NexConfig.lua

NexConfig.lua — keep secrets server-side

return {
  WebhookUrl = "https://nexrbx.com/api/webhooks/p/YOUR_PUBLIC_ID",
  ApiKey = "nex_dev_…", -- optional, for filtered webhooks
}

Minimal webhook POST

local HttpService = game:GetService("HttpService")
local Config = require(game.ReplicatedStorage.NexConfig)

local function notifyEvent(payload)
  return HttpService:PostAsync(
    Config.WebhookUrl,
    HttpService:JSONEncode(payload),
    Enum.HttpContentType.ApplicationJson
  )
end

notifyEvent({
  source = "roblox",
  event = "player_joined",
  userId = "123456789",
})

Enable HTTP requests in Roblox game settings before testing.

Next steps

Webhook proxies — forwarding, embeds, replay
Request filters — restrict who can call your proxy
API keys — generate and verify secrets
Script licenses — HWID binding, leak alerts, update channel
Auto-delivery — keys and grants on purchase events