Loading…
Represents a user's subscription to a gym plan, including expiration, available sessions, and check-ins.
| Field | Type | Description | Example |
|---|---|---|---|
| id | int | Unique identifier for the subscription | 123 |
| user_id | int | ID of the user | 789 |
| user | object | User resource object | { ... } |
| gym_plan | object | Gym plan resource object. On the two list endpoints it carries gym ({id, name, user_id}); single-subscription responses omit it |
| { ... } |
| expires_at | string|null | Expiration date (YYYY-MM-DD). null means the membership never expires: it is what a plan with no duration_days sells. Before 2026-10-17 such plans wrongly sold a membership expiring on the purchase date, and a null value rendered as "" | "2025-01-01" |
| available_sessions_count | int|null | Sessions left. Every check-in (REST, QR or MCP) uses one, and deleting that check-in gives it back (check-ins recorded before 2026-10-20 spent none and refund none). At 0 check-in is refused. null means unlimited and never changes | 16 |
| checkins_count | int | Number of check-ins on this subscription (the true total, even when checkins is capped) | 14 |
| checkins | array | Deprecated. List of check-in resources. Use checkins_count, or GET /gyms/{gym-id}/subscriptions/{subscription-id}/checkins, instead: oldest first (the last element is the newest check-in). List responses (GET /gyms/my-subscriptions and the gym's subscription list) embed only the latest 50 check-ins per subscription; single-subscription responses (create, update, subscribe) still embed all of them. The array will be removed once no released client reads it. | [ { ... }, ... ] |
{
"id": 123,
"user_id": 789,
"gym_plan": { /* gym plan resource */ },
"expires_at": "2025-01-01",
"available_sessions_count": 16,
"checkins_count": 14,
"checkins": [ { /* gym subscription checkin resource */ } ]
}
For schemas, see Gym Plan Resource, User Resource and Gym Subscription Check-in Resource.