This API is in private preview. Target October 2026; timing is subject to change.
Returns registered outcome templates for HIP-4 deployment planning.
Available now. This read is served at the interim endpoint today.
POST /{apiKey}/info
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | Selects outcomeTemplates. |
{
"type": "outcomeTemplates"
}| Field | Type | Description |
|---|---|---|
[] | array | Outcome-template entries. |
[].id | string | Template identifier, for example binaryPrice. |
[].role | object | Role configuration for the template. |
[].role.standaloneOutcome | object | Observed role configuration for a standalone outcome. |
[].role.standaloneOutcome.sideNames | array | Side names in the observed standalone-outcome role configuration. |
[].name | string | Human-readable label shown for the template. |
[].description | string | Human-readable explanation of the template's purpose. |
[].keywords | array | Search terms associated with the template. |
[
{
"id": "binaryPrice",
"role": {
"standaloneOutcome": {
"sideNames": ["Yes", "No"]
}
},
"name": "{perp} above {threshold} at {time}?",
"description": "The market resolves to Yes if the {perp} price is above {threshold} at {time}..."
}
]The 2026-09-02 capture returned seven templates on mainnet. validatorL1Votes records registerTemplate actions through which templates are registered in validator governance. For deployment context, see Deploying Hyperliquid markets.