LawLinter
Help

Guide

How API Access Fits With Legislative Research

LawLinter account users can manage API keys separately from saved research workflows, supporting developer and organizational access to legislative data.

Workflow

  1. Create an account and open API access from the account menu.
  2. Review the current plan and allowed scopes.
  3. Create a named API key for the application or workflow.
  4. Store the raw key securely because it is shown only once.
  5. Use developer docs for endpoint shape, authentication, rate limits, and errors.

Details

Saved workflows are built for browser research. API access is built for applications, data integrations, and repeat programmatic queries.

API keys have scopes, quota behavior, and usage history separate from favorites and collections.

Developer documentation remains public so teams can evaluate the API before needing production keys.

Questions

Do I need API access to use saved workflows?

No. Saved searches, favorites, collections, and text bookmarks are account research tools, not API-only features.

Where are API docs?

The developer documentation starts at /developers and includes authentication, search, bills, lawmakers, votes, errors, and rate limits.