Bulk Update Support for Extension Settings API

How: Enhance the existing PUT /api/v1.0.0/extensions/{extensionId}/settings endpoint to support bulk updates by accepting an array of key-value pairs in a single request.

This will allow multiple settings to be configured in one API call instead of individual requests per key.

Why: The current API design supports updating only one setting per request, which creates scalability challenges when managing multiple extensions and environments.

• Leads to repetitive API calls

• Increases execution time and complexity

• Introduces higher risk of manual/configuration errors

For Who: Implementation partners and system integrators

Developers managing multi-environment deployments (STAGE → PROD)

Teams working on large-scale PIM implementations with multiple extensions

Impact: ~80–90% reduction in configuration effort for extension setup

Enables complete extension provisioning in 2 API calls (create + configure)

Improves deployment speed and consistency across environments

Reduces operational overhead and error rates

Enhances platform usability for enterprise-scale implementations

Additional context:

Saves significant manual effort (e.g., 40+ extensions × multiple settings each)

Improves developer productivity and partner experience

High impact with low-to-moderate implementation effort (API enhancement only)

Currently, partners can automate extension creation via API, but settings must be applied one at a time, which becomes impractical at scale.
In real scenarios (e.g., ~40 extensions), this results in hundreds of API calls or manual configurations.

Bulk update capability would enable seamless environment replication, reduce onboarding time, and improve overall efficiency of PIM implementations.