V2 Integration Guide
This page describes how to integrate Play Style Profiles (Strategy Profiles V2) into your requests. For the list of profiles available, see the Universal Poker reference.
Understanding the Metrics
- VPIP: Percentage of hands Voluntarily Put money In Pot
- PFR: Percentage of hands with Pre-Flop Raise
- WTSD: Percentage of hands that Went To ShowDown
- AF: Aggression Factor (ratio of aggressive to passive actions)
- BB/100: Big blinds won per 100 hands (relative to GTO baseline)
Profile Name Format
Profile names match the target_profile_name API format. Use vpip / pfr for preflop, af / wtsd for postflop. Combine both pairs to bias both streets in a single name.
target_profile_name | Effect |
|---|---|
"vpip34-pfr14" | Preflop: VPIP=34%, PFR=14%. Postflop: GTO |
"af2.0-wtsd50" | Preflop: GTO. Postflop: AF=2.0, WTSD=50% |
"vpip34-pfr14-af2.0-wtsd50" | Both streets |
"vpip+5-pfr-6" | Offset from GTO (table-size independent) |
"gto" or "" | GTO for all streets |
Release Information
Postflop strategy profiles V2 will be available to B2B clients on January 07, 2026.
Request Format
Strategy Profiles V2 uses the same request structure as V1. Include the strategy profile object in your request:
{
"request_id": "unique-request-id",
"hand": {...},
"strategy_profile": {
"target_profile_name": "wtsd51-af1.2"
}
}Important: Match profile types to game types:
- Preflop profiles → Preflop games
- Postflop profiles → Postflop games
Verifying Profile Application
Check solution_information.strategy_profile_config in the response to confirm profile application.
When profile is not applied:
{
"request": {},
"strategy": {<default results>},
"solution_information": {
(...),
"strategy_profile_config": {
"game_format": "no_profile_applied",
"matched_profile_name": "no_profile_applied",
"strategy_after_adjust": "no_profile_applied",
"strategy_before_adjust": "no_profile_applied"
}
}
}Error Handling Behavior
Non-existent Profile Names
- Request succeeds with default GTO strategy
- Response includes
no_profile_appliedstatus - No service disruption
Profile Type Mismatch
Using preflop profiles for postflop games or vice versa:
- Request succeeds with default GTO strategy
- Response includes
no_profile_appliedstatus - Profile is ignored
MTT Tournament Requests
Warning: Strategy Profiles V2 are for cash games only.
- MTT requests with V2 profiles will fail
- Use legacy: Strategy Profiles V1 for MTT tournaments (supports
2-15game format)
Quick Reference
| Scenario | Request Result | Response Status | Strategy Applied |
|---|---|---|---|
| Valid profile + correct game type | Success | Profile name shown | Adjusted strategy |
| Invalid profile name | Success | no_profile_applied | Default GTO |
| Preflop profile → Postflop game | Success | no_profile_applied | Default GTO |
| Postflop profile → Preflop game | Success | no_profile_applied | Default GTO |
| V2 Profile → MTT tournament | Failure | Error response | N/A |