Length limits on ID parameters
What's new
Every ID-shaped path and query parameter in the S2S API now declares maxLength: 32. This covers 31 parameter names across 105 operations, from the resource IDs in the path to the ID filters on the list endpoints.
This mirrors the 32-character limit declared on the webhook payloads on 2026.09.08.
Impact
The identifiers Aghanim issues are already 32 characters, so nothing about the accepted values changed. The limit is now visible in the spec, which means generated clients and validators enforce it, and a malformed ID fails before the request leaves your service instead of coming back as a 404.
Changes
| Resource | Change |
|---|---|
| Resource path parameters on 105 operations | achievement_id, campaign_id, coupon_id, creator_id, daily_reward_id, item_category_id, item_id, leaderboard_id, locale_id, loyalty_settings_id, member_id, news_id, order_id, page_id, price_template_id, segment_group_id, segment_id, store_id, store_item_id, store_promotion_id, subscription_id, translation_glossary_id, user_id, video_id, and webhook_id capped at 32 characters |
| get_items | category_id and rarity_id filters capped at 32 characters |
| get_coupons | category_id filter capped at 32 characters |
| get_creators | creator_tier_group_id filter capped at 32 characters |
| get_news_list | collection_id filter capped at 32 characters |
| get_orders | start_after_id cursor capped at 32 characters |
| get_pages | parent_id filter capped at 32 characters |
| get_payments | order_id filter capped at 32 characters |
| get_segments | segment_group_id filter capped at 32 characters |
| get_translation_glossaries | locale_id filter capped at 32 characters |
Upgrade
- No action required. This is a constraint the API already applied.
- Regenerate clients if you want the limit reflected in your generated types.
- If your own schema declares these columns as something shorter than 32 characters, the mismatch is now visible in the spec.
Need help?
Contact our integration team at [email protected]