Excerpt |
---|
Creates a new entity/account as a child of another entity in the Rubiq database, with fields specified in a contract between the calling application and the Rubiq API. The parent-child relationship between the entities must be previously established in Rubiq Cloud. |
Endpoint ID: | 1005 | ||||||||||||||||||
Method: |
| ||||||||||||||||||
URL: | /userentity/dp-keyid/{dpentity-keyid}/child/{contract-id} /userentity/ext-key/{ext-key}/{ext-type}/child/{contract-id}
| ||||||||||||||||||
dp-key | dialogportal™ master key entity-id | Rubiq entity ID that uniquely identifies account that will be the parent of the new child's parent entity | |||||||||||||||||
ext-key | External key that uniquely identifies account that will be the parent of the identifies the new child's parent entity | ||||||||||||||||||
ext-type | Type of external key | ||||||||||||||||||
contract-id | Identifies the type of child to create and the set of contract fields passed in the request body | ||||||||||||||||||
Request body: | JSON data with properties corresponding to the fields in the specified contract
| ||||||||||||||||||
| JSON data with key(s) and data for the newly created child entity. The result will always hold the Rubiq entity ID, and if the app making the request is configured to use a specific external key, this key is also included in the response.
| ||||||||||||||||||
Status codes: | 201 | Child was created with success | |||||||||||||||||
303 | Child already exists, redirected to “Get Account Data” | ||||||||||||||||||
400 | Request is valid but data validation failed |
...