Shared Parameters in the API Connector are only added to a call if certain conditions are met — depending on the call type and whether existing parameters are already defined. If those conditions aren't satisfied, Shared Parameters are silently excluded, which can cause calls to behave unexpectedly.
What you might notice
Shared Parameters don't appear to be sent with certain API Connector calls
Calls behave differently than expected depending on how parameters are configured
Some calls include Shared Parameters and others don't, with no obvious reason why
When Shared Parameters are included
Shared Parameters are only added in these two cases:
GET or DELETE calls: Shared Parameters are added as QueryString parameters (e.g. ?key1=value1) only if at least one Parameter is already defined in the call.
POST, PUT, or PATCH calls with Body Type set to JSON: Shared Parameters are added to the JSON body as additional key-value pairs only if at least one Parameter is already defined.
Outside of these cases — including POST, PUT, or PATCH calls with Body Type set to form-data — Shared Parameters won't be added.
Workaround
If your call isn't picking up Shared Parameters, you have two options:
Add the parameters directly to the specific API Connector call instead of relying on Shared Parameters.
Ensure at least one parameter is defined in the call so that the conditions above are met.
For more detail on how Shared Parameters work, see the API Connector documentation.
Status
This behavior is documented and we don't have plans to change it at this time, as a fix could affect existing API setups. The workarounds above should cover most cases.