Skip to main content
DELETE
/
api
/
series
/
{showId}
Delete Series
curl --request DELETE \
  --url https://api.example.com/api/series/{showId} \
  --header 'X-API-Token: <x-api-token>'
{
  "200": {},
  "204": {},
  "401": {},
  "404": {},
  "500": {},
  "success": true,
  "message": "<string>",
  "_id": "<string>"
}

​
Overview

This endpoint permanently deletes a series from the MediaStream platform. This action will also affect all associated seasons and episodes.
This action is irreversible. Deleting a series will remove all associated seasons, episodes, and metadata. Make sure you want to permanently delete this content before proceeding.

​
Authentication

This endpoint requires MediaStream API authentication using the X-API-Token header.
​
X-API-Token
string
required
Your MediaStream API authentication token
​
Accept
string
default:"application/json"
Content type for the response

​
Path Parameters

​
showId
string
required
The unique identifier of the series to delete

​
Response

The response structure depends on the MediaStream platform API. Typically returns a success confirmation or the deleted series object.
​
success
boolean
Indicates whether the deletion was successful
​
message
string
Confirmation message about the deletion
​
_id
string
The ID of the deleted series

​
Example Request

curl -X DELETE "https://your-domain.com/api/series/507f1f77bcf86cd799439011" \
  -H "X-API-Token: your_api_token" \
  -H "Accept: application/json"

​
Example Response

{
  "success": true,
  "message": "Series deleted successfully",
  "_id": "507f1f77bcf86cd799439011"
}

​
Response Status Codes

​
200
Success
Series successfully deleted
​
204
No Content
Series successfully deleted (no content returned)
​
401
Unauthorized
Invalid or missing API token
​
404
Not Found
Series with the specified ID does not exist or has already been deleted
​
500
Internal Server Error
An error occurred while deleting the series from MediaStream

​
Cascade Effects

When a series is deleted, the following related data is typically affected:
  • Seasons: All seasons associated with the series
  • Episodes: All episodes in all seasons of the series
  • Images: All images associated with the series
  • Metadata: All metadata and custom fields associated with the series
The exact cascade behavior depends on the MediaStream platform configuration. Some platforms may soft-delete content or move it to a trash/archive system rather than permanently deleting it.

​
Implementation Notes

  • The endpoint proxies the delete request to the MediaStream platform API at /show/{showId}
  • Series are internally referred to as “shows” in the route parameters and backend code
  • The Laravel route uses the destroy method which corresponds to the DELETE HTTP method
  • All deletion logic is handled by the MediaStream platform

​
Best Practices

  • Always confirm with the user before deleting a series
  • Consider implementing a soft-delete or archive feature if you need to recover deleted content
  • Log deletion events for audit purposes
  • Check for related content (seasons, episodes) and warn users before deletion
  • Implement proper authorization to ensure only authorized users can delete series
  • Consider rate limiting to prevent accidental mass deletions

Build docs developers (and LLMs) love

Get started for freeTalk to us