Add or update the external keys associated with the destinations of an Interactions API key provisioned to your app.

An Interactions API key can be associated with one external API key per destination.
Tech partners can associate an external API key with an interactions key provisioned to their app only
if the data owner included an external API key-eligible destination (ex. VAN), and has not already
specified an external API key for the destination.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
int32
required

The ID of your root workspace

uuid
required

The ID of your movement app

int32
required

The ID of the API key.

Body Params

A DTO including the external keys you want to associate with the Interactions API key

A wrapper class for the external API keys to be associated with an Interactions API key's destination.

destinations
array of objects

The list of destinations to update. This will not change the set of destinations associated with the
Interactions API key, but will update the External API Keys associated with each destination.

destinations
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Responses

400

The request is invalid, or the interactions API key's destination is already associated
with an external API key owned by the Interactions API key's owner workspace

404

App, API key, or destination not found

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
text/plain
application/json
text/json