Skip to content
An RESTful API for U.S. federal spending data.
Python CSS PLpgSQL TSQL JavaScript SQLPL Other
Branch: dev
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.


Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Modifications to CODEOWNERS after first test Feb 21, 2019
bulk_downloads Adding bulk_downloads folder Nov 3, 2017
config keeping max workers even though the expectation is under 70 will be a… May 18, 2020
requirements Update versions Mar 12, 2020
usaspending_api Merge branch 'dev' into ftr/dev-5260-new-defc-reference-table Jun 1, 2020
.codeclimate.yml Update .codeclimate.yml Jul 12, 2019
.env [DEV-3064] improved scripts and docker compose Oct 22, 2019
.gitignore [DEV-4775] adding to .gitignore Apr 9, 2020
.pre-commit-config.yaml tweak to pre-commit regex Nov 25, 2019
.pyup.yml updated requests version and tweaked pyup file Oct 30, 2018
.travis.yml Correct travis command that runs integration tests Apr 2, 2020 Update Jul 26, 2019
Dockerfile referenced public rpm no longer exists May 5, 2020
LICENSE Adding and LICENSE Jul 16, 2019 DEV-4685 making use of local ES (preferably by way of docker-compose)… Mar 23, 2020 Fix typos and grammatical errors Dec 27, 2018
docker-compose.yaml DEV-4685 integration tests that show need for specifically routing re… Mar 23, 2020
dredd.yml TEST: added dredd to parse syntax (dry-run) Mar 27, 2020 dev-3232: more cleanup Aug 26, 2019 updated comment and changed python(2) to python3 Sep 16, 2019
pyproject.toml app python version is now 3.7 Nov 25, 2019
readme.jpg [DEV-3680] update readme.jpg to show the 2019 spending banner from we… Nov 1, 2019

USAspending API

Code style: black Build Status Test Coverage Code Climate

This API is utilized by to obtain all federal spending data which is open source and provided to the public as part of the DATA Act.

USAspending Landing Page

Creating a Development Environment

Ensure the following dependencies are installed and working prior to continuing:


If not using Docker:

Using Docker is recommended since it provides a clean environment. Setting up your own local environment requires some technical abilities and experience with modern software tools.

  • Command line package manager
    • Windows' WSL bash uses apt-get
    • MacOS users will use Homebrew
    • Linux users already know their package manager (yum, apt, pacman, etc.)
  • PostgreSQL version 10.x (with a dedicated data_store_api database)
  • Elasticsearch version 7.1
  • Python 3.7 environment
    • Highly recommended to use a virtual environment. There are various tools and associated instructions depending on preferences

Cloning the Repository

Now, navigate to the base file directory where you will store the USAspending repositories

$ mkdir -p usaspending && cd usaspending
$ git clone
$ cd usaspending-api

Database Setup

There are three documented options for setting up a local database in order to run the API:

  1. Local Empty DB. Use your own local postgres database for the API to use.
  2. Containerized Empty DB. Create an empty directory on your localhost where all the database files will persist and use the docker-compose file to bring up a containerized postgres database.
  3. Local Populated DB. Download either the whole database or a database subset from the USAspending website.

Option 1: Using a Locally Hosted Postgres Database

Create a Local postgres database called 'data_store_api' and either create a new username and password for the database or use all the defaults. For help, consult:

Make sure to grant whatever user you created for the data_store api database superuser permissions or some scripts will not work:

postgres=# ALTER ROLE <<role/user you created>> WITH SUPERUSER;

Option 2: Using the Docker Compose Postgres Database

See below for basic setup instructions. For help with Docker Compose:

Database Setup and Initialization with Docker Compose
  • None of these commands will rebuild a Docker image! Use --build if you make changes to the code or want to rebuild the image before running the up steps.

  • If you run a local database, set POSTGRES_HOST in .env to host.docker.internal. POSTGRES_PORT should be changed if it isn't 5432.

    • docker-compose up usaspending-db will create and run a Postgres database in the POSTGRES_CLUSTER_DIR specified in the .env configuration file. We recommend using a folder outside of the usaspending-api project directory so it does not get copied to other containers in subsequent steps.

    • docker-compose run usaspending-manage python3 -u migrate will run Django migrations:

    • docker-compose run usaspending-manage python3 -u load_reference_data will load essential reference data (agencies, program activity codes, CFDA program data, country codes, and others).

    • docker-compose run usaspending-manage python3 -u matview_runner --dependencies will provision the materialized views which are required by certain API endpoints.

Manual Database Setup
  • docker-compose.yaml contains the shell commands necessary to set up the database manually, if you prefer to have a more custom environment.

Option 3: Downloading the database or a subset of the database and loading it into PostgreSQL

For further instructions on how to download, use, and setup the database using a subset of our data please go to:

USAspending Database Download

Elasticsearch Setup

Some of the API endpoints reach into Elasticsearch for data.

  • docker-compose up usaspending-es will create and start a single-node Elasticsearch cluster, using the ES_CLUSTER_DIR specified in the .env configuration file. We recommend using a folder outside of the usaspending-api project directory so it does not get copied to other containers.

  • The cluster should be reachable via at http://localhost:9200 ("You Know, for Search").

  • Optionally, to see log output, use docker-compose logs usaspending-es (these logs are stored by docker even if you don't use this).

Running the API

docker-compose up usaspending-api

  • You can update environment variables in (buckets, elasticsearch, local paths) and they will be mounted and used when you run this.

The application will now be available at http://localhost:8000.

Using the API

In your local development environment, available API endpoints may be found at http://localhost:8000/docs/endpoints

Deployed production API endpoints and docs are found by following links here:

Loading Data

Note: it is possible to run ad-hoc commands out of a Docker container once you get the hang of it, see the comments in the Dockerfile.

For details on loading reference data, DATA Act Broker submissions, and current USAspending data into the API, see

For details on how our data loaders modify incoming data, see

Running Tests

Test Setup

To run tests, you need:

  1. Postgres A running PostgreSQL database server (See Database Setup above)
  2. Elasticsearch A running Elasticsearch cluster (See Elasticsearch Setup above)
  3. Required Python Libraries Python package dependencies downloaded and discoverable (See below)
  4. Environment Variables Tell python where to connect to the various data stores (See below)

Once these are satisfied, simply run:

(usaspending-api) $ pytest

Required Python Libraries

Create and activate the virtual environment using venv, and ensure the right version of Python 3.7.x is being used (the latest RHEL package available for python36u: as of this writing)

$ pyenv install 3.7.2
$ pyenv local 3.7.2
$ python -m venv .venv/usaspending-api
$ source .venv/usaspending-api/bin/activate

Your prompt should then look as below to show you are in the virtual environment named usaspending-api (to exit that virtual environment, simply type deactivate at the prompt).

(usaspending-api) $

pip install application dependencies

(usaspending-api) $ pip install -r requirements/requirements.txt

Environment Variables

Create a .envrc file in the repo root, which will be ignored by git. Change credentials and ports as-needed for your local dev environment.

export DATABASE_URL=postgres://usaspending:usaspender@localhost:5432/data_store_api
export ES_HOSTNAME=http://localhost:9200
export DATA_BROKER_DATABASE_URL=postgres://admin:root@localhost:5435/data_broker

If direnv does not pick this up after saving the file, type

$ direnv allow

Alternatively, you could skip using direnv and just export these variables in your shell environment.

Including Broker Integration Tests

Some automated integration tests run against a Broker database. If the dependencies to run such integration tests are not satisfied, those tests will bail out and be marked as Skipped. (You can see messages about those skipped tests by adding the -rs flag to pytest, like: pytest -rs)

To satisfy these dependencies and include execution of these tests, do the following:

  1. Ensure you have Docker installed and running on your machine
  2. Ensure the Broker source code is checked out alongside this repo at ../data-act-broker-backend
  3. Ensure you have the DATA_BROKER_DATABASE_URL environment variable set, and pointing to a live PostgreSQL server (no database required)
  4. Ensure you have built the Broker backend Docker image by running:
    (usaspending-api) $ docker build -t dataact-broker-backend ../data-act-broker-backend

NOTE: Broker source code should be re-fetched and image rebuilt to ensure latest integration is tested

Re-running the test suite using pytest -rs with these dependencies satisfied should yield no more skips of the broker integration tests.


To submit fixes or enhancements, or to suggest changes, see

You can’t perform that action at this time.