LawLinter

Access

Authentication And API Keys

Protected API requests require an API key created from an account with an active or trialing API subscription.

Auth

Authorization: Bearer API key

Current base

/api/legislative

Version target

/api/v1

Create an API key

Logged-in users manage their own keys from /account/api-access. Administrators can review plans, keys, usage, and subscription state in the admin API access section.

Launch-period API access is metered by plan. The account API access page shows the current monthly and burst limits for the account.

The raw API key is shown once after creation. Store it securely; only the key prefix and hash are retained for later validation.

  • Choose the scope set your plan allows.
  • Copy the raw key at creation time.
  • Send the key with each protected request.
  • Revoke keys that are no longer needed.

Request header

curl -H "Authorization: Bearer $LAWLINTER_API_KEY" "https://example.com/api/legislative/search?q=energy&entityType=bill"

Alternate header

The compatibility API also accepts X-API-Key for clients that cannot send Authorization headers.

curl -H "X-API-Key: $LAWLINTER_API_KEY" "https://example.com/api/legislative/search?q=energy"

Need an API key?

Create and revoke keys from your account API access page when your subscription allows API usage.

Manage API access Authentication guide