Location attention

A thin aggregate for owner dashboards and automations — the same signals Admin → Overview surfaces for “what needs attention.” Requires the summary scope.

GET /api/v2/locations/attention

Pass location_id as a query parameter.

curl

curl "https://app.<your-domain>/api/v2/locations/attention?location_id=loc_1" \
  -H "Authorization: Bearer ktly_<your-token>"

Query parameters

Parameter	Required	Notes
location_id	yes	Must match the API client’s location

Response (200)

{
  "ok": true,
  "location_id": "loc_1",
  "pending_refund_reversals": 3,
  "pending_refund_reversals_preview": [
    {
      "id": "rev_abc123",
      "status": "pending",
      "location_id": "loc_1",
      "contact_id": "kotally-contact-uuid",
      "entitlement_id": "kotally-entitlement-uuid",
      "granted_credits": 10,
      "suggested_credits": 10,
      "created_at": "2026-05-01T12:00:00.000Z"
    }
  ],
  "active_members_with_credits": 42,
  "generated_at": "2026-05-01T12:00:00.000Z"
}

Response fields

Field	Type	Notes
pending_refund_reversals	integer	Count of items awaiting apply/dismiss
pending_refund_reversals_preview	array	Up to 5 pending reversals (same shape as refund reversals)
active_members_with_credits	integer	Members with available credits at this location
generated_at	string	ISO 8601 timestamp when the snapshot was built

Use GET /api/v2/refund-reversals for the full pending queue and apply/dismiss decisions. Resolve contact_id values via GET /api/v2/contacts/{id} using the member’s external_contact_id.