Basic Usage
Fetch all members using the paginatedfetchAll method:
Pagination
Cursor-Based Pagination
Use
nextPageToken for cursor-based pagination (recommended for large datasets):Field Expansion
By default, only basic member information is returned. Use theexpanded parameter to include additional related data:
Fetching a Single Member
- By Member ID
- With Expanded Fields
Fetch a specific member using their type-safe
MemberID:Working with Member Data
Accessing Basic Information
Filtering Members
Error Handling
Always handle potential errors when fetching member data:Member ID Validation
The SDK uses type-safeMemberID for validation:
Valid Member IDs
Valid Member IDs
Member IDs must start with âTKTâ (case-insensitive) and are automatically normalized:
Invalid Member IDs
Invalid Member IDs
Invalid formats return
nil:Response Metadata
Access pagination metadata from the response:Best Practices
Use Pagination
Always use pagination for large datasets to avoid memory issues and improve performance.
Expand Selectively
Only expand fields you need to reduce response size and improve performance.
Handle Errors
Always wrap fetch calls in do-catch blocks to handle network and validation errors.
Validate IDs
Use
MemberID type for compile-time safety and automatic validation.Next Steps
Working with Families
Learn how to track and manage family relationships
Managing Seekers
Learn how to manage visitors and seekers
