Dare to Be Different.
Eight vendors.
One API + dashboard.
Unified RPS sits in front of Yealink YMCS, Polycom ZTP, Fanvil, GDMS, Snom, Gigaset, Auerswald, and Panasonic redirect services. One login, one device list, one audit trail — instead of eight portals with eight auth schemes. Multi-tenant from day one; BYO upstream credentials per vendor (or use Giant's). Bulk-import your existing estate in one click.
POST /api/v1/devices
{ "manufacturer": "yealink", "mac": "805ec0123456" }
{ "manufacturer": "polycom", "mac": "0004f2123456" }
{ "manufacturer": "fanvil", "mac": "0c383e123456" }
{ "manufacturer": "grandstream", "mac": "000b82123456" }
{ "manufacturer": "snom", "mac": "00041325abcd" }
{ "manufacturer": "gigaset", "mac": "7c2f80123456" }
...Vendor portals collapsed into a single dashboard.
Search any MAC across the whole estate. Audit who did what across every manufacturer. Same API call regardless of which vendor's brick is on the wall.
Built by people who got tired of eight portals.
Every reseller / MSP shipping multi-vendor SIP estates ends up writing the same script eight times. Unified RPS is what we wanted to exist.
Eight vendors at launch, more on request.
The vendors below are wired in today. If you've got a manufacturer that isn't here and you've got volume, ring us — we add new vendors as resellers commit to using them.
| Vendor | Upstream service | Devices commonly seen |
|---|---|---|
| Yealink | YMCS / RPS | T-series, W-series DECT, MeetingBoard |
| Polycom | ZTP | VVX, Trio, Edge series |
| Fanvil | XML-RPC redirect | X-series, V-series video |
| Grandstream | GDMS | GXP, GRP, GXV video |
| Snom | Snom Redirect | D-series, M-series DECT |
| Gigaset | Gigaset RPS | Maxwell, N-series DECT |
| Auerswald | Auerswald RPS | COMfortel D-series |
| Panasonic | Panasonic Cloud | KX-HDV / KX-TGP series |
Every vendor above is fronted by the same POST /api/v1/devices call — only the manufacturer field changes. Your automation doesn't care which brick is on the wall.
Everything you'd build yourself — already built.
The boring infrastructure (multi-tenant isolation, scoped API keys, audit log, webhooks, bulk import) that always seems to be missing on internal tools — done. Focus on what actually moves your business.
One API, every vendor
POST /api/v1/devices with {manufacturer, mac, redirect_url}. Same shape for Yealink, Polycom, Fanvil, Grandstream, Snom, Gigaset, Auerswald, Panasonic. JSON, form-encoded, or plain GET URL — pick what your automation tool likes.
Single dashboard
Device search, activity graphs, per-vendor stats, audit log — all in one place. Stop tab-hopping between YMCS / ZTP / GDMS / the other five.
Multi-tenant from day one
Each tenant is isolated by design — your devices, your audit log, your API keys. Reseller-of-resellers supported: nest tenants for sub-channel partners.
BYO upstream credentials
Bring your own Yealink RPS account, your own GDMS login, your own Polycom ZTP partner ID — per vendor, per tenant. Or use Giant's shared credentials where you'd rather not manage them yourself.
Scoped API keys
Read-only keys for monitoring + dashboards. Tenant-scoped keys for your automation. Admin-scoped keys for managing customers under your umbrella. Roll keys instantly, scope-down on the fly.
Bulk import
Already running hundreds of phones on YMCS or GDMS? One-click import: we pull the existing device list from each upstream and mirror it into your tenant. Reconciles automatically thereafter.
Activity + audit
Per-tenant activity graph (provisioning bursts, failures, redirect updates). Audit log searchable by user / vendor / MAC / time-window. Export as CSV / JSON for your SOC2 trail.
Standard SaaS plumbing
Email notifications, forgot-password flow, user invites, key rotation, role-based access, organisation switching. The boring stuff that always seems missing on internal tools — done.
JSON, form, or paste-into-Zapier. Same endpoint.
Same payload shape regardless of how you send it. Use the form variant for low-code platforms. Use the GET URL for Zapier / Make / no-code automations that just want a webhook target. JSON for everything else.
curl -X POST https://rps.giant.net.uk/api/v1/devices \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"manufacturer": "yealink",
"mac": "805ec0123456",
"redirect_url": "https://prov.your-platform.com/{mac}.cfg"
}'curl -X POST https://rps.giant.net.uk/api/v1/devices \
-H "Authorization: Bearer YOUR_API_KEY" \
-d "manufacturer=polycom" \
-d "mac=0004f2123456" \
-d "redirect_url=https://prov.your-platform.com/{mac}.cfg"https://rps.giant.net.uk/api/v1/devices?
manufacturer=fanvil&
mac=0c383e123456&
redirect_url=https://prov.your-platform.com/{mac}.cfg&
api_key=YOUR_API_KEYBuilt for resellers + MSPs shipping mixed estates.
If every customer site has the cheapest handset that was available the day it was bought, you're already living the problem this solves.
Wholesale ITSPs
Provisioning customer phones across multiple makes? You're already running a script per vendor or worse, manual portals. One API replaces all of that.
MSPs shipping mixed estates
Your customers' offices have whatever was cheapest at the time — Yealink in this branch, Polycom in that one, a Fanvil somebody bought on a whim. One dashboard for all of it.
PBX / hosted-VoIP vendors
If you sell hosted PBX / SIP trunks and your customers BYO handsets, Unified RPS is the layer that auto-redirects each device to your platform — regardless of brand — on first power-on.
Sandbox to production tenant. Bulk import day after that.
Sandbox + read-only API key within 24h of signup. Production tenant + first vendor wired typically inside 3 working days. If you're consolidating an existing multi-vendor estate, the bulk import wizard handles the migration.
Real questions, honest answers.
Dare to Be Different.
One API. Every vendor.
Stop tab-hopping between eight RPS portals. Sandbox tenant in your inbox within 24h of signup; production live inside three working days.