Copy page

Recipes

Result/proof explorer

Use this recipe when you want a small result page or internal proof viewer for completed tournaments. It starts with the developer playground so you can exercise the loop in test mode before wiring a branded result surface.

Status: public-beta runnable for projects with a test-mode service-account token.

Public-clean example: examples/developer-platform/result-proof-explorer.

What you build

• A server route that emits the playground completion fixture.
• A server-side result/proof read with a pw_mgmt_... management token.
• A browser page that renders only the public-safe result/proof DTO.

Requirements

• A Console project.
• A service account token stored server-side.
• Management scopes: playground:write and tournament_result_proofs:read.
• Environment restriction: test.

1. Emit the playground completion

Code
curl https://api.pokerworks.io/api/v1/developer-api/management/playground/tournament-completion \
  -H "Authorization: Bearer pw_mgmt_..." \
  -H "Content-Type: application/json" \
  -d '{
    "projectId": "devproj_...",
    "fixture": "completed-six-max-nlhe-v1"
  }'

The response includes playground.id, queued webhook delivery summaries, the synthetic tournament.completed event envelope, and a resultProof object. The playground fixture is test-only and uses synthetic players such as Playground Alice; it never reads real player data.

2. Fetch the result/proof read

Use the returned playground tournament id:

Code
curl "https://api.pokerworks.io/api/v1/developer-api/management/tournaments/{playground.id}/result-proof" \
  -H "Authorization: Bearer pw_mgmt_..."

For webhook-driven recipes, prefer the links.resultProof.href discovery link from the signed event envelope and forward the verified PokerWorks-Event-Id and PokerWorks-Delivery-Id headers when you make this GET request.

3. Render the safe fields

Display only fields from the result/proof DTO:

• tournament.displayName, status, completedAt, and visibility;
• winner.displayName and winner.rank;
• standings[].displayName, rank, finalChips, and payout;
• evidence.replay.status, evidence.replay.url, and evidence.fairness.status;
• support.requestId, support.webhookEventId, and support.webhookDeliveryId for support.

Do not display or log raw player ids, private cards, deck order, proof secrets, webhook endpoint secrets, or management token metadata. Those fields are intentionally absent from the DTO.

Related

• Result/proof reads
• Webhooks
• Discord tournament announcements
• Google Sheets results export