Decision Desk HQ is working on developing new endpoints, and categories of endpoints for client use, including:

New endpoints

Available races

This endpoint will return all available race_id’s and metadata based on the filtering parameters in the “Get a set of races by Race Parameters” endpoint. This endpoint will serve as a lighter weight version of the “Get a set of races by Race Parameters” endpoint.

Schedules / calendar

This endpoint will return a list of race_id’s and metadata that can be filtered by office, election_type, etc… that are ordered by race_date for all upcoming race_dates.

New Categories of Endpoints

Ultra low latency / push

We are working on creating ultra low latency, and push architecture API for clients. Implementation strategies include using websockets.

LLM oriented (high textual redundancy)

Based on client demand, we are actively working on creating endpoints that are designed for large language models. These endpoints will contain information in redundant keys that encompass multiple ways of “asking” for the data. For example our API includes a field for if a race is “called”, in a LLM optimized endpoint, we would add additional keys. like “Race projection” to create better inferencing from an LLM.

New fields

Race status

We are in the process of adding a new field to each race that contains information on what the current “status” of a race is. Different statuses would include “Vote’s are being counted”, “Election has been projected”, “Election has been certified”

Poll average and Forecast

For races that DDHQ has a poll average for, or a forecast for, those averages and ratings will be exposed through a poll_average, forecast, and win_probability key