Post data using field UUIDs to a specific dataset. Data will be processed according to Governance Rules defined in the related dataset (template in The Data Standards Cloud UI). If any data fails when tested against Governance Rules, the entire dataset will be moved into the draft/pending state, and no attached integrations will be run. If no data fails, integrations will be executed as defined in the dataset (template in The Data Standards Cloud UI). This endpoint returns a transactionUuid, which can be used to retrieve the submission status and results. Note: the current implementation allows a max of 1,000 rows per request.
POST Data to a specific dataset
To get the UUIDs to be used as headers you can call one of the following endpoints:
Post data to a specific dataset. Data will be processed according to Governance Rules defined in the related dataset (template in The Data Standards Cloud UI). If any data fails when tested against Governance Rules, the entire dataset will be moved into the draft/pending state, and no attached integrations will be run. If no data fails, integrations will be executed as defined in the dataset (template in The Data Standards Cloud UI).
This endpoint returns a transactionUuid, which can be used to retrieve the submission status and results.
Note: the current implementation allows a max of 1,000 rows per request.
Updating data for a specific dataset
Include the Claravine Id UUID in your request fieldUuids to overwrite a row. By adding a row's CVID that row will replace the previous row in the template's data. You may not add rows and update rows in the same submission.
Static FieldsStatic fields can also be updated through the API. To keep values for types such as random, autonumber, or pattern, resubmit them with your update.