e.ventures Data

Welcome to e.ventures Data! You'll find here a comprehensive guide to help you start working with e.ventures Data as quickly as possible.

At e.ventures, we use data science, machine learning, and artificial intelligence to run our data analytics platform, which guides our business decisions. We're excited to open source and share our proprietary technologies with you.

Get Started

API Reference

Overview

We provide a total of 9 API to give you access to Federal Election Commission (FEC) Data.

The API are categorized as:

1. Data + Charts API

  • We provide 5 API that returns the:
    • Documentation and user instructions
    • Age distribution for the donors to one or more committees
    • Number of cumulative donors over time for one or more candidates a given candidate id(s) and cycle(s)
    • Candidate information for a given candidate name
    • Candidate and Committee information for a given candidate name

2. Enricher API

  • We provide 4 API that enrich and make the dataset more meaningful. With our API, you can get the:
    • Gender and age estimates with names and reference dates.
    • Gender and age distributions for a name and a reference date.
    • Ethnicities for a name and a year given in a JSON file.
    • Ethnicity for a name and a year.

API Reference

Our REST API use standard HTTP response codes, authentication, and verbs.

The base URL is https://data.eventures.vc/data-charts/v1.

You can test our API on our interactive Swagger pages:

  1. Data + Charts API
  2. Enricher API

Authentication

Before you can run any of our API, you have to authenticate with your API key. This API key is provided by an e.ventures team member.

Here are the steps on how to do so using our interactive Swagger pages for Data + Charts API or Enricher API.

  1. Go to Data + Charts API or Enricher API.
  2. Click the Authorize button on the left.
  3. In the Value field, enter your API key. This API key is provided by an e.ventures team member.
  4. Click the Authorize button.
  5. Awesome! You are now authorized to test the API on the interactive Swagger page.

Status Codes

We provide a list of Hypertext Transfer Protocol (HTTP) response status codes to indicate the success of failure of an API request.

Here is the HTTP status code summary:

Code

Description

200 - OK

A CSV/JSON or HTML file containing the result.

401 - Unauthorized

The API key is missing or invalid.

404 - Not Found

Page or Content not found

Unexpected error

Unexpected error.

HTTP Verbs

We have the following HTTP verbs for our API:

Verb

Description

GET

This verb is used for retrieving resources.

POST

This verb is used for creating resources.

Next Steps

Learn more about our Data + Charts API or Enricher API.

For more details on what you can do with the data, please refer to the Use Cases section. You can also learn how to access the data on the FEC Data Platform via our:

Updated 11 months ago



API Reference


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.