Some external data providers require information that's not available in the External Data Context.

To pass additional data to the External Data Component configuration, add the key-value pairs URL-encoded to the tn_edc_parameters.

Usage

Consider an integration where fictional session & customer id's need to be passed to the external data provider:

• sessionId: 1Aed12fdef
• customerId: 12344:

These values should be formatted like normal URL parameters:

sessionid=Aed12fdef&customerid=1234

The compound value should then be URL encoded and passed to the tn_edc_parameters:

tn_edc_parameters=sessionid%3DAed12fdef%26customerid%3D1234

Which results in the full example:

curl --request GET \
     --url 'https://gateway.tweakwisenavigator.com/navigation/{instancekey}?tn_cid=1001&tn_edc_parameters=session%3DAed12fdef%26beacon%3DAed12fdef_item12344' \
     --header 'TWN-Source: Tweakwise API docs' \
     --header 'accept: application/json'

The individual parameters can then be used in the Builder Configuration mapping step, using $.extraParameters: