List my check-ins
Users
List my check-ins
GET
List my check-ins
Returns the authenticated member’s own check-ins, newest first. The
subject is resolved from the access token, so there is no member ID in
the path. Same shape as
Auth: OAuth access token with the
The
GET /check_ins,
scoped to the member.
Tasting note - This is the clean self-feed. To read check-ins for
a specific restaurant or location instead, use the filterable
GET /check_ins. Each row embeds the
full location (with its restaurant and neighborhood), so one call
renders a feed without follow-ups.read:checkins scope. A token
missing that scope returns 403 with error="insufficient_scope" in
the WWW-Authenticate header.
Example
Response
location object is returned in full (embedding its restaurant
and neighborhood), trimmed here for brevity.
Schema
| Field | Type | Notes |
|---|---|---|
check_ins | array | Each item is a check_in. See GET /check_ins for the full object. |
check_ins[].visit_number | integer | This member’s running visit count at this location, not global. |
check_ins[].created_at | ISO 8601 timestamp | Visit start. |
check_ins[].ended_at | ISO 8601 timestamp | Visit end, or null if ongoing. |
pagination | object | Standard pagination wrapper. next_page is null on the last page. |
See also
- Check-in feed: render a member’s history.
- Pagination + errors: paging and scope errors.