---
title: "Put your app behind Cloudflare, or take it back out"
method: POST
path: "/client/domains/{id}/proxied"
tags: ["Apps"]
---

# Put your app behind Cloudflare, or take it back out

`POST /client/domains/{id}/proxied`

## Request

- Base URL: `https://api.roar-ai.com`
- URL: `https://api.roar-ai.com/client/domains/{id}/proxied`
- Auth: HTTP bearer

Serve your app’s Roar address through Cloudflare instead of resolving straight to the server. Body: `{ "proxied": true }` to turn it on, `false` to turn it off.

It filters bad traffic and is faster for visitors far from where your app is hosted — and slower for visitors in that same region, because their requests take a detour. Colombo pays the most for this; Singapore and Bangalore pay very little.

Only your free `*.roarai.app` address can be proxied. **A domain you own cannot**, and neither can a Roar address that one of your own domains points at — turning it on there would send your visitors to an edge that has never heard of your name. Put your own domain behind your own Cloudflare instead, which gives you your own rules. `id` is a DOMAIN id, from `GET /client/services/{id}/domains`. Requires `apps:deploy`.

## Path parameters

- `id` string, uuid, required

## Response `200`

The updated domain

## Other responses

- `400`: A domain you own, one your own domain points at, or one with no DNS target yet
- `403`: Key lacks apps:deploy
- `404`: No such domain

---

[API](https://skmtc.dev/roar-ai/apis/roar-ai-api.md) · [All operations](https://skmtc.dev/roar-ai/apis/roar-ai-api/llms.txt) · [OpenAPI document](https://skmtc.dev/roar-ai/apis/roar-ai-api/revisions/37e4d0d5a7fe?raw)