Excerpt |
---|
Connects an entity/account to a track in dialogportal™
|
Endpoint ID: | 1007 | |||||||||||||
Method: |
| |||||||||||||
URL: | /userentity/dp-keyid/{dpentity-keyid}/tracks/{track-id} /userentity/ext-key/{ext-key}/{ext-type}/tracks/{track-id} | |||||||||||||
dp-key | dialogportal™ master key entity-id | Rubiq entity ID that uniquely identifies an account to connect with specified track | ||||||||||||
ext-key | External key that uniquely identifies an account to connect with specified track | |||||||||||||
ext-type | Type of external key | |||||||||||||
track-id | ID of track to connect account with | |||||||||||||
Request body: | None | |||||||||||||
| JSON data with information about the newly created connection
| title | Example – Account with dialogportal™ master key 12345 was just successfully connected to track with 397:
---|
{
" |
trackID": 397,
"name": "Name of track",
" |
connection": |
true
} |
Connection created successfully
Account is already connected to the specified track
Account was not found or track was not found.
The following sub codes may be returned:
404.1 | User not found |
404.2 | External user could not be found |
404.4 | Track not found |
...