> ## Documentation Index
> Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Hip4SideSpec Schema

> Per-side spec nested in Hip4OutcomeAggregate.sidespecs. Includes parameters, response shapes, examples, and implementation notes from the 0xArchive contract.

Source OpenAPI: 0xArchive API 1.8.0; 227 paths; 217 component schemas.

Per-side spec nested in `Hip4OutcomeAggregate.side_specs`. One element per side (typically two: side 0 = Yes, side 1 = No).

## Required Fields

| Field | Type | Description |
| - | - | - |
| `asset_id` | integer:int64 | Public asset ID for this side |
| `coin` | string | Coin identifier for this side. |
| `name` | string | Human label for this side |
| `side` | integer | Side index: 0 = Yes, 1 = No |

## JSON Schema

```json theme={"theme":"github-dark"}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Hip4SideSpec",
  "description": "Per-side spec nested in `Hip4OutcomeAggregate.side_specs`. One element per side (typically two: side 0 = Yes, side 1 = No).",
  "type": "object",
  "required": [
    "asset_id",
    "coin",
    "name",
    "side"
  ],
  "properties": {
    "asset_id": {
      "description": "Public asset ID for this side",
      "type": "integer",
      "format": "int64",
      "example": 100000000
    },
    "coin": {
      "description": "Coin identifier for this side. Returned in `#`-prefixed form. REST paths accept either the bare numeric id (e.g. `0`) or the `#`-prefixed form (e.g. `#0`).",
      "type": "string",
      "example": "#0"
    },
    "name": {
      "description": "Human label for this side",
      "type": "string",
      "example": "Yes"
    },
    "side": {
      "description": "Side index: 0 = Yes, 1 = No",
      "type": "integer",
      "enum": [
        0,
        1
      ],
      "example": 0
    }
  }
}
```

## Components using this schema

* [Hip4OutcomeAggregate](/schemas/components/hip4-outcome-aggregate)

## Referenced By

Use this shared schema with the generated component index and route-specific endpoint pages during implementation.

## Operations using this component transitively

* [`GET /v1/hyperliquid/hip4/outcomes`](/schemas/operations/list-hip4-outcomes)
* [`GET /v1/hyperliquid/hip4/outcomes/{outcome_id}`](/schemas/operations/get-hip4-outcome)
* [`GET /v1/hyperliquid/hip4/outcomes/by-slug/{slug}`](/schemas/operations/get-hip4-outcome-by-slug)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.