Pools

Within Cloudflare, pools represent your endpoints and how they are organized. As such, a pool can be a group of several endpoints, or you could also have only one endpoint (an origin server, for example) per pool.

If you are familiar with DNS terminology, think of a pool as a “record set,” except Cloudflare only returns addresses that are considered healthy. You can attach health monitors to individual pools for customized monitoring.

For more details about how endpoints and pools become unhealthy, refer to Endpoint and pool health.

​​ Properties

For an up-to-date list of pool properties, refer to Pool properties Open API docs link in our API documentation.

​​ Create pools

For step-by-step guidance, refer to Create pools.

​​ Per-endpoint Host header override

When your application needs specialized routing (CNAME setup or custom hosts like Heroku), change the Host header used in health monitor requests. For more details, refer to Override HTTP Host headers.

​​ API commands

The Cloudflare API supports the following commands for pools. Examples are given for user-level endpoint but apply to the account-level endpoint as well.