Document the purpose of api.cloudflareclient.com

[jamie-sandbox]

Existing documentation URL(s)

https://developers.cloudflare.com/cloudflare-one/connections/connect-devices/warp/deployment/firewall/#client-orchestration-api

What changes are you suggesting?

The endpoint api.cloudflareclient.com is not mentioned anywhere in the WARP zero trust documentation, even though the WARP client seems to connect to this on a regular basis.

This has been observed both in full WARP and DoH-only modes.

Connections to api.cloudflareclient.com follow the system proxy settings, as these connections were observed when reviewing the corporate proxy server logs for a laptop using the WARP zero trust client.

As far as I can tell, api.cloudflareclient.com resolves to generic Cloudflare addresses rather than dedicated WARP ranges.

What is the purpose of api.cloudflareclient.com? Is it supposed to follow the system proxy settings? Do we need to whitelist it?

Additional information

No response

[deadlypants1973]

Hi @jamie-sandbox, api.cloudflareclient.com is used for consumer WARP (https://developers.cloudflare.com/warp-client/). It is not related to Zero Trust WARP and therefore won't be documented here.

[jamie-sandbox]

@deadlypants1973 Thanks for confirming. I think it'd still be useful to document this, as seeing it in our logs has still caused a lot of confusion (hence why I logged this issue).

It'd be useful for other people facing the same problem to have a short sentence in the documentation for it.

[DikozImpact]

Hi @jamie-sandbox, api.cloudflareclient.com is used for consumer WARP (https://developers.cloudflare.com/warp-client/). It is not related to Zero Trust WARP and therefore won't be documented here.

Then why is it not mentioned here (https://developers.cloudflare.com/warp-client/) ? And in general, there is no mention of it in the whole cloudflare documentation.