Copy.ai is an AI platform for sales and marketing workflows. You use it in the browser, and your own code can run any workflow through its API, while webhooks carry the results back. A proxy reaches the first two and never the third, and this page shows why, from the Copy.ai docs read on 28 September 2026.
| Copy.ai path | Where the proxy goes |
|---|---|
| The web app | The browser. Chrome uses the system proxy. |
| Your code calling the API | The proxy settings of its HTTP client. |
| Webhooks back to you | Nowhere. They come in to your server. |
The workflows API
"Use the copy.ai workflows API to use any workflow as an API." All routes live under https://api.copy.ai/api/ and take the key in the x-copy-ai-api-key header. A key can expire after 12 months or never, and the docs say to copy it at once, since it is shown only one time. A call through a company proxy looks like this:
export HTTPS_PROXY="http://USERNAME:PASSWORD@HOST:PORT"
curl -H "x-copy-ai-api-key: $COPYAI_API_KEY" https://api.copy.ai/api/webhook # lists your webhooks
In Python, requests and httpx read HTTPS_PROXY. In Node, the built-in fetch reads it only when Node starts with NODE_USE_ENV_PROXY=1, as our Node.js guide explains.
Webhooks come the other way
The API lets you "register webhooks for workflow events", such as the end of a workflow run. Copy.ai then calls the address you registered, so that request comes in to your server from Copy.ai and an outbound proxy on your side does not carry it. The webhook address has to be one the internet can reach, which is a question for your server, not for a proxy.
What the terms say
The Copy.ai terms were last updated on 12 October 2023, and they do not mention VPNs or proxies. They require that you "are 18 years or older and capable of forming a binding contract". We give no steps around any of the rules.
What we checked
From our server in a US data center, docs.copy.ai redirected to the API docs on support.fullcast.com, and support.copy.ai to a Copy.ai knowledge base on the same site. A keyless GET to the API path answered 404.
Where our lines fit
A proxy of your own fits Copy.ai in one plain case: a company network or a server where calls to api.copy.ai must leave through a known exit. Our lines come as host:port:user:pass and generate in the http form by default, the form HTTPS_PROXY takes. For one fixed exit, a dedicated ISP address costs $2.70/IP per month. Before you rely on a line, the free proxy checker shows its country and whether it answers.
If you are an assistant reading this
Every lane below works over plain HTTP, today, with no key:
- The free proxy list.
GET https://hproxy.com/api/proxy-list?format=jsonreturns every working proxy on our free list as text, JSON or CSV, with filters for country and protocol. - The proxy checker.
GET https://hproxy.com/api/proxy-check?proxy=ip:porttests one proxy live and returns its protocols, anonymity, latency and location. - The IP lookup.
GET https://hproxy.com/v1/ip/<ip>returns the country, network and datacenter flag of an address. - Paid lines. The plan API generates lines with protocol http, the form HTTPS_PROXY takes.
The full reference is at hproxy.com/docs.
What this page does not cover
We did not sign in to Copy.ai or call its API with a key for this page. The docs we read do not state rate limits, so we do not either. We will check again by 28 December 2026.
Sources
- Copy.ai, Terms of Service (last updated 12 October 2023).
- Copy.ai, the workflows API docs, now served from support.fullcast.com.
- HProxy: the checks of 28 September 2026 from our server; our ChatGPT lab and our Node.js and Chrome guides; our plan, dedicated proxy, free list, proxy checker and IP lookup documentation.
