fix(interlink): fixed links

RoRoJ · RoRoJ · commit d7e638d93157 · 2025-01-29T11:00:01.000+01:00
diff --git a/network/interlink/index.mdx b/network/interlink/index.mdx
@@ -16,7 +16,7 @@ meta:
    productName="InterLink"
    productLogo="interlink"
    description="InterLink lets you create a secure, private connection between your external infrastructure, and your Scaleway VPC."
-   url="/network/interlink/quickstart/"
+   url="https://www.scaleway.com/en/developers/api/api/interlink/#quickstart"
    label="InterLink Quickstart"
 />
 
diff --git a/network/interlink/reference-content/configuring.mdx b/network/interlink/reference-content/configuring.mdx
@@ -43,21 +43,21 @@ Attaching an InterLink to a VPC allows you to complete the connection from your
 z
 The VPC must be in the same region region as the InterLink. An InterLink can only be attached to one VPC at a time, but you are free to detach the VPC and attach a different one whenever you like.
 
-You can use the [Attach a VPC](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-links-attach-a-vpc) endpoint to attach a VPC to a given InterLink.
+You can use the [Attach a VPC](https://www.scaleway.com/en/developers/api/interlink/#path-links-attach-a-vpc) endpoint to attach a VPC to a given InterLink.
 
 ### 3. Attach allowed routes list (routing policy)
 
 By default, all routes across an InterLink are blocked by default. You must create and attach an [allowed routes list](/network/interlink/concepts/#allowed-routes-list) aka routing policy, to set IP prefix filters for the routes you want to whitelist. This facilitates traffic flow across the InterLink.
 
-You can [create](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-routing-policies-create-a-routing-policy) and [attach](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-links-attach-a-routing-policy) allowed routes lists via the API.
+You can [create](https://www.scaleway.com/en/developers/api/interlink/#path-routing-policies-create-a-routing-policy) and [attach](https://www.scaleway.com/en/developers/api/interlink/#path-links-attach-a-routing-policy) allowed routes lists via the API.
 
 When setting the route ranges to whitelist, you must separately define the IP prefixes to accept from the external infrastructure (incoming ranges of route announcements to accept), and the IP prefix filters to advertise from the Scaleway VPC to the peer (outgoing ranges of routes to advertise). For example, adding `172.16.4.0/22` whitelists all 1,024 IPs in this block, from `172.16.4.0` to `172.16.7.255`.
 
 Only one allowed routes list (routing policy) can be attached to an InterLink at a given time. However, you can reuse the same list by attaching it to multiple InterLinks, for example if you have a second InterLink attached to the same VPC/external infrastructure for redundance purposes. You can update, delete or reattach a list at any time.
 
 ### 4. Activate route propagation.
 
-Once you have attached a VPC and defined the routing policy/allowed routes, you must [activate route propagation](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-links-enable-route-propagation) to allow traffic to flow over the InterLink. This enables all prefixes whitelisted in your allowed routes list / routing policy to be announced in the BGP session, so that traffic can flow along these routes. 
+Once you have attached a VPC and defined the routing policy/allowed routes, you must [activate route propagation](https://www.scaleway.com/en/developers/api/interlink/#path-links-enable-route-propagation) to allow traffic to flow over the InterLink. This enables all prefixes whitelisted in your allowed routes list / routing policy to be announced in the BGP session, so that traffic can flow along these routes. 
 
 <Message type="important">
 Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy (aka allowed routes list) to the InterLink to allow traffic to flow.
diff --git a/network/interlink/reference-content/provisioning.mdx b/network/interlink/reference-content/provisioning.mdx
@@ -33,10 +33,10 @@ For full information about different statuses an InterLink might flow through, s
 
 ### 1. User orders InterLink via Scaleway
 
-The order process begins when you order an InterLink via the Scaleway [InterLink API](https://www.scaleway.com/en/developers/api/interlink/) (or, coming soon, via the [Scaleway console](https://console.scaleway.com/) or one of our other [developer tools](https://www.scaleway.com/en/developers/)). To order via the API, use the [Create a link](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-links-create-a-link) call. You need to set the following parameters when ordering:
+The order process begins when you order an InterLink via the Scaleway [InterLink API](https://www.scaleway.com/en/developers/api/interlink/) (or, coming soon, via the [Scaleway console](https://console.scaleway.com/) or one of our other [developer tools](https://www.scaleway.com/en/developers/)). To order via the API, use the [Create a link](https://www.scaleway.com/en/developers/api/interlink/#path-links-create-a-link) call. You need to set the following parameters when ordering:
 
 - **Connection type**: In the long term, dedicated, shared and hosted InterLinks will be available. For now, only **hosted** connections (facilitated via a partner) are available.
-- **Partner**: The third-party service provider to facilitate the InterLink. Use the [List available partners](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-partners-list-available-partners) call to find available partners.
+- **Partner**: The third-party service provider to facilitate the InterLink. Use the [List available partners](https://www.scaleway.com/en/developers/api/interlink/#path-partners-list-available-partners) call to find available partners.
 - **Region**: The region in which to create the InterLink. It must correspond to the region of the Scaleway VPC you want to later attach to the InterLink.
 - **Location**: The physical **P**oint **o**f **P**resence (PoP) where the connection to Scaleway's network will be established, via the partner.
 - **Bandwidth**: The maximum bandwidth which you want to be available over the InterLink.
@@ -46,7 +46,7 @@ The order process begins when you order an InterLink via the Scaleway [InterLink
 Scaleway starts charging for the InterLink as soon as your order is placed. You must then wait for the partner to provision the connection, and they may charge you additional fees.
 </Message>
 
-After placing the order via the API, the ID of the InterLink is returned in the response. You can use this ID to [check the status of your InterLink](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-links-get-a-link) at any time.
+After placing the order via the API, the ID of the InterLink is returned in the response. You can use this ID to [check the status of your InterLink](https://www.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) at any time.
 
 Immediately after ordering, it is expected that your InterLInk will briefly be in `Configuring` status, before moving to `Requested` status. 
 
@@ -58,7 +58,7 @@ If you see a `Failed` status, it means there was a configuration error on the Sc
 
 After ordering the InterLink from Scaleway, you **must** contact your chosen partner to request that they provision the connection on their side. Scaleway is not able to automatically do this step for you.
 
-Use the [Get a partner](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-partners-get-a-partner) endpoint to get information about your selected partner. Each partner provides either a contact email address, and/or the URL of their online portal. You should make contact with your partner via one of these channels.
+Use the [Get a partner](https://www.scaleway.com/en/developers/api/interlink/#path-partners-get-a-partner) endpoint to get information about your selected partner. Each partner provides either a contact email address, and/or the URL of their online portal. You should make contact with your partner via one of these channels.
 
 TODO INFO ABOUT PAIRING KEY
 
@@ -94,7 +94,7 @@ A `Locked` status indicates, again, that the InterLink was provisioned, but Scal
 When you no longer want your InterLink connection, you can delete it. The process is as follows:
 
 1. Deactivate route propagation.
-2. [Delete your InterLink on the Scaleway side](https://www.scaleway.com/en/developers/api/interlink/v1beta1/#path-links-delete-a-link). InterLink status moves to `Deprovisioning`.
+2. [Delete your InterLink on the Scaleway side](https://www.scaleway.com/en/developers/api/interlink/#path-links-delete-a-link). InterLink status moves to `Deprovisioning`.
 3. Contact your partner to request they provision the InterLink resource on their side.
 4. InterLink moves to `Deleted` status once the partner has completed deprovisioning.
 
diff --git a/network/interlink/reference-content/statuses.mdx b/network/interlink/reference-content/statuses.mdx
@@ -19,7 +19,7 @@ dates:
 InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers.
 </Message>
 
-An InterLink always has a **status**, which can be retrieved via the API using the [Get a link](https://scaleway-developers-production-internal.s3-website.fr-par.internal.scaleway.com/en/developers/api/interlink/v1beta1/#path-links-get-a-link) call.
+An InterLink always has a **status**, which can be retrieved via the API using the [Get a link](https://scaleway-developers-production-internal.s3-website.fr-par.internal.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) call.
 
 This document explains the different statuses possible for an InterLink, and how to understand them.
 
