Delete a pet profile
DELETE
/pet-profiles/{pet_profile_id}Delete a pet profile by ID. Deletion is a soft delete: after deletion the profile can no longer be retrieved, updated, or deleted by the current user, and its extension records become unreadable as well.
Request URL
text
DELETE https://open-api.habitaxx.com/v1/ms-ai-fast/pet-profiles/44Request headers
http
Authorization: Bearer <ACCESS_TOKEN>Path parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
pet_profile_id | integer | Yes | ID of the pet profile to delete. |
Request body
None. The record ID is already part of the URL path; do not send a JSON request body.
Response example
json
{
"code": 200,
"message": "success",
"data": {
"id": 44
}
}Response fields
| Field | Type | Description |
|---|---|---|
id | integer | ID of the deleted pet profile. |
Notes
- Calling the detail, update, or delete endpoint again with the same ID after deletion returns an error of the "profile not found or no permission" kind.
- Historical consultation sessions and reports that involved this profile do not disappear when the profile is deleted; they can still be queried by session ID.
- Deletion is an irreversible business action; before calling it, have the user confirm once more in the interface.