Immediately returns the registration information on the voter queried by the authenticated organization.

When submitting new voter records to the API, the first_name, last_name, address, city, state, and zip fields are required. birth_date is optional, as are middle_name, suffix and phone_num. submitted_registration_date is optional and reflects the date a person was registered to vote by a voter registration organization (for example, the day their form was mailed in or the day they submitted an online form).

In addition to given inputs, the API will return back registration status and registration date. If both registration status and registration date are null, then the person is not found on the voter files and is therefore likely not registered. If registration status is null but there is a non-null registration date, then the person is found on the voter files, but a voter status was not provided by the Secretary of State.

Voters queried through this endpoint can be returned through the Get Voters query endpoint. An HTTP request to this endpoint will return an id, which can be used to track the voter through our other endpoints described below.

This endpoint is useful for immediately looking up a single person's current voter registration status at one point in time. To re-check a person's voter registration status and see if anything has changed, you'll need to re-call the API, or you'll need to use the Get Voters endpoint.

Once you've checked the status of a voter or group of voters through the Submit Voters POST endpoint or the Verify endpoint, you can use this endpoint to see if there have been updates to Alloy's data that may have impacted a voter's status. This endpoint returns all state codes found in your population of voters with the date the corresponding state was last updated in Alloy's database. You can learn more about how often we are committed to updating state-level voter data on our website: https://alloy.us/verify/details/

This endpoint submits new voter records in bulk and adds them to your tracked voters list. When submitting new voter records to the API, the first_name, last_name, address, city, state, and zip fields are required. birth_date, middle_name, suffix, and phone_num are optional. submitted_registration_date is optional and reflects the date a person was registered to vote by a voter registration organization (for example, the day their form was mailed in or the day they submitted an online form). It is an error to submit records which are missing the required fields or have values defined for appended fields. Users may submit no more than 1000 records per request.

This is endpoint is used for looking up voter registration statuses for many people. To check a single voter registration status, that may be queried by the corresponding GET endpoint.

Returns the full information on the voters tracked by the authenticated organization. Tracked voters can only be queried after they have been submitted via the Submit Voters POST request or the Verify GET request.

In addition to given inputs, the API will return back registration status and registration date. If both registration status and registration date are null, then the person is not found on the voter files and is therefore likely not registered. If registration status is null but there is a non-null registration date, then the person is found on the voter files, but a voter status was not provided by the Secretary of State.

We limit responses to 1000 records per request, sorted by updated_date. To paginate through the list of all voter records, you may include page_size and offset query parameters.

We include the ability to filter your voters by query parameters related to status, zipcode, and registration update dates:

• registration_status: Use the registration_status query parameter to filter voters whose registration status matches a certain status. Statuses include:

  • Active
  • Challenged
  • Not Eligible
  • Denied
  • Inactive
  • Pending
  • Confirmation
  • Removed
  • Preregistered
  • Rejected
  • Unregistered
  • Verify
  • Cancelled
  • Incomplete
  • Purged

• zip: Use the zipcode query parameter to filter by your population's zipcode. For example, to find Purged voters who reside in the zipcode 22121, you can use the query params ?registration_status=Purged&zip=22121.

• exceeding_days: Use the exceeding_days query parameter to filter voters whose registration status has not changed in over the specified number of days. For example, to find voters who reside in 22121, were Pending over 30 days ago, and their status still has not changed, you can use the query params ?registration_status=Pending&zip=22121&exceeding_days=30.

• within_days: Use the within_days query parameter to filter voters whose registration status has changed within the specified number of days. For example, to find a population of voters who have been Purged within 30 days, you can use the query params ?registration_status=Purged&zip=22121&within_days=30.

Use this endpoint to get the full information on the voters tracked by the authenticated organization. In addition to given inputs, the API will return back registration status and registration date. If both registration status and registration date are null, then the person is not found on the voter files and is therefore likely not registered. If registration status is null but there is a non-null registration date, then the person is found on the voter files, but a voter status was not provided by the Secretary of State.

Use this endpoint to add or replace individual fields of an existing voter record.