Graph node and page block IDs limited to 32 characters
What's new
The 32-character cap on resource-reference ID request fields now covers graph action nodes and page blocks. It applies to fields such as item_id, store_id, store_item_id, page_id, category_id, category_template_id, collection_id, leaderboard_id, news_id, achievement_id, segment_id, program_id, the offer IDs (pick_one_offer_id, piggy_bank_offer_id, range_offer_id, rolling_offer_id, sequential_offer_id), and the fallback_* variants.
This extends the cap introduced on catalog, store, and promotion endpoints to the graph and layout payloads that were still unconstrained.
Impact
An ID longer than 32 characters in any of these fields is now rejected by validation. Aghanim resource IDs are already 32 characters or shorter, so callers passing valid IDs are unaffected.
Changes
| Resource | Change |
|---|---|
| create_campaign, update_campaign, update_campaign_graph | ID fields on every graph action node capped at 32 characters — AddPageBlockNode, AddStoreNode, AddToSegmentNode, AddUserAchievementNode, CreateCouponNode, CreateItemBannerActionNode, CreateUserStoreSettingsNode, CreateVirtualSKUNode, ItemAddNode, ItemCategorySortNode, and the email, push, popup, PWA, and webhook action nodes |
| create_campaign, update_campaign | Custom-attribute profile_display.card_template_id and run_for_subscription_id capped at 32 characters |
| bulk_update_campaigns | id request field capped at 32 characters |
| create_page, update_page, bulk_update_page | ID fields on page blocks capped at 32 characters — CarouselBlock, DynamicBlock (including its graph rules), FeaturedItemBlock, FeaturedNewsBlock, FeaturedPageBlock, FullNewsBlock, LatestPagesBlock, LeaderboardCardBlock, LeaderboardFullBlock, LimitedStoreBannerBlock, StoreBlock, and the offer blocks |
| bulk_update_page, bulk_delete_page | id request field capped at 32 characters |
| update_segment_group | ID fields on every graph action node capped at 32 characters, matching the campaign graph |
Upgrade
- No action required if you send standard Aghanim resource IDs. If you generate or forward IDs from another system, ensure they do not exceed 32 characters.
Need help?
Contact our integration team at [email protected]