Integration attendee lists

Read assigned event attendees

GET /api/v1/integrations/ti-events/{id}/attendees

Read assigned users grouped by user and ticket, with optional ticket filtering. The pass owner is not used as the attendee identity. No pass activation, expiry, refund or check-in condition is applied.

Before you call

The selected resource must enable its ticket-event system. The event must exist, be active and belong to that resource; knowing an event ID alone is insufficient.

Use the existing resource public key and resource-scoped service-api-key headers. The account must be active and not suspended, with an active attached service-account user. The service_account role has a separate route allowance; the account must also have full_access or an explicit grant for this controller/action. An ordinary member token is insufficient. Root context bypasses the route ACL, but is not the example credential.

Service-account initialization can create or update a session, increment request counters, extend its expiry and record the request/response, even for GET. An invalid key can fall back to ordinary context resolution; no dedicated invalid-key response is guaranteed. See credential transport.

This action does not require that the service-account user own a pass or be assigned to it. Its account grant controls access to the resource-scoped integration action.

Request

Bodyless GET.

Result

HTTP 200 collection, with no nested user object. Assignment rows require a matching user and ticket. Items are grouped by user ID and ticket ID and ordered by the maximum pass creation time ascending; there is no stable tie-breaker.

An internal collection failure is logged and can return the default empty collection with total 0 and has_more false. An empty result is therefore not conclusive proof of no assignments. This read does not establish current pass usability, attendance or content access.

curl "${WALLKIT_API_BASE}/api/v1/integrations/ti-events/1001/attendees?limit=100&offset=0&tickets%5B%5D=2001" \
  -H "resource: ${RESOURCE_KEY}" \
  -H "service-api-key: ${SERVICE_API_KEY}"

const response = await fetch(`${process.env.WALLKIT_API_BASE}/api/v1/integrations/ti-events/1001/attendees?limit=100&offset=0&tickets%5B%5D=2001`, {
  method: "GET",
  headers: {"resource": process.env.RESOURCE_KEY, "service-api-key": process.env.SERVICE_API_KEY}
});
console.log(response.status, await response.json());

import os, json
from urllib.request import Request, urlopen
from urllib.error import HTTPError

request = Request(os.environ["WALLKIT_API_BASE"] + "/api/v1/integrations/ti-events/1001/attendees?limit=100&offset=0&tickets%5B%5D=2001",
    headers={'resource': os.environ["RESOURCE_KEY"], 'service-api-key': os.environ["SERVICE_API_KEY"]}, method="GET")
try:
    with urlopen(request) as response:
        print(response.status, json.load(response))
except HTTPError as error:
    print(error.code, json.load(error))

{
  "items": [
    {
      "email": "reader@example.com",
      "first_name": "Alex",
      "last_name": "Rivera",
      "ti_event_ticket_id": 2001
    }
  ],
  "total": 1,
  "limit": 100,
  "offset": 0,
  "has_more": false
}

{
  "items": [],
  "total": 0,
  "limit": 100,
  "offset": 0,
  "has_more": false
}