Skip to content

Fix placeholder traffic-purchase endpoint in troubleshooting docs #1207

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
miller-da merged 2 commits into from
Aug 6, 2026
+44 −8
Merged

Fix placeholder traffic-purchase endpoint in troubleshooting docs #1207

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
928f0d9
Fix fabricated traffic-purchase endpoint in troubleshooting docs
8bitpal Aug 4, 2026
3d34129
Merge branch 'main' into content/fix-traffic-purchase-endpoint-1100
8bitpal Aug 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 21 additions & 4 deletions docs-main/appdev/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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": "<validator-party-id>",
"domain_id": "<synchronizer-id>",
"traffic_amount": 100000,
"tracking_id": "<unique-tracking-id>",
"expires_at": <expiry-unix-timestamp-micros>
}'
```
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.
</Accordion>
Expand Down Expand Up @@ -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": "<validator-party-id>",
"domain_id": "<synchronizer-id>",
"traffic_amount": 100000,
"tracking_id": "<unique-tracking-id>",
"expires_at": <expiry-unix-timestamp-micros>
}'
```
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:
Expand Down
13 changes: 11 additions & 2 deletions docs-main/global-synchronizer/troubleshooting-guide/runbooks.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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": "<validator-party-id>",
"domain_id": "<synchronizer-id>",
"traffic_amount": 100000,
"tracking_id": "<unique-tracking-id>",
"expires_at": <expiry-unix-timestamp-micros>
}'
```
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
Expand Down
14 changes: 12 additions & 2 deletions docs-main/global-synchronizer/troubleshooting-guide/transaction-failures.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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": "<validator-party-id>",
"domain_id": "<synchronizer-id>",
"traffic_amount": 100000,
"tracking_id": "<unique-tracking-id>",
"expires_at": <expiry-unix-timestamp-micros>
}'
```

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
Expand Down