ElectionDateType

AI-generated Key Takeaways

• Election date types are used for pre-election data and election results feeds, but not for officeholder feeds.

• The possible enumeration values for election date type are scheduled, snap, and bounded.

• scheduled indicates an election that is already scheduled, while snap indicates a snap election.

• bounded is used when election dates are uncertain but expected within a timeframe, with specific rules for interpreting StartDate and EndDate.

• bounded elections cannot have an EndDate in the past unless their DateStatus is postponed or canceled.

Note: This enumeration is the same for the pre-election data and election results feed types. It isn't used with officeholder feeds.

The following table lists the enumerations for election date type in the Election entity:

Value	Description
scheduled	When the election is already scheduled.
snap	When a snap election is called.
bounded	When the election dates are uncertain but expected within a given timeframe. For elections with this date type, the EndDate will be interpreted as "expected on-or-before", and StartDate will be interpreted as "expected on-or-after" if different from EndDate and ignored if the same. In other words, to specify only an "expected on-or-before" date, set both the StartDate and EndDate to that date, and to specify a full range during which the election could happen, set the StartDate to the earliest possible date and the EndDate to the latest possible date. Specifying only an "expected on-or-after" date is not possible. Note: bounded elections cannot have an EndDate in the past, unless they have a postponed or canceled DateStatus.