Schema for the Continuous Compliance Engine API
Masking API (5.1.42)
- Mock serverhttps://help-api.delphix.com/_mock/continuous-compliance-engine/2025.2.0.0/cc-engine-apis-2025.2.0.0/profile-jobs
- https://help-api.delphix.com/masking/api/v5.1.42/profile-jobs
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://help-api.delphix.com/_mock/continuous-compliance-engine/2025.2.0.0/cc-engine-apis-2025.2.0.0/profile-jobs?page_number=1&page_size=0&environment_id=0' \
-H 'Authorization: YOUR_API_KEY_HERE'Success
{ "_pageInfo": { "numberOnPage": 0, "total": 0 }, "responseList": [ { … } ] }
The profile job to create
The name of the profile job. Once the profile job is created, this field cannot be changed.
The ID number of the profile set to be used during the profiling phase.
The ID of the ruleset that this profile job is targeting. Once the profile job is created, the underlying environment that is inferred from the ruleset will be unchangeable. That is, the job can only be updated to reference a ruleset that is in the same environment as the environment of the original ruleset.
The email address to send job status notifications to; note that the SMTP settings must be configured first to receive notifications.
The granularity with which the Masking Engine provides updates on the progress of the profile job. For instance, a feedbackSize of 50000 results in log updates whenever 50000 rows are processed during the profiling phase.
A description of the job.
The maximum amount of memory, in MB, that the profile job can consume during execution.
The minimum amount of memory, in MB, that the profile job can consume during execution.
This field determines whether the profile job, after creation, can be executed using a connector that is different from the underlying connector associated with the ruleset that this profile job is targeting.
This field controls the amount of parallelism that the profile job uses to extract out the data to be profiled. For instance, when profiling a database, specifying 5 input streams results in the profile job reading up to 5 database tables in parallel and then profiling those 5 streams of data in parallel. The higher the value of this field, the more potential parallelism there will be in the job, but the profile job will consume more memory. If the number of input streams exceeds the number of units being profiled (e.g. tables or files), then the excess streams will do nothing.
This field determines whether the profiler stops after it flags a field as sensitive or if it continues to scan for more sensitive patterns.
- Mock serverhttps://help-api.delphix.com/_mock/continuous-compliance-engine/2025.2.0.0/cc-engine-apis-2025.2.0.0/profile-jobs
- https://help-api.delphix.com/masking/api/v5.1.42/profile-jobs
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://help-api.delphix.com/_mock/continuous-compliance-engine/2025.2.0.0/cc-engine-apis-2025.2.0.0/profile-jobs \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-d '{
"jobName": "minimal_profile_job",
"profileSetId": 2,
"rulesetId": 7,
"jobDescription": "This example value illustrates the minimal set of fields required to create a ProfileJob. All other fields have default values. Refer to the extensive documentation on the ProfileJob object for reference on the other, optional fields."
}'Success
The ID number of the profile job. This field is auto-generated by the Masking Engine.
The name of the profile job. Once the profile job is created, this field cannot be changed.
The ID number of the profile set to be used during the profiling phase.
The ID of the ruleset that this profile job is targeting. Once the profile job is created, the underlying environment that is inferred from the ruleset will be unchangeable. That is, the job can only be updated to reference a ruleset that is in the same environment as the environment of the original ruleset.
The user that created the profile job. This field is auto-generated by the Masking Engine.
The time when the profile job was created. This field is auto-generated by the Masking Engine.
The email address to send job status notifications to; note that the SMTP settings must be configured first to receive notifications.
The granularity with which the Masking Engine provides updates on the progress of the profile job. For instance, a feedbackSize of 50000 results in log updates whenever 50000 rows are processed during the profiling phase.
A description of the job.
The maximum amount of memory, in MB, that the profile job can consume during execution.
The minimum amount of memory, in MB, that the profile job can consume during execution.
This field determines whether the profile job, after creation, can be executed using a connector that is different from the underlying connector associated with the ruleset that this profile job is targeting.
This field controls the amount of parallelism that the profile job uses to extract out the data to be profiled. For instance, when profiling a database, specifying 5 input streams results in the profile job reading up to 5 database tables in parallel and then profiling those 5 streams of data in parallel. The higher the value of this field, the more potential parallelism there will be in the job, but the profile job will consume more memory. If the number of input streams exceeds the number of units being profiled (e.g. tables or files), then the excess streams will do nothing.
This field determines whether the profiler stops after it flags a field as sensitive or if it continues to scan for more sensitive patterns.
{ "jobName": "minimal_profile_job", "profileSetId": 2, "rulesetId": 7, "jobDescription": "This example value illustrates the minimal set of fields required to create a ProfileJob. All other fields have default values. Refer to the extensive documentation on the ProfileJob object for reference on the other, optional fields." }
- Mock serverhttps://help-api.delphix.com/_mock/continuous-compliance-engine/2025.2.0.0/cc-engine-apis-2025.2.0.0/profile-jobs/{profileJobId}
- https://help-api.delphix.com/masking/api/v5.1.42/profile-jobs/{profileJobId}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://help-api.delphix.com/_mock/continuous-compliance-engine/2025.2.0.0/cc-engine-apis-2025.2.0.0/profile-jobs/{profileJobId}' \
-H 'Authorization: YOUR_API_KEY_HERE'Success
The ID number of the profile job. This field is auto-generated by the Masking Engine.
The name of the profile job. Once the profile job is created, this field cannot be changed.
The ID number of the profile set to be used during the profiling phase.
The ID of the ruleset that this profile job is targeting. Once the profile job is created, the underlying environment that is inferred from the ruleset will be unchangeable. That is, the job can only be updated to reference a ruleset that is in the same environment as the environment of the original ruleset.
The user that created the profile job. This field is auto-generated by the Masking Engine.
The time when the profile job was created. This field is auto-generated by the Masking Engine.
The email address to send job status notifications to; note that the SMTP settings must be configured first to receive notifications.
The granularity with which the Masking Engine provides updates on the progress of the profile job. For instance, a feedbackSize of 50000 results in log updates whenever 50000 rows are processed during the profiling phase.
A description of the job.
The maximum amount of memory, in MB, that the profile job can consume during execution.
The minimum amount of memory, in MB, that the profile job can consume during execution.
This field determines whether the profile job, after creation, can be executed using a connector that is different from the underlying connector associated with the ruleset that this profile job is targeting.
This field controls the amount of parallelism that the profile job uses to extract out the data to be profiled. For instance, when profiling a database, specifying 5 input streams results in the profile job reading up to 5 database tables in parallel and then profiling those 5 streams of data in parallel. The higher the value of this field, the more potential parallelism there will be in the job, but the profile job will consume more memory. If the number of input streams exceeds the number of units being profiled (e.g. tables or files), then the excess streams will do nothing.
This field determines whether the profiler stops after it flags a field as sensitive or if it continues to scan for more sensitive patterns.
{ "jobName": "minimal_profile_job", "profileSetId": 2, "rulesetId": 7, "jobDescription": "This example value illustrates the minimal set of fields required to create a ProfileJob. All other fields have default values. Refer to the extensive documentation on the ProfileJob object for reference on the other, optional fields." }
The updated profile job
The name of the profile job. Once the profile job is created, this field cannot be changed.
The ID number of the profile set to be used during the profiling phase.
The ID of the ruleset that this profile job is targeting. Once the profile job is created, the underlying environment that is inferred from the ruleset will be unchangeable. That is, the job can only be updated to reference a ruleset that is in the same environment as the environment of the original ruleset.
The email address to send job status notifications to; note that the SMTP settings must be configured first to receive notifications.
The granularity with which the Masking Engine provides updates on the progress of the profile job. For instance, a feedbackSize of 50000 results in log updates whenever 50000 rows are processed during the profiling phase.
A description of the job.
The maximum amount of memory, in MB, that the profile job can consume during execution.
The minimum amount of memory, in MB, that the profile job can consume during execution.
This field determines whether the profile job, after creation, can be executed using a connector that is different from the underlying connector associated with the ruleset that this profile job is targeting.
This field controls the amount of parallelism that the profile job uses to extract out the data to be profiled. For instance, when profiling a database, specifying 5 input streams results in the profile job reading up to 5 database tables in parallel and then profiling those 5 streams of data in parallel. The higher the value of this field, the more potential parallelism there will be in the job, but the profile job will consume more memory. If the number of input streams exceeds the number of units being profiled (e.g. tables or files), then the excess streams will do nothing.
This field determines whether the profiler stops after it flags a field as sensitive or if it continues to scan for more sensitive patterns.
- Mock serverhttps://help-api.delphix.com/_mock/continuous-compliance-engine/2025.2.0.0/cc-engine-apis-2025.2.0.0/profile-jobs/{profileJobId}
- https://help-api.delphix.com/masking/api/v5.1.42/profile-jobs/{profileJobId}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://help-api.delphix.com/_mock/continuous-compliance-engine/2025.2.0.0/cc-engine-apis-2025.2.0.0/profile-jobs/{profileJobId}' \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-d '{
"jobName": "minimal_profile_job",
"profileSetId": 2,
"rulesetId": 7,
"jobDescription": "This example value illustrates the minimal set of fields required to create a ProfileJob. All other fields have default values. Refer to the extensive documentation on the ProfileJob object for reference on the other, optional fields."
}'Success
The ID number of the profile job. This field is auto-generated by the Masking Engine.
The name of the profile job. Once the profile job is created, this field cannot be changed.
The ID number of the profile set to be used during the profiling phase.
The ID of the ruleset that this profile job is targeting. Once the profile job is created, the underlying environment that is inferred from the ruleset will be unchangeable. That is, the job can only be updated to reference a ruleset that is in the same environment as the environment of the original ruleset.
The user that created the profile job. This field is auto-generated by the Masking Engine.
The time when the profile job was created. This field is auto-generated by the Masking Engine.
The email address to send job status notifications to; note that the SMTP settings must be configured first to receive notifications.
The granularity with which the Masking Engine provides updates on the progress of the profile job. For instance, a feedbackSize of 50000 results in log updates whenever 50000 rows are processed during the profiling phase.
A description of the job.
The maximum amount of memory, in MB, that the profile job can consume during execution.
The minimum amount of memory, in MB, that the profile job can consume during execution.
This field determines whether the profile job, after creation, can be executed using a connector that is different from the underlying connector associated with the ruleset that this profile job is targeting.
This field controls the amount of parallelism that the profile job uses to extract out the data to be profiled. For instance, when profiling a database, specifying 5 input streams results in the profile job reading up to 5 database tables in parallel and then profiling those 5 streams of data in parallel. The higher the value of this field, the more potential parallelism there will be in the job, but the profile job will consume more memory. If the number of input streams exceeds the number of units being profiled (e.g. tables or files), then the excess streams will do nothing.
This field determines whether the profiler stops after it flags a field as sensitive or if it continues to scan for more sensitive patterns.
{ "jobName": "minimal_profile_job", "profileSetId": 2, "rulesetId": 7, "jobDescription": "This example value illustrates the minimal set of fields required to create a ProfileJob. All other fields have default values. Refer to the extensive documentation on the ProfileJob object for reference on the other, optional fields." }
- Mock serverhttps://help-api.delphix.com/_mock/continuous-compliance-engine/2025.2.0.0/cc-engine-apis-2025.2.0.0/profile-jobs/{profileJobId}
- https://help-api.delphix.com/masking/api/v5.1.42/profile-jobs/{profileJobId}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X DELETE \
'https://help-api.delphix.com/_mock/continuous-compliance-engine/2025.2.0.0/cc-engine-apis-2025.2.0.0/profile-jobs/{profileJobId}' \
-H 'Authorization: YOUR_API_KEY_HERE'