Delete ALL monitoring records for a professional.
Utilizing [professionalId] and [product], delete the records pertaining to a professional.
Endpoint:
HTTP Method: DELETE
Path: /v2/monitoring
Server URL: https://api.propelus.com
Source: https://propelus.com/developer/monitoring/DeleteProfessionalMonitoring
Authentication
Two header-based authentication methods are required:
| Header | Type | In | Description |
| x-api-key | token | header | API key credential |
| x-client-id | token | header | Client identifier credential |
Query Parameters
| Parameter | Type | Required | Description |
| professionalId | string (UUID) | Yes | Unique identifier for the professional. |
| product | string | Yes | Monitoring product to delete. Allowed values: "credentialVerification" | "adverseCheckEssentials" | "adverseCheckPro". |
Example Request — JSON
fetch("https://api.propelus.com/v2/monitoring?professionalId=628fc8e2-ee7e-4779-9eb7-d980e7a92f3a&product=credentialVerification", {
method: "DELETE",
headers: {
"x-api-key": "<your-api-key>",
"x-client-id": "<your-client-id>"
}
})Example Request — cURL
curl -X DELETE "https://api.propelus.com/v2/monitoring?professionalId=628fc8e2-ee7e-4779-9eb7-d980e7a92f3a&product=credentialVerification" \
-H "x-api-key: <your-api-key>" \
-H "x-client-id: <your-client-id>"Responses
200 — Success
{
"status": 200,
"code": "deleted",
"detail": "string"
}Error Responses
Standardized error bodies. Validation-style errors include an errors array; each item contains detail, pointer, parameter, header, and code: https://propelus.com/developer/monitoring/DeleteProfessionalMonitoring#response-body
400 — Bad Request
401 — Unauthorized
403 — Forbidden
404 — Not Found
4XX — Client Error
5XX — Server Error