Filter event-registration API results by updated date

Use the supported start and optional end parameters with time_field=updated_at. For example, append start=1779193772&time_field=updated_at to the appropriate event-registration request, preserving its other filters and authentication. An updated_at parameter by itself is not the date-filter parameter in this API.

Timestamps are Unix seconds. The lower comparison is inclusive (updated_at >= start), and the optional upper comparison is inclusive (updated_at <= end). Other supported time fields are created_at, completed_at, captured_at and deposited_at. Payment capture/deposit filtering joins the corresponding payment/deposit records, so it has different scope from registration modification.

A registration created months earlier can still match a recent updated_at range. Inspect the timestamp being filtered before treating the response as incorrect. For a specific discrepancy collect the redacted request, response record ID and timestamps; do not include API credentials. Deployment/version must match the integration being tested.

Default timestamp field

Missing, null or unrecognized time_field selects event_registrations.updated_at in the query; it does not disable time filtering. start supplies an inclusive lower bound and end an optional inclusive upper bound in Unix seconds. If start is omitted the implementation coerces it to epoch0. Other state/event/payment filters still apply. Specify time_field explicitly for integrations so the intended timestamp is clear.

Event API payment fields versus Gifts API

Do not map the field names as exact equivalents. In event registration payment, type is the processor label (the event paths use Stripe or PayPal), while payment_method is the processor record’s subtype: Stripe returns its stored payment_method_subtype and PayPal returns PayPal or Venmo. These values can be absent when no payment exists and the Stripe subtype is provider-supplied, not a fixed list of values. Gifts card_type uses the payment subtype display with a stored cc_type fallback; Gifts payment_method is the contribution’s payment-method value. Preserve processor and subtype separately and handle null/unknown future subtype values.