Read the visitor's address from a PROXY protocol header on the cluster's websites (ports 80 and 443), for a cluster behind another load balancer. Connections without one still work.
API key access: full.
apiKeyAuthorizationBearer <pyo_…>An API key from the dashboard's API keys page: Authorization: Bearer pyo_…. Keys can expire, and an expired one gets a 401.
application/jsonRead the visitor's address from a PROXY protocol header on the cluster's websites (ports 80 and 443), for a cluster behind another load balancer. Connections without one still work.
API key access: full.
op*"setClusterWebProxyProtocol""setClusterWebProxyProtocol"clusterId*stringon*booleanDone. Always ok: true, and some operations add more, such as a new API key or a join command. A warning comes with a change that went through but won't fully take effect yet, such as more replicas than the servers have room for.
application/jsoncurl -X POST 'https://your-pyo.example.com/api/v1/ops' \
-H 'Content-Type: application/json' \
-d '{
"clusterId": "cl_8kq2x7ad",
"on": true,
"op": "setClusterWebProxyProtocol"
}'{}