# proxy_id

Route an image render through your own HTTP proxy.

## How it works

The `proxy_id` parameter tells the API to route **all outbound traffic for this render** through one of the proxies you’ve configured in the dashboard at [https://htmlcsstoimage.com/dashboard/proxies](https://htmlcsstoimage.com/dashboard/proxies).

This is commonly used to:

*   Allowlist a single egress IP on a private origin.
*   Get past bot detection on the target site.
*   Make requests appear from a specific region.

For setup instructions, supported fields, and bypass-host behavior, see the full [HTTP Proxies guide](/guides/advanced/proxies/).

## Value

| Type | Description |
| --- | --- |
| `String` | The `id` of a proxy you’ve created in the dashboard. |

## Example usage

### JSON request

```json
{
  "url": "https://internal.example.com",
  "proxy_id": "your-proxy-id"
}
```

### cURL

```bash
curl -X POST https://hcti.io/v1/image \
  -u 'UserID:APIKey' \
  -H 'Content-Type: application/json' \
  -d '{
        "url": "https://internal.example.com",
        "proxy_id": "your-proxy-id"
      }'
```

### HTML/CSS render

```json
{
  "html": "<img src='https://internal.example.com/logo.png' />",
  "proxy_id": "your-proxy-id"
}
```

Plan availability

Proxies are available on the **10,000 images/month plan or higher**.

Disabling a proxy

You can disable a proxy in the dashboard at any time. Existing images keep working — only new renders that pass that `proxy_id` will be rejected.

## Manage proxy configurations

Create or inspect proxies through the [Management API](/management-api/proxies/) or [MCP tools](/integrations/mcp/tools/#proxies). Using an existing proxy for image creation requires image permissions; editing its configuration requires proxy management permissions.

## Need help?

Talk to a human. Email [support@htmlcsstoimage.com](mailto:support@htmlcsstoimage.com) and we’ll help you get started.