Remove a Recipe from a Community

This endpoint allows you to remove a recipe from a community.

Remove a Recipe

DELETE https://api.whisk.com/community/v2/{community_id}/recipes/{recipe_id}

You can use the following path parameters to remove a recipe from a particular community:

Path Parameters

Name	Type	Description
community_id	string	The community identifier. For example, 39d539c738eb47debfb1a6319d34235a.
recipe_id	string	The recipe identifier. For example, 101772a1db675504ef37b28e918643d571decf6ddb5.

Headers

Name	Type	Description
Authentication	string	User Access token containing community:write scope to authorize the API usage. For more information, see Authentication.

200 This is how a successful response looks.

{}

400 This failed response appears when error codes are found in the endpoint query.

{
  "error_code": "REAL_CODES_ARE_IN_ENDPOINT_DESCRIPTION",
  "message": "Additional details about error are not static and can be changed"
}

401 This failed response appears due to API authentication failure. The possible error codes that may appear are: auth.tokenNotFound , auth.tokenExpired, auth.tokenInvalid, auth.tokenRequired.

{
  "code": "auth.tokenNotFound"
}

500 This failed response appears when something is not right on Whisk's end. Please send a message to [email protected], and be sure to include both the Request and Response data. We’ll get back to you soon.

This is unexpected response, something is wrong on our side, please contact: [email protected]

Sample Request and Response

Curl Request

curl -X DELETE "https://api.whisk.com/community/v2/39d539c738eb47debfb1a6319d34235a/recipes/101772a1db675504ef37b28e918643d571decf6ddb5"
    -H "Accept: application/json" 
    -H "Authorization: Bearer <YOUR-API-ACCESS-KEY>"

Whisk allows you to discover and understand its API capabilities on the Swagger interface with the ability to try out the API calls directly in your browser. You can call this endpoint here.

Response

{}