Read-Only Hudu API Access — Today, Not Eventually

Hudu has an open feature request for read-only API keys. While you wait, GuardProxy gives you read-only access right now.

Start free trial Try the demo

The Problem with Hudu API Keys

Hudu API keys inherit the creating user's permissions with no way to restrict to read-only. If you want to connect an external dashboard, reporting tool, or AI agent, you must hand over a key that can create, modify, and delete assets.

The Hudu community has requested read-only API keys on their feedback board. It's a known gap. But feature requests take time, and your security needs don't wait.

Every day your full-access Hudu key is in a third-party tool or AI agent, you're one bug or hallucination away from data loss.

The feature has been requested. While you wait, GuardProxy gives you read-only access today.

How GuardProxy Fixes It

Wrap your Hudu API key in a GuardProxy proxy endpoint. The key stays the same — the access doesn't.

GuardProxy intercepts write methods before they reach Hudu. Reads pass through, writes get a 403.

Your existing integrations keep working. Just change the base URL to point at GuardProxy.

60-second setup. Cancel anytime if Hudu ships native read-only keys.

your terminal

# Before — direct to Hudu (full access)

$curl https://your-hudu-url.com/api/v1/assets \

# After — through GuardProxy (read-only)

$curl https://cust_acme.guardproxy.dev/hudu/v2/organizations \

-H "Authorization: Token YOUR_KEY"

200 OKdata returned, writes blocked

Lock down your Hudu API key in 60 seconds.

Free for 14 days. No credit card. Cancel anytime.

Start your free trial