PUT /accounts/{account_id}/moq/relays/{relay_id}
Updates a relay's name and/or configuration. The relay ID goes in
the URL path — PUT /accounts/{account_id}/moq/relays/{relay_id} —
not the request body; there is no collection-level update endpoint.
This is also the only way to set a relay's config (config cannot be
set at create time). Partial updates: omitted fields are preserved;
config sub-objects replace as whole objects when present.
Servers
- https://api.cloudflare.com/client/v4
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
relay_id |
String | Yes |
Relay unique identifier (32 hex characters). |
account_id |
String | Yes |
Cloudflare account identifier. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
name |
String | No | |
config |
Object | No | |
config.upstreams |
Object | No |
Upstreams are external MOQT server publishers that a relay falls back to when it has no local publisher for a requested namespace/track. |
config.upstreams.upstreams[] |
Array | No |
Ordered list of upstream MOQT server publishers. Each entry is an object (not a bare string) so per-upstream configuration can be added in the future without another breaking change. |
config.upstreams.upstreams[].url |
String | Yes |
Upstream MOQT server publisher URL. Must be an absolute URL with a host and a scheme the relay can dial: moqt:// (raw QUIC) or https:// (WebTransport). Validated on update (PUT); rejected with 21013. |
config.upstreams.enabled |
Boolean | No |
Default value: false |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.