ProxyHubb Docs

Order credentials

Fetch CONNECT credentials after marketplace escrow activation.

After a marketplace order is funded and the linked session is active, fetch CONNECT credentials for the buyer edge.

GET /v1/orders/{id}/credentials
Authorization: Bearer <jwt>

Partners with orders:create API keys can also call this route when authenticated as that buyer.

Response

{
  "proxy_credentials": {
    "username": "...",
    "password": "...",
    "host": "proxy.proxyhubb.com",
    "port": 8090,
    "protocol": "http",
    "endpoint": "proxy.proxyhubb.com:8090"
  }
}

protocol: "http" means HTTP CONNECT to that host/port (not absolute-URI forward proxy).

Smoke test

curl -x "http://USER:[email protected]:8090" https://httpbin.org/ip

Lifecycle

  1. Create marketplace order (UI or API).
  2. Fund Solana escrow for the order.
  3. Wait until session/order is active.
  4. GET /v1/orders/:id/credentials.
  5. Use username/password at proxy.proxyhubb.com:8090.

SDK helpers

Common errors

CodeMeaningFix
401Not authenticatedJWT or eligible API key required
403Order belongs to another buyerUse the purchasing account
404Unknown order idCheck UUID
409Escrow / session not readyConfirm funding and activation, then retry
Proxy 407 with returned credsCreds rotated or session endedRe-fetch credentials

For short-lived rotating access without escrow, prefer session intents.