Task Status Rejection
| Request |
|
| Description |
Allows a customer to reject a scheduled task or a group of tasks with the same alternativeId. Only tasks scheduled from the same day on, having a possible status transition to the targeted status are rejected. If the status transition to the target status is of type unplan, the tasks are unplanned, otherwise only a no-action transition is possible. |
| URL |
/rs/v1/customer/task/reject |
| Method |
POST |
| Content-Type |
application/x-www-form-urlencoded |
| Response Type |
No body — HTTP status code only |
| Form Parameter |
Datatype |
Required |
Description |
configId |
Integer |
Yes |
The identifier of the configuration. |
taskId |
String |
Yes |
The external identifier of the task. |
status |
String |
Yes |
The target status code after rejection. |
authentication |
String |
Yes |
Authentication token UUID from the email link. |
message |
String |
No |
Free-text message from the customer. Stored as a task note and triggers a notification email. |
Response Codes
| Code |
Meaning |
| 200 |
Rejection registered successfully. |
| 500 |
Server error. |
The endpoint returns only an HTTP status code — no response body. The caller is responsible for mapping the status code to a user-facing message. This is typically handled by the respond form template.
This endpoint is normally called by the JavaScript in the appointmentRespondForm template, not directly from an email link. Direct email links open the /respond page first, which then POSTs to this endpoint.
Sample Call
POST /omdservices/rs/v1/customer/task/reject
Content-Type: application/x-www-form-urlencoded
configId=16168276&taskId=AU-2022-46069_Weissach-282&status=IP-R&authentication=fe417f2e-be72-476d-955e-8db2c98f0463