diff --git a/docs-main/appdev/faq.mdx b/docs-main/appdev/faq.mdx index 93ca13f4b..85df2c318 100644 --- a/docs-main/appdev/faq.mdx +++ b/docs-main/appdev/faq.mdx @@ -286,9 +286,18 @@ This error indicates the mediator didn't receive sufficient confirmations from a 2. Verify all validators are healthy 3. Top up CC if needed: ```bash - curl -X POST "http://localhost/api/validator/v0/admin/traffic/purchase" \ - -H "Authorization: Bearer $TOKEN" + curl -X POST "http://localhost/api/validator/v0/wallet/buy-traffic-requests" \ + -H "Authorization: Bearer $TOKEN" \ + -H "Content-Type: application/json" \ + -d '{ + "receiving_validator_party_id": "", + "domain_id": "", + "traffic_amount": 100000, + "tracking_id": "", + "expires_at": + }' ``` + See [Buying Traffic](/sdks-tools/api-reference/splice-validator-api#buying-traffic) for the full request/response schema. The error message includes `unresponsiveParties` which tells you which party(ies) didn't respond. @@ -585,10 +594,18 @@ Navigate to the wallet interface and use the top-up functionality. **Via API:** ```bash -curl -X POST "http://localhost/api/validator/v0/admin/traffic/purchase" \ +curl -X POST "http://localhost/api/validator/v0/wallet/buy-traffic-requests" \ -H "Authorization: Bearer $TOKEN" \ - -H "Content-Type: application/json" + -H "Content-Type: application/json" \ + -d '{ + "receiving_validator_party_id": "", + "domain_id": "", + "traffic_amount": 100000, + "tracking_id": "", + "expires_at": + }' ``` +This only creates the request; check its status with the `/v0/wallet/buy-traffic-requests/{tracking_id}/status` endpoint. See [Buying Traffic](/sdks-tools/api-reference/splice-validator-api#buying-traffic) for the full request/response schema. **Automatic top-ups:** Configure automatic traffic purchases in your validator configuration: diff --git a/docs-main/global-synchronizer/troubleshooting-guide/runbooks.mdx b/docs-main/global-synchronizer/troubleshooting-guide/runbooks.mdx index 6547767cb..a2b0906db 100644 --- a/docs-main/global-synchronizer/troubleshooting-guide/runbooks.mdx +++ b/docs-main/global-synchronizer/troubleshooting-guide/runbooks.mdx @@ -71,9 +71,18 @@ If `availableTraffic` is 0 or traffic limits are exhausted, purchase traffic or 1. Purchase traffic immediately: ```bash - curl -X POST "http://localhost/api/validator/v0/admin/traffic/purchase" \ - -H "Authorization: Bearer $TOKEN" + curl -X POST "http://localhost/api/validator/v0/wallet/buy-traffic-requests" \ + -H "Authorization: Bearer $TOKEN" \ + -H "Content-Type: application/json" \ + -d '{ + "receiving_validator_party_id": "", + "domain_id": "", + "traffic_amount": 100000, + "tracking_id": "", + "expires_at": + }' ``` + This only creates the request; check its status with the `/v0/wallet/buy-traffic-requests/{tracking_id}/status` endpoint. See [Buying Traffic](/sdks-tools/api-reference/splice-validator-api#buying-traffic) for the full request/response schema. 2. Enable auto-top-up to prevent recurrence: ```yaml # In validator-values.yaml diff --git a/docs-main/global-synchronizer/troubleshooting-guide/transaction-failures.mdx b/docs-main/global-synchronizer/troubleshooting-guide/transaction-failures.mdx index c7c642f84..2ce6b2bf4 100644 --- a/docs-main/global-synchronizer/troubleshooting-guide/transaction-failures.mdx +++ b/docs-main/global-synchronizer/troubleshooting-guide/transaction-failures.mdx @@ -110,10 +110,20 @@ If the balance is zero or near-zero, transactions will fail because the sequence **Top up traffic:** ```bash -curl -X POST "http://localhost/api/validator/v0/admin/traffic/purchase" \ - -H "Authorization: Bearer $TOKEN" +curl -X POST "http://localhost/api/validator/v0/wallet/buy-traffic-requests" \ + -H "Authorization: Bearer $TOKEN" \ + -H "Content-Type: application/json" \ + -d '{ + "receiving_validator_party_id": "", + "domain_id": "", + "traffic_amount": 100000, + "tracking_id": "", + "expires_at": + }' ``` +This only creates the request; check its status with the `/v0/wallet/buy-traffic-requests/{tracking_id}/status` endpoint. See [Buying Traffic](/sdks-tools/api-reference/splice-validator-api#buying-traffic) for the full request/response schema. + **Enable auto-top-up** to prevent this from recurring. In your `validator-values.yaml`: ```yaml