[25.2] Clean up API doc xrefs to new Bump URLs (#1311)

kbatuigas · web-flow · commit 1652ae6d0870 · 2025-08-20T15:20:24.000+01:00
diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
@@ -255,9 +255,9 @@
 *** link:https://github.com/redpanda-data/helm-charts/releases[Redpanda Helm Chart^]
 *** link:https://github.com/redpanda-data/redpanda-operator/releases[Redpanda Operator^]
 ** xref:reference:api-reference.adoc[]
-*** xref:api:ROOT:pandaproxy-rest.adoc[]
-*** xref:api:ROOT:pandaproxy-schema-registry.adoc[]
-*** xref:api:ROOT:admin-api.adoc[]
+*** link:/api/doc/http-proxy/[HTTP Proxy API]
+*** link:/api/doc/schema-registry/[Schema Registry API]
+*** link:/api/doc/admin/[Admin API]
 ** xref:reference:data-transforms/sdks.adoc[]
 *** xref:reference:data-transforms/golang-sdk.adoc[Golang]
 *** xref:reference:data-transforms/rust-sdk.adoc[Rust]
diff --git a/modules/develop/pages/produce-data/configure-producers.adoc b/modules/develop/pages/produce-data/configure-producers.adoc
@@ -249,7 +249,7 @@ Each time a broker receives a message with a skewed timestamp that is outside a
 === Disable broker timestamp retention
 
 // For cloud there must be restrictions on Admin API usage. We should find out and omit any references to unsupported endpoints.
-While not advised for typical use, Redpanda lets you override the use of broker timestamps for retention policy with the Admin API. Use the xref:api:ROOT:admin-api.adoc#Licenses-and-Features/operation/put_feature[`activate feature`] API to disable the `broker_time_based_retention` property.
+While not advised for typical use, Redpanda lets you override the use of broker timestamps for retention policy with the Admin API. Use the link:/api/doc/admin/operation/operation-put_feature[`activate feature`] API to disable the `broker_time_based_retention` property.
 
 If you disable this feature, make sure to specify your desired timestamp policy. This is stored in the xref:reference:cluster-properties.adoc#log_message_timestamp_type[`log_message_timestamp_type`] cluster property. The timestamp policy defaults to `CreateTime` (client timestamp set by producer) but may be updated to `LogAppendTime` (server timestamp set by Redpanda).
 endif::[]
diff --git a/modules/manage/pages/cluster-maintenance/partition-recovery.adoc b/modules/manage/pages/cluster-maintenance/partition-recovery.adoc
@@ -13,7 +13,7 @@ NOTE: If you want to instead force recover all partitions in bulk from a set of
 
 The following examples assume that partition 0 in topic `test` is unavailable and its replicas cannot form a majority to elect a leader.
 
-. Call the xref:api:ROOT:admin-api.adoc#tag/Partitions/operation/get_topic_partitions[`/partitions/kafka/<topic>`] endpoint to determine the current broker and shard assignments of the partition replicas.
+. Call the link:/api/doc/admin/operation/operation-get_topic_partitions[`/partitions/kafka/<topic>`] endpoint to determine the current broker and shard assignments of the partition replicas.
 +
 [,bash]
 ----
@@ -77,7 +77,7 @@ curl -X POST http://localhost:9644/v1/debug/partitions/kafka/test/0/force_replic
 +
 The request body includes the broker ID and the CPU core (shard ID) for the replica on broker 1, to hydrate the new replicas assigned to brokers 4 and 5 on cores 1 and 0 respectively. 
 +
-If there are `n` CPU cores on the machine, the value of `core` can be within the range `[0, n-1]`. You may use a random value within the range, or the least loaded shard. See the xref:reference:public-metrics-reference.adoc[public metrics reference] for metrics regarding CPU usage, and xref:api:ROOT:admin-api.adoc#tag/Partitions/operation/force_update_partition_replicas[Redpanda Admin API] for additional detail.
+If there are `n` CPU cores on the machine, the value of `core` can be within the range `[0, n-1]`. You may use a random value within the range, or the least loaded shard. See the xref:reference:public-metrics-reference.adoc[public metrics reference] for metrics regarding CPU usage, and link:/api/doc/admin/operation/operation-force_update_partition_replicas[Redpanda Admin API] for additional detail.
 
 include::shared:partial$suggested-reading.adoc[]
 
diff --git a/modules/manage/pages/iceberg/redpanda-topics-iceberg-snowflake-catalog.adoc b/modules/manage/pages/iceberg/redpanda-topics-iceberg-snowflake-catalog.adoc
@@ -142,7 +142,7 @@ Use any of the following to set `redpanda.iceberg.mode`:
 +
 * `rpk`. See the following examples to run `rpk topic` commands.
 * The Cloud UI. Navigate to *Topics* to create a new topic and specify `redpanda.iceberg.mode` in *Additional Configuration*, or edit an existing topic under the topic's *Configuration* tab.
-* The Data Plane API to xref:api:ROOT:cloud-dataplane-api.adoc#post-/v1/topics[create a new topic] or xref:api:ROOT:cloud-dataplane-api.adoc#patch-/v1/topics/-topic_name-/configurations[update a property for an existing topic]. Specify the key-value pair for `redpanda.iceberg.mode` in the request body.
+* The Data Plane API to link:/api/doc/cloud-dataplane/operation/operation-topicservice_createtopic[create a new topic] or link:/api/doc/cloud-dataplane/operation/operation-topicservice_updatetopicconfigurations[update a property for an existing topic]. Specify the key-value pair for `redpanda.iceberg.mode` in the request body.
 endif::[]
 +
 The following examples show how to use `rpk` to create a new topic or alter the configuration for an existing topic, setting the Iceberg mode to `key_value`.  
diff --git a/modules/manage/pages/kubernetes/networking/k-connect-to-redpanda.adoc b/modules/manage/pages/kubernetes/networking/k-connect-to-redpanda.adoc
@@ -235,7 +235,7 @@ kubectl exec <pod-name> --namespace <namespace> -- curl https://<pod-name>.redpa
   --key /etc/tls/certs/redpanda-client/tls.key
 ----
 
-For all available endpoints, see xref:api:ROOT:pandaproxy-rest.adoc[].
+For all available endpoints, see the link:/api/doc/http-proxy/[HTTP Proxy API reference].
 
 === Connect to internal Schema Registry
 
@@ -366,7 +366,7 @@ kubectl exec <pod-name> --namespace <namespace> -- \
 
 NOTE: If the broker's certificate is signed by a well-known, trusted CA, and your system's CA trust store is reliable, you may omit `--cacert`.
 
-For all available endpoints, see xref:api:ROOT:admin-api.adoc[].
+For all available endpoints, see the link:/api/doc/admin/[Admin API reference].
 
 --
 ====
@@ -577,7 +577,7 @@ curl https://<pod-name>.redpanda.<namespace>.svc.cluster.local:30082/topics \
   --key /etc/tls/certs/external/tls.key
 ----
 
-For all available endpoints, see xref:api:ROOT:pandaproxy-rest.adoc[].
+For all available endpoints, see the link:/api/doc/http-proxy/[HTTP Proxy API reference].
 
 === Connect to external Schema Registry
 
@@ -684,7 +684,7 @@ curl https://<pod-name>.redpanda.<namespace>.svc.cluster.local:31644/v1/node_con
   --key /etc/tls/certs/external/tls.key
 ----
 
-For all available endpoints, see xref:api:ROOT:admin-api.adoc[].
+For all available endpoints, see the link:/api/doc/admin/[Admin API reference].
 
 == Next steps
 
diff --git a/modules/manage/pages/schema-reg/schema-reg-authorization.adoc b/modules/manage/pages/schema-reg/schema-reg-authorization.adoc
@@ -370,7 +370,7 @@ The `Invalid license: not present` error indicates that the user is trying to cr
 ifndef::env-cloud[]
 * xref:manage:schema-reg/schema-reg-overview.adoc[]
 * xref:reference:rpk/rpk-registry/rpk-registry.adoc[rpk registry]
-* xref:api:ROOT:pandaproxy-schema-registry.adoc[Schema Registry API]
+* link:/api/doc/schema-registry/[Schema Registry API]
 * xref:reference:node-configuration-sample.adoc[] (search for `schema_registry`)
 * xref:manage:monitoring.adoc#service-level-queries[Monitor Schema Registry service-level metrics]
 * xref:deploy:redpanda/manual/node-property-configuration.adoc[Configure broker properties for Schema Registry]
@@ -379,7 +379,7 @@ endif::[]
 ifdef::env-cloud[]
 * xref:manage:schema-reg/schema-reg-overview.adoc[]
 * xref:reference:rpk/rpk-registry/rpk-registry.adoc[rpk registry]
-* xref:api:ROOT:pandaproxy-schema-registry.adoc[Schema Registry API]
+* link:/api/doc/schema-registry/[Schema Registry API]
 * xref:manage:monitoring.adoc#service-level-queries[Monitor Schema Registry service-level metrics]
 * xref:manage:schema-reg/record-deserialization.adoc#schema-registry[Deserialization]
 
diff --git a/modules/manage/pages/schema-reg/schema-reg-overview.adoc b/modules/manage/pages/schema-reg/schema-reg-overview.adoc
@@ -144,7 +144,7 @@ All CRUD operations are supported for the JSON Schema (`json-schema`), and Redpa
 
 === Limitations
 
-Schemas are held in subjects. Subjects have a compatibility configuration associated with them, either directly specified by a user, or inherited by the default. See `PUT /config` and `PUT/config/\{subject}` in the xref:api:ROOT:pandaproxy-schema-registry.adoc[Schema Registry API].
+Schemas are held in subjects. Subjects have a compatibility configuration associated with them, either directly specified by a user, or inherited by the default. See `PUT /config` and `PUT/config/\{subject}` in the link:/api/doc/schema-registry/[Schema Registry API].
 
 If you have inserted a second schema into a subject where the compatibility level is anything but `NONE`, then any JSON Schema containing the following items are rejected:
 
@@ -165,15 +165,15 @@ endif::[]
 
 == Suggested reading
 ifndef::env-cloud[]
-* xref:api:ROOT:pandaproxy-schema-registry.adoc[Schema Registry API]
+* link:/api/doc/schema-registry/[Schema Registry API]
 * xref:console:config/deserialization.adoc[Deserialization]
 * xref:reference:node-configuration-sample.adoc[] (search for `schema_registry`)
 * xref:manage:monitoring.adoc#service-level-queries[Monitor Schema Registry service-level metrics]
 * xref:deploy:redpanda/manual/node-property-configuration.adoc[Configure broker properties for Schema Registry]
 
 endif::[]
 ifdef::env-cloud[]
-* xref:api:ROOT:pandaproxy-schema-registry.adoc[Schema Registry API]
+* link:/api/doc/schema-registry/[Schema Registry API]
 * xref:manage:schema-reg/record-deserialization.adoc[Deserialization]
 * xref:manage:monitoring.adoc#service-level-queries[Monitor Schema Registry service-level metrics]
 
diff --git a/modules/manage/partials/authentication.adoc b/modules/manage/partials/authentication.adoc
@@ -1354,7 +1354,7 @@ Each of the HTTP APIs implements its own permission model with different levels
 
 The Admin API primarily requires superuser privileges, with a few exceptions for read-only status endpoints.
 
-For a complete list of all Admin API endpoints, see see xref:api:ROOT:admin-api.adoc[].
+For a complete list of all Admin API endpoints, see the link:/api/doc/admin/[Admin API reference].
 
 ==== Schema Registry API permissions
 
@@ -1539,7 +1539,7 @@ curl https://localhost:8082/topics --cacert <path-to-ca>/ca.crt -u <username>:<p
 NOTE: If the broker's certificate is signed by a well-known, trusted CA, and you're confident about the integrity of your system's CA trust store, you don't need the `--cacert` flag.
 endif::[]
 
-For all available endpoints, see xref:api:ROOT:pandaproxy-rest.adoc[].
+For all available endpoints, see the link:/api/doc/http-proxy/[HTTP Proxy API reference].
 
 ===== Connect to the Schema Registry API
 
@@ -1738,7 +1738,7 @@ curl https://localhost:8082/topics --cacert <path-to-ca>/ca.crt -H "Authorizatio
 NOTE: If the broker's certificate is signed by a well-known, trusted CA, and you're confident about the integrity of your system's CA trust store, you don't need the `--cacert` flag.
 endif::[]
 
-For all available endpoints, see xref:api:ROOT:pandaproxy-rest.adoc[].
+For all available endpoints, see the link:/api/doc/http-proxy/[HTTP Proxy API reference].
 
 ===== Connect to the Schema Registry API
 
diff --git a/modules/manage/partials/iceberg/about-iceberg-topics.adoc b/modules/manage/partials/iceberg/about-iceberg-topics.adoc
@@ -34,7 +34,7 @@ To enable Iceberg for Redpanda topics, you must have the following:
 ifdef::env-cloud[]
 * A running xref:get-started:cluster-types/byoc/index.adoc[BYOC] cluster on Redpanda version 25.1 or later. The Iceberg integration is supported only for BYOC, and the cluster properties to configure Iceberg are available with v25.1.
 * rpk: See xref:get-started:rpk-install.adoc[].
-* Familiarity with the Redpanda Cloud API. You must xref:redpanda-cloud:manage:api/cloud-api-authentication.adoc[authenticate] to the Cloud API and use the Control Plane API to update your cluster configuration.
+* Familiarity with the Redpanda Cloud API. You must link:/api/doc/cloud-controlplane/authentication[authenticate] to the Cloud API and use the Control Plane API to update your cluster configuration.
 endif::[]
 
 ifndef::env-cloud[]
@@ -195,7 +195,7 @@ The Redpanda cluster ID is also used as the container name (ID) and the storage
 
 For Azure clusters, you must add the public IP addresses or ranges from the REST catalog service, or other clients requiring access to the Iceberg data, to your cluster's allow list. Alternatively, add subnet IDs to the allow list if the requests originate from the same Azure region.
 
-For example, to add subnet IDs to the allow list through the Control Plane API xref:api:ROOT:cloud-controlplane-api.adoc#patch-/v1/clusters/-cluster.id-[`PATCH /v1/clusters/<cluster-id>`] endpoint, run:
+For example, to add subnet IDs to the allow list through the Control Plane API link:/api/doc/cloud-controlplane/operation/operation-clusterservice_updatecluster[`PATCH /v1/clusters/<cluster-id>`] endpoint, run:
 
 [,bash]
 ----
diff --git a/modules/manage/partials/iceberg/use-iceberg-catalogs.adoc b/modules/manage/partials/iceberg/use-iceberg-catalogs.adoc
@@ -149,7 +149,7 @@ Cloud API::
 +
 --
 . Authenticate and make a `GET /v1/clusters/\{id}` request to xref:manage:api/cloud-dataplane-api.adoc#get-data-plane-api-url[retrieve the Data Plane API URL] for your cluster.
-. Make a request to xref:api:ROOT:cloud-dataplane-api.adoc#post-/v1/secrets[`POST /v1/secrets`]. You must use a Base64-encoded secret.
+. Make a request to link:/api/doc/cloud-dataplane/operation/operation-secretservice_createsecret[`POST /v1/secrets`]. You must use a Base64-encoded secret.
 +
 [,bash]
 ----
@@ -196,7 +196,7 @@ rpk cluster config set iceberg_rest_catalog_client_secret ${secrets.<secret-name
 Cloud API::
 +
 --
-Make a request to the xref:api:ROOT:cloud-controlplane-api.adoc#patch-/v1/clusters/-cluster.id-[`PATCH /v1/clusters/<cluster-id>`] endpoint of the Control Plane API.
+Make a request to the link:/api/doc/cloud-controlplane/operation/operation-clusterservice_updatecluster[`PATCH /v1/clusters/<cluster-id>`] endpoint of the Control Plane API.
 
 [,bash]
 ----
diff --git a/modules/manage/partials/mountable-topics.adoc b/modules/manage/partials/mountable-topics.adoc
@@ -394,7 +394,7 @@ endif::[]
 You cannot cancel mount and unmount operations in the following <<monitor-progress,states>>:
 
 ifndef::env-cloud[]
-- `planned` (but you may still xref:api:ROOT:admin-api.adoc#delete-/v1/migrations/-id-[delete] a planned mount or unmount)
+- `planned` (but you may still link:/api/doc/admin/operation/operation-delete_migration[delete] a planned mount or unmount)
 endif::[]
 ifdef::env-cloud[]
 - `planned` (but you may still delete a planned mount or unmount)
diff --git a/modules/manage/partials/recovery-mode.adoc b/modules/manage/partials/recovery-mode.adoc
@@ -242,7 +242,7 @@ endif::[]
 
 == Disable partitions
 
-Problems that prevent normal cluster startup may be isolated to certain partitions or topics. You can use rpk or the xref:api:ROOT:admin-api.adoc#tag/Partitions[Admin API] to disable these partitions at the topic level, or individual partition level. A disabled partition or topic returns a `Replica Not Available` error code for Kafka API requests.
+Problems that prevent normal cluster startup may be isolated to certain partitions or topics. You can use rpk or the link:/api/doc/admin/group/endpoint-partitions[Admin API] to disable these partitions at the topic level, or individual partition level. A disabled partition or topic returns a `Replica Not Available` error code for Kafka API requests.
 
 To disable a partition, you need a healthy controller in the cluster, so you must start the cluster in recovery mode if a problematic partition is affecting cluster startup. If you disable a partition while in recovery mode, starting Redpanda again in non-recovery mode leaves the partition in a deactivated state. You must explicitly re-enable the partition.
 
@@ -378,7 +378,7 @@ curl http://localhost:9644/v1/cluster/partitions/<partition-namespace>/<topic-na
 
 include::shared:partial$suggested-reading.adoc[]
 
-- xref:api:ROOT:admin-api.adoc[]
+- link:/api/doc/admin/[Admin API reference]
 
 // * xref:./tiered-storage.adoc#whole-cluster-restore-for-disaster-recovery[] - this PR is not yet merged
 * xref:cluster-maintenance/rolling-restart.adoc[]
diff --git a/modules/migrate/pages/kubernetes/strimzi.adoc b/modules/migrate/pages/kubernetes/strimzi.adoc
@@ -304,7 +304,7 @@ TIP: You can use the xref:redpanda-connect:get-started:quickstarts/helm-chart.ad
 [[migrate-kafkabridge]]
 ==== Migrate the KafkaBridge resource
 
-Redpanda includes a built-in HTTP proxy on each broker, enabling direct HTTP-based interactions without the need for a separate bridge component. For details, see xref:develop:http-proxy.adoc[]. For the API reference, see xref:api:ROOT:pandaproxy-rest.adoc[].
+Redpanda includes a built-in HTTP proxy on each broker, enabling direct HTTP-based interactions without the need for a separate bridge component. For details, see xref:develop:http-proxy.adoc[]. For the complete API reference, see link:/api/doc/http-proxy/[HTTP Proxy API reference].
 
 [[migrate-kafkamirrormaker]]
 ==== Migrate the KafkaMirrorMaker2 resource
diff --git a/modules/reference/pages/api-reference.adoc b/modules/reference/pages/api-reference.adoc
@@ -3,12 +3,12 @@
 
 Use Redpanda's API reference documentation to learn about and interact with API endpoints:
 
-* xref:api:ROOT:pandaproxy-schema-registry.adoc[Schema Registry API Reference]
+* link:/api/doc/schema-registry/[Schema Registry API Reference]
 +
 Manage schemas within a Redpanda cluster. See also: xref:manage:schema-reg/index.adoc[Schema Registry documentation].
-* xref:api:ROOT:pandaproxy-rest.adoc[HTTP Proxy API Reference]
+* link:/api/doc/http-proxy/[HTTP Proxy API Reference]
 +
 HTTP Proxy is an HTTP server that exposes operations you can perform directly on a Redpanda cluster. Use the Redpanda HTTP Proxy API to perform a subset of actions that are also available through the Kafka API, but using simpler REST operations. See also: xref:develop:http-proxy.adoc[Use Redpanda with the HTTP Proxy API].
-* xref:api:ROOT:admin-api.adoc[Admin API Reference]
+* link:/api/doc/admin/[Admin API Reference]
 +
 Manage components of a Redpanda cluster, such as individual brokers and partition leadership. The Redpanda Admin API also allows you to perform operations that are specific to Redpanda Self-Managed and cannot be done using the standard Kafka API.
diff --git a/modules/upgrade/partials/rolling-upgrades/enable-maintenance-mode.adoc b/modules/upgrade/partials/rolling-upgrades/enable-maintenance-mode.adoc
@@ -52,7 +52,7 @@ curl -X GET "http://<broker-address>:<admin-api-port>/v1/broker/pre_restart_prob
 +
 In this example, the restart probe indicates that there is an under-replicated partition `kafka/topic_a/0` (with a replication factor of 1) at risk of going offline if the broker is restarted.
 +
-See the xref:api:ROOT:admin-api.adoc#get-/v1/broker/pre_restart_probe[Admin API reference] for more details on the restart probe endpoint.
+See the link:/api/doc/admin/operation/operation-pre_restart_probe[Admin API reference] for more details on the restart probe endpoint.
 
 ifdef::rolling-upgrade[. Select a broker that has not been upgraded yet and place it into maintenance mode:]
 ifdef::rolling-restart[. Select a broker and place it into maintenance mode:]
diff --git a/modules/upgrade/partials/rolling-upgrades/post-upgrade-tasks.adoc b/modules/upgrade/partials/rolling-upgrades/post-upgrade-tasks.adoc
@@ -13,7 +13,7 @@ To view additional information about your brokers, run:
 rpk redpanda admin brokers list
 ```
 
-You can also use the xref:api:ROOT:admin-api.adoc#get-/v1/broker/post_restart_probe[Admin API] to check how much each broker has progressed in recovering its workloads:
+You can also use the link:/api/doc/admin/operation/operation-post_restart_probe[Admin API] to check how much each broker has progressed in recovering its workloads:
 
 ```bash
 curl -X GET "http://<broker-address>:<admin-api-port>/v1/broker/post_restart_probe"

Original file line number	Diff line number	Diff line change
`@@ -13,7 +13,7 @@ NOTE: If you want to instead force recover all partitions in bulk from a set of`
`13`	`13`
`14`	`14`	The following examples assume that partition 0 in topic `test` is unavailable and its replicas cannot form a majority to elect a leader.
`15`	`15`
`16`		-. Call the xref:api:ROOT:admin-api.adoc#tag/Partitions/operation/get_topic_partitions[`/partitions/kafka/<topic>`] endpoint to determine the current broker and shard assignments of the partition replicas.
	`16`	+. Call the link:/api/doc/admin/operation/operation-get_topic_partitions[`/partitions/kafka/<topic>`] endpoint to determine the current broker and shard assignments of the partition replicas.
`17`	`17`	`+`
`18`	`18`	`[,bash]`
`19`	`19`	`----`
`@@ -77,7 +77,7 @@ curl -X POST http://localhost:9644/v1/debug/partitions/kafka/test/0/force_replic`
`77`	`77`	`+`
`78`	`78`	`The request body includes the broker ID and the CPU core (shard ID) for the replica on broker 1, to hydrate the new replicas assigned to brokers 4 and 5 on cores 1 and 0 respectively.`
`79`	`79`	`+`
`80`		-If there are `n` CPU cores on the machine, the value of `core` can be within the range `[0, n-1]`. You may use a random value within the range, or the least loaded shard. See the xref:reference:public-metrics-reference.adoc[public metrics reference] for metrics regarding CPU usage, and xref:api:ROOT:admin-api.adoc#tag/Partitions/operation/force_update_partition_replicas[Redpanda Admin API] for additional detail.
	`80`	+If there are `n` CPU cores on the machine, the value of `core` can be within the range `[0, n-1]`. You may use a random value within the range, or the least loaded shard. See the xref:reference:public-metrics-reference.adoc[public metrics reference] for metrics regarding CPU usage, and link:/api/doc/admin/operation/operation-force_update_partition_replicas[Redpanda Admin API] for additional detail.
`81`	`81`
`82`	`82`	`include::shared:partial$suggested-reading.adoc[]`
`83`	`83`
Original file line number	Diff line number	Diff line change
@@ -142,7 +142,7 @@ Use any of the following to set `redpanda.iceberg.mode`:
`142`	`142`	`+`
`143`	`143`	* `rpk`. See the following examples to run `rpk topic` commands.
`144`	`144`	* The Cloud UI. Navigate to Topics to create a new topic and specify `redpanda.iceberg.mode` in Additional Configuration, or edit an existing topic under the topic's Configuration tab.
`145`		-* The Data Plane API to xref:api:ROOT:cloud-dataplane-api.adoc#post-/v1/topics[create a new topic] or xref:api:ROOT:cloud-dataplane-api.adoc#patch-/v1/topics/-topic_name-/configurations[update a property for an existing topic]. Specify the key-value pair for `redpanda.iceberg.mode` in the request body.
	`145`	+* The Data Plane API to link:/api/doc/cloud-dataplane/operation/operation-topicservice_createtopic[create a new topic] or link:/api/doc/cloud-dataplane/operation/operation-topicservice_updatetopicconfigurations[update a property for an existing topic]. Specify the key-value pair for `redpanda.iceberg.mode` in the request body.
`146`	`146`	`endif::[]`
`147`	`147`	`+`
`148`	`148`	The following examples show how to use `rpk` to create a new topic or alter the configuration for an existing topic, setting the Iceberg mode to `key_value`.
Original file line number	Diff line number	Diff line change
`@@ -149,7 +149,7 @@ Cloud API::`
`149`	`149`	`+`
`150`	`150`	`--`
`151`	`151`	. Authenticate and make a `GET /v1/clusters/\{id}` request to xref:manage:api/cloud-dataplane-api.adoc#get-data-plane-api-url[retrieve the Data Plane API URL] for your cluster.
`152`		-. Make a request to xref:api:ROOT:cloud-dataplane-api.adoc#post-/v1/secrets[`POST /v1/secrets`]. You must use a Base64-encoded secret.
	`152`	+. Make a request to link:/api/doc/cloud-dataplane/operation/operation-secretservice_createsecret[`POST /v1/secrets`]. You must use a Base64-encoded secret.
`153`	`153`	`+`
`154`	`154`	`[,bash]`
`155`	`155`	`----`
`@@ -196,7 +196,7 @@ rpk cluster config set iceberg_rest_catalog_client_secret ${secrets.<secret-name`
`196`	`196`	`Cloud API::`
`197`	`197`	`+`
`198`	`198`	`--`
`199`		-Make a request to the xref:api:ROOT:cloud-controlplane-api.adoc#patch-/v1/clusters/-cluster.id-[`PATCH /v1/clusters/<cluster-id>`] endpoint of the Control Plane API.
	`199`	+Make a request to the link:/api/doc/cloud-controlplane/operation/operation-clusterservice_updatecluster[`PATCH /v1/clusters/<cluster-id>`] endpoint of the Control Plane API.
`200`	`200`
`201`	`201`	`[,bash]`
`202`	`202`	`----`