Actions36
- List Actions
- Participant Actions
- Passport Actions
- Profile Actions
- Punch Pass Actions
Participant → Get Many
AI-generatedOverview
This node operation fetches multiple participant records from the OneTap API. It supports returning all participants or a limited subset with pagination controls. Users can filter participants based on various criteria such as check-in/check-out dates, status, IP address, list IDs, profile IDs, and sorting options. This operation is useful for scenarios where you need to retrieve participant data for reporting, analysis, or integration with other systems.
Use Case Examples
- Retrieve all participants who checked in after a specific date.
- Fetch up to 50 participants filtered by a specific list ID and sorted by check-in date.
- Get participants who are currently checked in and filter by IP address.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all participant results or only up to a given limit. |
| Limit | Maximum number of participant results to return when not returning all. |
| Skip | Number of participants to skip for pagination purposes. |
| Additional Fields | Optional filters and sorting options to refine the participant query, including date filters, check-in/out status, IP address, list/profile IDs, search query, and sorting preferences. |
Output
JSON
json- Participant data object returned from the OneTap API, containing participant details matching the query parameters.
Dependencies
- OneTap API authentication credential
Troubleshooting
- Common issues include API authentication failures, which can be resolved by verifying the API key credential.
- Incorrect date formats in filters may cause errors; ensure dates are in valid ISO format or timestamps.
- Pagination parameters (limit and skip) must be positive integers; invalid values may cause request failures.
- If no participants are returned, verify that the filter criteria are correct and that participants exist matching those filters.