Try the block / use / audit loop. No signup. No real keys.
We pre-wired a fake HiBob integration. Issue a scoped demo RelayKey, watch how RelayKey allows and blocks calls against the scope you set, and see the audit trail. Everything below runs in your browser.
Issue a disposable RelayKey
Pretend we've already protected your real HiBob key. Pick the methods and path glob you want this disposable RelayKey to allow, then issue it.
In the real product, only the methods + paths you select pass through. Everything else returns 403 from the proxy before the upstream call is made.
Globs welcome - e.g. /v1/people/*.
Make a call
One token, two calls. The first matches your scope and goes through. The second is out of scope and the proxy blocks it before it touches the upstream.
curl https://proxy.relaykey.ai/conn_demo/v1/people \
-H "Authorization: Bearer rk_proxy_demo_xxxxxxxxxxxx"{
"employees": [
{ "id": "e_401", "name": "Ana Vega", "title": "Recruiter" },
{ "id": "e_402", "name": "Ben Liu", "title": "Engineer" }
]
}See it in the audit log
Both calls land in the audit log - the allowed one with a 200, the blocked one with a 403 and a denial reason. Filter by RelayKey, key holder, or status. Export when you need it.
This is what RelayKey looks like with real keys.
Connect your first integration in under three minutes. Free forever for one protected key.