در حال بارگذاری…
Deletes a check-in record from a gym subscription.
| Permission | Description |
|---|---|
gym_subscription_checkins.delete | Delete check-ins for your own gyms |
gym_subscription_checkins.delete_any | Delete check-ins for any gym |
| Name | Type | Required | Description | Example |
|---|---|---|---|---|
| gym-id |
| int |
| Yes |
| ID of the gym |
| 123 |
| subscription-id | int | Yes | ID of the subscription | 456 |
| checkin-id | int | Yes | ID of the check-in | 789 |
DELETE /api/v1/gyms/123/subscriptions/delete-checkin/456/789
Authorization: Bearer {token}
Despite the 204, this endpoint does return a JSON body: a localized confirmation message.
HTTP defines 204 as bodyless, so some clients and proxies discard it; treat the body as informational,
not something to depend on.
{
"message": "Gym subscription check-in deleted successfully."
}
Localized from messages.gyms.subscriptions.checkins.deleted_successfully (fa: “چکاین اشتراک باشگاه با موفقیت حذف شد.”).
Deleting a check-in reverses it: if the check-in spent one of the membership's sessions, that session is added back
to its available_sessions_count (an unlimited, null count stays null). A check-in recorded before check-in
started spending sessions (2026-10-20) never took one, so deleting it refunds nothing.
| Status | Description | Reference |
|---|---|---|
| 404 | Not found (invalid gym, subscription, or check-in) | |
| 401 | Unauthorized | Authentication error |
| 403 | Forbidden (no permission) | Permission error |