A pure JavaScript library for accessing the Legiscan database of US state legislation. You will need an API key from https://legiscan.com/legiscan in order to use this client. Best-practice code examples from actual reporting at Chalkbeat are available in the samples folder.

For Node or other server-based runtimes, you can install from NPM:

npm install @civicnews/legiscan-client

Although it is primarily intended for use on the server, the client uses only standard runtime APIs like fetch(), and (as long as the API continues to use the correct CORS headers) can also run in the browser itself.

When using Node, this package also installs a command-line client that can be run with the legiscan-client command, either for manual access or integration with other languages.

Getting started

To interact with the API, import and create an instance of the LegiscanClient class, which takes an API key as its argument. You can also set the $LEGISCAN_API_KEY environment variable, and then the client will pick that up instead.

import { LegiscanClient } from "@civicnews/legiscan-client";
// providing an API key directly:
let legiscan = new LegiscanClient(API_KEY);
// with the environment variable:
let legiscan = new LegiscanClient();

The client provides async methods corresponding to each API call. For example, to run a search and get bill details, you could run the following code:

let results = await client.getSearch("education AND javascript");
for (let result of results) {
  var details = await client.getBill(result.bill_id);
  Object.assign(result, details);
}

Generally, the objects returned by the client methods will match the schema described in the API documentation, but with some normalization applied. For example, when calling getBill, the status, event, and sponsor type fields will be normalized to their string representations, with an added *_id property containing the numerical code. This is meant to create more consistency between API calls, some of which return flags as strings and some as numerical codes.

CLI

When installed globally, or when executed from an npm run script, the legiscan-client command provides ND-JSON output from API calls. Some of these calls return a lot of results, or need to be filtered, and that's easier to do with newline-delimited output in languages and tools that support streaming from invoked processes.

The command line takes a case-insensitive API method name as its first argument, followed by positional arguments for required input and flags for optional parameters matching the Legiscan documentation:

# getBill always wants an ID
legiscan-client getbill 174039

# you can also provide this with a flag
legiscan-client getbill --id=174039

# getsearch example
legiscan-client getbill "education AND gender" --state=TN

Best practices and usage notes

Caching

The Legiscan API limits users to 30,000 requests per month (resetting on the 1st). This may seem like a lot, unless you're a journalist who does a lot of scraping, or until you start pulling all legislation for an active session in, say, Michigan (about 3,000 bills as of April 2024). Since you cannot get many parts of the bill status without individual calls to the getBill method, your token usage can add up quickly.

As a result, it is extremely important to add a caching layer whenever you use the API client for anything involving bill details. For example, in the samples/michigan.js file, you can see where we use a SQLite database as a key/value store:

import Database from "better-sqlite3";
var cache = new Database("cache.db");
cache.exec(`CREATE TABLE IF NOT EXISTS cache (key TEXT PRIMARY KEY, value TEXT);`);
var getCached = cache.prepare(`SELECT value FROM cache WHERE key = ?;`).pluck();
var setCached = cache.prepare(`INSERT INTO cache VALUES (?, ?);`);

Each bill returned from a Legiscan API call includes a change_hash ID that is unique to that particular bill revision. Using that hash as a key, you can only make requests when the bill is updated, and otherwise pull from the database to save a request:

var hash = bill.change_hash;

var details = getCached.get(hash);
if (details) {
  // use the cached info
  details = JSON.parse(details);
} else {
  // get a fresh copy and cache it
  details = await client.getBill(bill.bill_id);
  setCached.run(hash, JSON.stringify(details));
}

This is, of course, a kind of Minimum Viable Cache, and if you're using a database more extensively for storing persistent legislative data, you can probably just adapt it. Conversely, if you're only getting master lists or searches and don't really care about the bill details, it may be possible (although probably not advisable) to hit the API directly. We do not ship a cache layer in the client itself, because we believe it's better for you to be in control of response freshness based on your specific needs.

Flags and Enums

The Legiscan API uses a lot of flags and/or sentinel values for things like legislation progress, states, or record type. Sometimes these are supplemented with a human-readable text version, and sometimes not. As mentioned above, this client will attempt to normalize and fill in properties so that anything like state_id will also provide a string-typed state field.

However, if you're interacting with some API calls that expect to receive these flags, this library also exports a set of constants that can be used to convert between them. The following constants are objects mapping the numeral code to their text value:

• BILL_TYPE - Legislation categories, such as "Bill," Resolution," or "Executive Order"
• EVENT_TYPE - Distinguishes between hearings, executive sessions, and markup
• PARTY - Political party associated with sponsors, legislation, and so on
• PROGRESS - Legislation progress from "Prefiled" forward. Note that these IDs are not in chronological order.
• REASON - Not used in the REST API
• ROLE - The type of person or persons sponsoring a bill
• SAST_TYPE - Same As/Similar To metadata
• SPONSOR_TYPE - The sponsor relationship to a bill ("Sponsor", "Co-Sponsor", etc)
• STANCE - A position that can be provided when setting an automated monitor list
• STATE - US State by Postal Code
• SUPPLEMENT_TYPE - Types of supplemental documents for a bill, such as fiscal notes or analysis
• TEXT_TYPE - Types of primary documents for a bill revision
• VOTE - "Yea," "Nay," "Not voting," or "Absent"

Each of these has a corresponding *_VALUES constant that goes the other way, where the lookup key is the string text, and the value is the API flag.

import { VOTE, VOTE_VALUES } from "@civicnews/legiscan-client";

console.log(VOTE[1]); // "Yea"
console.log(VOTE_VALUES["Nay"]); // 2

Internal methods

In addition to the methods provided on the client, you can also make arbitrary requests to the Legiscan API endpoint using its request() method. This is what we use internally for calling the API, and may be useful if new methods are added, or you're using something the client doesn't currently have built-in. For example, to get a monitor list, you could write:

var response = await client.request("getMonitorList", { record: "current" });
console.log(response.monitorlist);

In some cases (including the above monitor list), the API will not return an array for a list of items, but instead will provide an object with numerical keys. In this case, you can use the provided numericalToArray function to convert this into an actual JavaScript array (note that this will throw away any non-numerical keys on the object during conversion):

import { numericalToArray } from "@civicnews/legiscan-client";
var response = await client.request("getMonitorList", { record: "current" });
// convert to a native array
var list = numericalToArray(response.monitorlist);

Yes, this is a weird and annoying API choice, and was one of the inspirations for creating this client in the first place.