DELETE
/schedules/{scheduleId}Delete Schedule
Standard API endpoint for Delete Schedule.
DELETE
/schedules/{scheduleId}Mandatory Fields
- scheduleId
Note
For any technical assistance or feature requests, please contact our API support team.
Important Notes
- Always use HTTPS for API requests.
- Access tokens are valid for a limited time and should be refreshed periodically.
- Rate limiting applies to all endpoints to ensure system stability.
Parameter Details
| Name | In | Type | Required | Description |
|---|---|---|---|---|
scheduleId | path | integer | Required | Unique identifier for the schedule to delete. |
- All parameters should be formatted according to the types specified in the table above.
Responses
| Status | Meaning | Description | Schema |
|---|---|---|---|
| 204 | No Content | No Content - Schedule deleted successfully, no response body. | None |
| 400 | Bad Request | Bad Request | None |
| 401 | Unauthorized | Unauthorized | None |
| 403 | Forbidden | Forbidden - Access denied | None |
| 404 | Not Found | Schedule not found | None |
| 429 | Too Many Requests | Too Many Requests | None |
| 500 | Internal Server Error | Internal Server Error | None |
Response Notes
The response will include a status field indicating success or failure, along with the requested data or relevant error messages. Standard HTTP status codes are used to indicate the outcome of the request.
Example Request
# You can also use wget
curl -X DELETE /schedules/{scheduleId} \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'Authorization: Bearer {access-token}'
Need Support?
Our team is here to help you integrate and make the most of our APIs. Get in touch for technical support, custom solutions, or any questions.