Excerpt |
---|
Creates a new entity/user account in the Rubiq database with fields specified in a contract between the calling application and the Rubiq platform. A unique Rubiq entity ID is automatically assigned to the new entity, and optionally a key with an external type. |
Endpoint ID: | 1001 | |||||||
Method |
| |||||||
URL: | / |
...
entity/{contract-id} |
...
contract-id | Identifies the set of contract fields passed in the request body. If omitted, the default contract for the particular app is used. | ||||||
Request body: | JSON data with properties corresponding to the fields in the specified contract
| ||||||
| JSON data with key(s) for the newly created account and data for the account. 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 | Account was created with success |
...
303 | Account already exists |
...
...
Contributors
...
400 | Request is valid but data validation failed |
Recent activity
Change History |
---|
In case SMS verification is enabled, the following sub codes may be returned:
|