Elections API v3.2 Release Notes
|
|
|
|
Updates to Switching to Certified Data
Using the resultsType=b parameter in the Elections request allows you to switch to certified data as it becomes available without having to change from resultsType=l to resultsType=c to get certified results.
Previously, when the resultsType=b and votetypes=true parameters were specified in the Elections request, the response included only certified cumulative results, but no vote type data because certified data is currently not available for vote by type.
Starting Feb. 12, 2026, you will receive a blend of certified cumulative data and live vote type data when you specify resultsType=b and votetypes=true in the request. The response also includes new fields to indicate the source (certified or live) for cumulative results and each vote type if applicable; for example:
Election Calendar Report Updates
In the Election Calendar report, the govOrSenIncl field has been replaced by the nationalOffices field. This field confirms which national-level races (represented by the office IDs) will be covered in the event; for example, P for President, S for U.S. Senate, H for U.S. House, G for Governor.
Additional updates include the following new fields:
-
additionalEventDetails. Includes details on races AP will be tabulating for the event.
-
specialOnly. Specifies whether the event includes only special elections.
-
balanceOfPower. (For special elections) If applicable, indicates that the special election will affect balance of power; for example, chamber control.
For more information, see Election Calendar Report.
Virtual Timestamps During Testing
During the scheduled test sessions, Elections API used to return timestamps with the date and time of the test in real time.
Starting Feb. 2, 2026, results returned during scheduled elections testing will include "virtual timestamps," so that the times noted in the results response are as if they are those during the election event. These "virtual timestamps" replace the previous timestamps, which reflected the time of the results response during the test event.
For example, during a test taking place on Oct. 10, 2025, for the November 2025 general election, the lastUpdated field in the test results response would show a date of 2025-11-04 rather than 2025-10-10. The time in the lastUpdated field would show the simulated time on election night, and not the time of the test results response.
This change affects the following response field values:
-
lastUpdated (JSON); LastUpdated (XML)
-
pollClosingTime (JSON); PollClosingTime (XML)
-
winnerDateTime (JSON); WinnerDateTime (XML)
-
minDateTime in the next request link