---
description: "Read order lines, attendee registration data, and check-in status."
group: "Resources"
order: 20
---

# Working with attendees

Read order lines, attendee registration data, and check-in status.

An attendee is represented by an `OrderLine`. A single order can contain multiple lines and multiple attendees. Keep the order line ID as the attendee key and its product relationship separately.

## List attendees {#list-attendees}

```curl
curl --user "$PAYDRO_EMAIL:$PAYDRO_PASSWORD" \
  --header 'Accept: application/json' \
  "$PAYDRO_ORIGIN/$EVENT_ID/order_lines/index/index.json"
```

The response is an array of `OrderLine` records containing names, email, product ID, timestamps, and company information where available. The standard event list uses `index` and returns 100 records per page. It applies the existing confirmed/invoiced order or reservation filters and omits cancelled credit records and package container products.

## Include check-in state {#include-check-in-state}

```curl
curl --user "$PAYDRO_EMAIL:$PAYDRO_PASSWORD" \
  --header 'Accept: application/json' \
  "$PAYDRO_ORIGIN/$EVENT_ID/order_lines/index/index.json?include=scan"
```

Add `include=scan` to request a numeric `scanned` flag. This read flag indicates an associated scan. To record attendance, use the authorized POST action in the [check-in guide](/en-us/docs/check-in.md).

## Retrieve registration fields {#retrieve-registration-fields}

`/{event_id}/order_lines/edit_data/{attendee_id}.json` returns `{ok: true, data: {...}}`. Read the attendee from `data.orderLine`, answers from `data.orderLine.answers`, and question definitions from `currentQuestions` and `historicalQuestions`. Registration questions vary by event and product. Match fields by ID and read their names when supplied.

## Bulk imports {#bulk-imports}

Compact attendee snapshots group rows by event, use abbreviated names, and cap each event at 10,000 rows. Treat the `deleted_items` delta list as removal IDs. Consult the synchronization guide for cancelled orders, weekly windows, and recovery.

## Manage registration {#manage-registration}

Use [attendee management](/en-us/docs/attendee-management.md) for contact/answer updates, eligible product changes, archived question actions and ticket resends. Each operation retains event ownership, order-state and validation checks.