STATUS WITH A SOURCE
Mail In Ballot Vote API
Explain what a ballot status actually means.
A ballot-status message is only useful when its meaning and source are clear. “Received” may describe a specific step in one jurisdiction's process; it should not be expanded into a universal claim about counting or acceptance. This page explains how to evaluate a proposed status interface. VoteAPI.com does not track individual ballots, handle ballots, or determine the status of a person's vote.
Keep the jurisdiction's vocabulary intact
Build a status dictionary from the actual authority's documented process. Preserve the original label and provide a careful explanation, rather than mapping every event to a generic green check. California's official ballot-status page is one example of a jurisdiction describing mailed, received, and counted updates. It does not establish a nationwide status vocabulary. A proposed integration should identify which jurisdiction each explanation applies to and avoid suggesting that the absence of an update proves a particular action did or did not occur.
Separate an event time from an observation time
A source may describe when an event occurred, when its record changed, or when an application retrieved it. Model those times separately. If only the retrieval time is available, label it honestly rather than calling it the time the ballot moved. Define how a stale observation will be displayed and what happens when refreshing fails. A previous status can remain readable with its age visible, but an unavailable response should not overwrite that record with an invented rejection or acceptance.
Design a private route to official assistance
Keep personal status lookups out of public indexes and shared result pages. A proposed support flow should identify the responsible election office and relevant jurisdiction without collecting unnecessary sensitive data. Do not infer a remedy, deadline, or procedural entitlement from a status code unless the official source explicitly supports it. For actual questions about a person's ballot, the appropriate next step is the official channel identified by that authority. The interface should help the reader understand the source of uncertainty, rather than making an unsupported procedural decision.
COMMON QUESTIONS
A clearer
starting point.
Does a received status necessarily mean a ballot was counted?
Do not assume that. Interpret the label using the relevant authority's own explanation and process. A proposed interface should preserve the distinction between stages rather than compressing them into one success state. This page cannot determine the status of an individual ballot or confirm its treatment.
What should an interface do when no update appears?
Explain which information is unavailable and when the source was last checked. Preserve an earlier observation with its timestamp if appropriate. Provide the relevant official support route, and avoid inventing a deadline, rejection, or counting result from silence. Actual procedural questions belong with the responsible election authority.
CONTINUE EXPLORING
Connect the ideas.
All 18 topic guides05 / 18
Voter ID Vote API
The voter ID vote API label can blur several different questions: who controls an account, whether a record matches a person, and.
EXPLORE THE GUIDE
02 / 18
Election Vote API
A single-contest election feed should make a precise promise: these records describe this office or question, in this jurisdiction, for this election.
EXPLORE THE GUIDE
15 / 18
Elections Vote API
An elections index helps readers find the right event and jurisdiction before inspecting individual contests. Its central questions are coverage, calendar meaning.
EXPLORE THE GUIDE