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
- Create marketplace order (UI or API).
- Fund Solana escrow for the order.
- Wait until session/order is active.
GET /v1/orders/:id/credentials.- Use username/password at
proxy.proxyhubb.com:8090.
SDK helpers
- Python:
get_order_credentials→as_requests_proxy_from_credentials - Node:
getOrderCredentials→proxyUrlFromCredentials - Go:
GetOrderCredentials→ProxyURLFromCredentials
Common errors
| Code | Meaning | Fix |
|---|---|---|
401 | Not authenticated | JWT or eligible API key required |
403 | Order belongs to another buyer | Use the purchasing account |
404 | Unknown order id | Check UUID |
409 | Escrow / session not ready | Confirm funding and activation, then retry |
Proxy 407 with returned creds | Creds rotated or session ended | Re-fetch credentials |
For short-lived rotating access without escrow, prefer session intents.