SeatInfo Google Wallet API

User
seatInfo google wallet api detail for seat position like ringside or other
Assistant
In the **Google Wallet API for Event Tickets**, if you want to include **seat-related information** like "Ringside", "Section", "Row", or "Seat Number", you need to use the `seatInfo` object inside the **EventTicketObject**.

### โœ… `seatInfo` structure

"seatInfo": {
  "seat": {
    "defaultValue": {
      "language": "en-US",
      "value": "12A"
    }
  },
  "row": {
    "defaultValue": {
      "language": "en-US",
      "value": "R"
    }
  },
  "section": {
    "defaultValue": {
      "language": "en-US",
      "value": "Ringside"
    }
  },
  "gate": {
    "defaultValue": {
      "language": "en-US",
      "value": "Gate 1"
    }
  }
}

### ๐Ÿ‘€ Where to include this?
Inside your EventTicketObject payload when creating the object via Google Wallet API:

$passObject = [
  'id' => $objectId,
  'classId' => $classId,
  'state' => 'active',
  ...
  'seatInfo' => [
    'seat' => [
      'defaultValue' => [
        'language' => 'en-US',
        'value' => $order['seat_number'] ?? '12A'
      ]
    ],
    'row' => [
      'defaultValue' => [
        'language' => 'en-US',
        'value' => $order['seat_row'] ?? 'A'
      ]
    ],
    'section' => [
      'defaultValue' => [
        'language' => 'en-US',
        'value' => $order['seat_section'] ?? 'Ringside'
      ]
    ],
    'gate' => [
      'defaultValue' => [
        'language' => 'en-US',
        'value' => $order['gate'] ?? 'Main Gate'
      ]
    ]
  ],
];

### โ„น๏ธ Notes:
– All values (`seat`, `row`, `section`, `gate`) are optional.
– You can localize them with multiple languages if needed.
– These will be shown in the **ticket layout** if the template supports them.

Let me know if you want this added conditionally or need to debug layout visibility of this data.

Leave a Comment

Your email address will not be published. Required fields are marked *