Section-scoped token values when building document bundles via API
When using the sections/uploads endpoint to build a bundled document from multiple templates, token (variable) values passed in the second call are applied globally across the entire document - overwriting same-named token values from the first call.
Fields already support section-level scoping via the mergefieldscope=upload query parameter, but tokens do not. This creates a hard limitation for dynamic bundling use cases where templates are selected at runtime (e.g. from CRM data) and cannot be pre-configured with unique token names per bundle combination.
The current workaround — converting shared tokens to fields and using mergefieldscope=upload - requires modifying every template involved in bundling, which is impractical when any template may be paired with any other dynamically.
Requested behavior: Extend section-level scoping to tokens in the sections/uploads endpoint, either by supporting mergefieldscope=upload for the tokens array, or by introducing an equivalent mechanism that allows token values to be scoped to a specific section without requiring globally unique token names across templates.
Anonymous
shared this idea