Store sorting and payment risk nodes removed

What's new

Eight graph node types are gone from the S2S API, along with the SortStoreType enum they used:

• Store nodes — AddStoreNode, SortStoreItemsNode, ItemCategorySortNode.
• Payment risk nodes — DeclinePaymentNode, Require3DSNode, RequirePennyDropNode, BanUserNode, BatchBanUserNode.

The payment risk set is the one added on 2026.08.20 and extended with the penny drop node on 2026.08.26; ItemCategorySortNode dates to 2026.07.20. None of them appear in any graph's node union anymore, and their schemas are no longer in components.

Impact

Fraud and store-ordering rules can no longer be expressed as graph nodes through this API. A payload carrying one of these model_type values is now rejected.

Changes

Resource	Change
create_campaign, update_campaign	Removed the eight node types from the graph.nodes discriminator and oneOf
get_campaign_graph, update_campaign_graph	Removed the eight node types from the graph nodes discriminator and oneOf
update_segment_group	Removed the eight node types from the graph.nodes discriminator and oneOf
get_pages, get_page, create_page, update_page, bulk_update_page, translate_page	Removed the eight node types from the DynamicBlock.graph_rules.nodes discriminator and oneOf
Components	Removed the AddStoreNode, SortStoreItemsNode, ItemCategorySortNode, DeclinePaymentNode, Require3DSNode, RequirePennyDropNode, BanUserNode, and BatchBanUserNode schemas, and the SortStoreType enum

Upgrade

• Drop these nodes from any graph you send. Sending one now fails validation instead of being accepted.
• Regenerate clients so the removed models and the SortStoreType enum stop appearing in your generated code.
• The narrowing that came with this removal is described in Graphs get a schema per context.

Need help?
Contact our integration team at integration@aghanim.com