Skip to content

Commit c7e317c

Browse files
Fix broken links from BYOIP to the API docs
1 parent 151d140 commit c7e317c

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

src/content/docs/byoip/concepts/dynamic-advertisement/best-practices.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ After saving your changes, it takes between two to seven minutes to enable adver
5555

5656
### Via the API
5757

58-
To configure prefix advertisement with the Cloudflare API, use the [IP Address Management and Dynamic Advertisement](/api/resources/addressing/subresources/prefixes/subresources/bgp/subresources/statuses/methods/get/) API.
58+
To configure prefix advertisement with the Cloudflare API, use the [IP Address Management and Dynamic Advertisement](/api/resources/addressing/subresources/prefixes/subresources/advertisement_status/methods/edit/) API.
5959

6060
Most dynamic advertisement operations require that you supply the Cloudflare ID for any prefix you want to access with the Cloudflare API. The following section outlines how to obtain prefix IDs.
6161

src/content/docs/byoip/service-bindings/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,12 +12,12 @@ description: In IP address management, service binding refers to the association
1212
Service bindings are mappings that control whether traffic destined for a given IP address is routed to [Magic Transit](/magic-transit/), the CDN pipeline [^1], or the Spectrum pipeline [^2].
1313

1414
:::note
15-
Service binding operations are currently only available via API. You can find all endpoints and their specifications in the [Cloudflare API documentation](/api/resources/addressing/subresources/prefixes/subresources/bgp/subresources/bindings/methods/list/).
15+
Service binding operations are currently only available via API. You can find all endpoints and their specifications in the [Cloudflare API documentation](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/).
1616
:::
1717

1818
## Scope
1919

20-
Customers using BYOIP with Magic Transit can leverage the [service binding API endpoints](/api/resources/addressing/subresources/prefixes/subresources/bgp/subresources/bindings/methods/list/) to selectively route traffic through the CDN [^1] or Spectrum [^2] pipelines on a per-IP address basis.
20+
Customers using BYOIP with Magic Transit can leverage the [service binding API endpoints](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/) to selectively route traffic through the CDN [^1] or Spectrum [^2] pipelines on a per-IP address basis.
2121

2222
You can upgrade individual IPs within a Magic Transit prefix to either a CDN IP or a Spectrum IP. For example, if you have `203.0.113.0/24`, you can upgrade `203.0.113.1` to CDN and `203.0.113.2` to Spectrum.
2323

src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ At this point, continuing the [example](#before-you-begin), you should have a ma
6262

6363
</Example>
6464

65-
4. To confirm you currently only have a Magic Transit service binding and that it spans across your entire prefix, make a `GET` request to the [List Service Bindings](/api/resources/addressing/subresources/prefixes/subresources/bgp/subresources/bindings/methods/list/) endpoint. Replace the `{prefix_id}` in the URI path by the actual prefix ID you got from the previous step.
65+
4. To confirm you currently only have a Magic Transit service binding and that it spans across your entire prefix, make a `GET` request to the [List Service Bindings](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/methods/list/) endpoint. Replace the `{prefix_id}` in the URI path by the actual prefix ID you got from the previous step.
6666

6767
<Example>
6868

@@ -79,7 +79,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/addressing/prefi
7979
Once a service binding is created (or deleted), it will take four to six hours to propagate across Cloudflare's global network. Services for the IP addresses in scope will likely be disrupted during this window.
8080
:::
8181

82-
1. Make a `POST` request to the [Create service binding](/api/resources/addressing/subresources/prefixes/subresources/bgp/subresources/bindings/methods/create/) endpoint, indicating the IP address you want to bind to the CDN. Specify the **corresponding network mask** as needed.
82+
1. Make a `POST` request to the [Create service binding](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/methods/create/) endpoint, indicating the IP address you want to bind to the CDN. Specify the **corresponding network mask** as needed.
8383

8484
<Example>
8585

@@ -119,7 +119,7 @@ In the response body, the initial provisioning state should be `provisioning`.
119119

120120
</Example>
121121

122-
You can periodically check the service binding status using the [List Service Bindings](/api/resources/addressing/subresources/prefixes/subresources/bgp/subresources/bindings/methods/list/) endpoint.
122+
You can periodically check the service binding status using the [List Service Bindings](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/methods/list/) endpoint.
123123

124124
## 3. Create address maps
125125

0 commit comments

Comments
 (0)