Length limits on ID fields
What's new
Every ID-shaped string in the webhook payloads now declares maxLength: 32. This covers the envelope fields event_id, game_id, and transaction_id on all 48 events, the context identifiers (context.order.id, context.daily_reward.id, context.loyalty_program.id, context.progression_program.id, context.rolling_offer.id, context.order.virtual_currency.id, context.order.coupons[].id, and context.order.rewards.available[].virtual_currency_id), and the identifiers inside event_data — order, user, company, game, item, coupon, and nested item IDs.
Impact
The values themselves have not changed. Aghanim already sent 32-character identifiers; the specs just say so now, which means generated clients and validators pick the limit up. If your code declares these columns or fields as something shorter, that mismatch is now visible in the spec rather than only at runtime.
Changes
| Resource | Change |
|---|---|
| All events | event_id, game_id, and transaction_id capped at 32 characters |
| All events | context object identifiers for orders, coupons, virtual currencies, daily rewards, loyalty and progression programs, and rolling offers capped at 32 characters |
| order events, payment events, item.add, item.remove, coupon.redeemed, store.get, subscription events, and others | event_data identifiers — id, order_id, user_id, company_id, game_id, item_id, and nested item and coupon IDs — capped at 32 characters |
Upgrade
- No action required. This is a constraint the payloads already satisfied.
- Regenerate clients if you want the limit reflected in your generated types.
Need help?
Contact our integration team at [email protected]