Merge pull request #77 from XDeFi-tech/chore/update-endpoint-routingapi

components/ChainsV2.jsx

@@ -3,7 +3,7 @@ import LoadingIcon from "./LoadingIcon";
 import PlayIcon from "./PlayIcon";
 
 export default function ChainsV2() {
-  const ENDPOINT = "https://routingapi.xdefi.services/";
+  const ENDPOINT = "https://routingapi.xdefiservices.com/";
   const [response, setResponse] = useState([]);
   const [loading, setLoading] = useState(false);
 

routing/introduction.md

@@ -28,13 +28,13 @@ First, given a pair tokenA/tokenB, with assets belonging to the same chain or se
 ## Connecting to the API
 
 Before connecting to the API, one needs to go through the Ctrl (fka XDEFI) VPN to access it or to whitelist the IP address.
-API endpoints share the same root URL: https://routingapi.xdefi.services/.
+API endpoints share the same root URL: https://routingapi.xdefiservices.com/.
 
 To check the health status of the API just send a GET request to the above URL:
 ::: code-group
 
 ```ts [Request]
-URL = "https://routingapi.xdefi.services";
+URL = "https://routingapi.xdefiservices.com";
 
 response = await fetch(URL);
 

routing/query-mutation-details.md

@@ -16,7 +16,7 @@ Both of these queries return information about assets available in one (chain, g
 While `chainsV2` has no parameters, `chainV2` takes one of the following chain names:
 
 ```js [JavaScript]
-const ENDPOINT = "https://routingapi.xdefi.services/";
+const ENDPOINT = "https://routingapi.xdefiservices.com/";
 
 const fetchChainsV2 = async () => {
   fetch(ENDPOINT + "chains")