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).

Optional fields are used to narrow in on the voter record that best matches your query parameters. If birth_date is included in your query and does not match the birth date found on the SOS voter record, a null response will be returned. For all other optional fields, if that data is not part of the SOS voter record, it won't impact the match.

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.

For more information on the voter registration statuses returned for each state, check out Alloy's Voter Status Data Dictionary.

The rate limit for this endpoint is 200 requests/second.

Was this section helpful? Let us know here!

In some states, voters may request to be placed on a "permanent absentee ballot" list. This list is often maintained alongside the raw voter file data and denotes whether or not a voter meets that state's requirements to be considered permanent absentee for the upcoming election. You can see state specifications for permanent absentee below:

Some states use an exclusively vote-by-mail system. Voters verified in these states will return ‘true’ for their permanent absentee status. These states include: Colorado, Oregon, Utah, and Washington.

This endpoint returns all state codes 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/

Was this section helpful? Let us know here!

This endpoint can be used to check the voter status of many voters at once using a CSV.

The Verify API makes it easy to get the voter registration status for any voter: the Verify GET request can immediately return a voter status for a voter, and the Submit Voters POST request can help you track changing voter statuses over time. However, there may also be cases when you need to check the voter registration status for a large batch of voters one-off to support your voter registration efforts.

You can either implement this endpoint as needed to batch check statuses, or you can submit your CSV of voters through our website and have the results of your query emailed to you, typically within 1-2 days. The link for downloading your results expires one week after it is sent. You’ll only be able to use this form once you have an API key and secret assigned. Please reach out to our Partnerships team at partnerships@alloy.us to request API access if you haven’t already!

Note that when uploading your CSV, the columns should match the query parameters of the /v1/verify endpoint. Any misformatted rows will be removed from the output of voters you receive.

Want to learn more about how to bulk upload voters through Verify? Check out our how-to doc here!

Example:

first_name,middle_name,last_name,suffix,birth_date,zip,address,city,state,phone_num,submitted_registration_date
George,,Washington,,,22121,3200 Mount Vernon,Mt Vernon,VA,,

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.

Optional fields are used to narrow in on the voter record that best matches your query parameters. If birth_date is included in your query and does not match the birth date found on the SOS voter record, a null response will be returned. For all other optional fields, if that data is not part of the SOS voter record, it won't impact the match.

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.

The rate limit for this endpoint is 10 requests/second.