Configuring Connectors

Each connector needs to be configured prior to using it to set up a data connection. Depending on the implementation, a connector may offer the ability to be used as a source, destination or both. Each of these need to be configured explicitly. Following is an example for configuring a connector.

Example

Path	/v1/partner/connector/db69f718d3244495/config
Method	POST
Header	Content-Type: application/json Authorization: Bearer access token
Query Params	NONE
Body	{ "sourceConfig": { “api-key”: “AKIAVDSFGDFS23DSGF4355332DSGA”, “bucket-name”: “madconnect_aud_nke” }, "destinationConfig": { “api-key”: “AKIAVDSFGDFS23DSGF4355332DSGA”, “bucket-name”: “madconnect_aud_nke” } }

OAuth Setup

In cases where the source/destination platform supports OAuth, MAdConnect will return a URL for the OAuth setup. Using this URL the platform’s client can authenticate and thus provide the access credentials.