feat: update docs to clarify usage of getCallsStatus versus

getCrossChainStatus

Author: Zer0dot

docs/pages/transactions/cross-chain-swap-tokens/api.mdx

@@ -166,4 +166,52 @@ For other potential responses, [check out the API reference!](/docs/wallets/api-
 
 </Step>
 
+<Step title="Track the cross-chain swap">
+
+<Tip>
+  We recommend using `wallet_getCrossChainStatus_v0` for richer data including
+  separate origin and destination transaction details. [See the tracking
+  documentation](/wallets/transactions/cross-chain-swap-tokens#tracking-a-cross-chain-swap)
+  for more details.
+</Tip>
+
+You can use the `wallet_getCallsStatus` endpoint to check the status of your cross-chain swap. Cross-chain swaps may take longer than single-chain swaps due to cross-chain messaging.
+
+```bash
+curl -X POST https://api.g.alchemy.com/v2/{API_KEY} \
+  -H "Content-Type: application/json" \
+  -d '{
+    "jsonrpc": "2.0",
+    "method": "wallet_getCallsStatus",
+    "params": [
+      [
+        "{CALL_ID_FROM_STEP_2_OR_STEP_4}"
+      ]
+    ],
+    "id": 1
+  }'
+```
+
+This returns:
+
+```json
+{
+  "id": "1",
+  "jsonrpc": "2.0",
+  "result": {
+    "id": "CALL_ID",
+    "chainId": "SOURCE_CHAIN_ID",
+    "atomic": true,
+    "status": 200,
+    "receipts": [...]
+  }
+}
+```
+
+To get your transaction hash, you can access `result.receipts[0].transactionHash`.
+
+For status codes and more details on tracking cross-chain swaps, see the [tracking documentation](/wallets/transactions/cross-chain-swap-tokens#tracking-a-cross-chain-swap).
+
+</Step>
+
 </Steps>

docs/pages/transactions/cross-chain-swap-tokens/client.mdx

@@ -106,3 +106,7 @@ export const client = createSmartWalletClient({
 ```
 
 </CodeBlocks>
+
+## Status codes
+
+For status codes and more details on tracking cross-chain swaps, see the [tracking documentation](/wallets/transactions/cross-chain-swap-tokens#tracking-a-cross-chain-swap).

docs/pages/transactions/cross-chain-swap-tokens/index.mdx

@@ -78,6 +78,12 @@ After sending your cross-chain swap, you can track its progress using the `walle
   via API only. SDK support coming soon.
 </Info>
 
+<Tip>
+  The `wallet_getCrossChainStatus_v0` endpoint is in beta. Note that there may
+  be changes in the future to simplify the endpoint. We will let you know
+  if/when that happens.
+</Tip>
+
 ## Use the status endpoint
 
 Pass the `callId` from your swap request to check the current status:
@@ -210,11 +216,19 @@ The expiry is an informational indicator of when you can expect to be able to pr
 
 ## What are the different status codes for cross-chain swaps?
 
-Cross-chain swaps may have additional status codes beyond standard transaction statuses to reflect the cross-chain nature of the transaction. These are:
+Cross-chain swaps support comprehensive status tracking. See the [tracking documentation](/wallets/transactions/cross-chain-swap-tokens#status-codes) for a complete list of status codes including:
 
-- 120: Cross-chain in progress
-- 410: Cross-chain refund
+- 100: Pending
+- 110: Preconfirmed
+- 115: Preconfirmed Onchain Failure
+- 116: Preconfirmed Partial Onchain Failure
+- 120: Cross-Chain In Progress
+- 200: Confirmed
+- 400: Offchain Failure
+- 410: Cross-Chain Refunded
+- 500: Onchain Failure
+- 600: Partial Onchain Failure
 
 ## When is a CallId returned from `wallet_requestQuote_v0`?
 
-Any time you’re requesting a cross-chain quote via `wallet_requestQuote_v0` , a `callId` is returned. This `callId` includes important data for cross-chain tracking. You can use this just like any other `callId` in `wallet_getCallsStatus`!
+Any time you're requesting a cross-chain quote via `wallet_requestQuote_v0` , a `callId` is returned. This `callId` includes important data for cross-chain tracking. You can use this just like any other `callId` in `wallet_getCallsStatus` or `wallet_getCrossChainStatus_v0`!

docs/pages/transactions/cross-chain-swap-tokens/react.mdx

@@ -135,19 +135,9 @@ export default function CrossChainSwap() {
 
 Cross-chain swaps take longer than single-chain swaps due to cross-chain messaging and confirmation requirements.
 
-## Cross-chain status codes
-
-Cross-chain swaps have additional status codes to reflect the cross-chain nature:
-
-| Code    | Status                      |
-| ------- | --------------------------- |
-| 100     | Pending                     |
-| **120** | **Cross-Chain In Progress** |
-| 200     | Confirmed                   |
-| 400     | Offchain Failure            |
-| **410** | **Cross-chain Refund**      |
-| 500     | Onchain Failure             |
-| 600     | Partial Onchain Failure     |
+## Status codes
+
+For status codes and more details on tracking cross-chain swaps, see the [tracking documentation](/wallets/transactions/cross-chain-swap-tokens#tracking-a-cross-chain-swap).
 
 ## Swap options