Delete Recipe Serving
Delete a serving by ID.
The serving is excluded from listRecipeServings but is retained for audit compliance. Returns 204 No Content on success.
On versions declaring the recipe_versioning capability, the
response carries an ETag header set to the new Version ULID so
clients can pass it back as If-Match on the next mutation —
204 has no body to carry the field.
Path Parameters
Serving ID
Header Parameters
Optimistic-concurrency token. Pass the version_id returned by the previous mutation (or by GET /recipes/{id}/versions) so the server can reject the request when another writer has advanced the recipe in the meantime. A mismatch surfaces HTTP 412 with the current version_id in the response body so the client can decide whether to retry, merge, or surface the conflict to the user. Only consumed on API versions that declare the recipe_versioning capability — older versions ignore the header.
Response Body
application/json
curl -X DELETE "https://loading/studio/recipes/string/servings/string"{
"detail": [
{
"loc": [
"string"
],
"msg": "string",
"type": "string",
"input": null,
"ctx": {}
}
]
}