/opensecrets/lobbying-clients

POST /api/opensecrets/lobbying-clients

Price: 10 credits

Get a federal lobbying client profile by organization id

How to use it

Get the federal lobbying profile of a client (the organization paying to lobby) by its OpenSecrets organization id. Returns the reported lobbying total for the year, the subsidiaries portion, the split between in-house spending and outside firms, the issue areas lobbied, the hired firms, the agencies and bills named on the filings, the quarter-by-quarter breakdown and the full annual spending history.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Lobbying client organization id (examples: "D000000125")
• year integer nullable — Calendar year of reported lobbying; the most recent reported year is used when omitted (examples: 2024; min: 1998)

Response

• @type string (default: "OpensecretsLobbyingClient")
• id string required
• client_id string nullable
• name string nullable
• alias string nullable
• year integer nullable
• profile_url string nullable
• industry object nullable
  • @type string (default: "OpensecretsLobbyingIndustry")
  • id string nullable
  • name string nullable
• total_lobbying integer nullable
• subsidiaries_subtotal integer nullable
• lobbyist_count integer nullable
• former_government_lobbyist_count integer nullable
• other_inhouse_lobbyist_count integer nullable
• inhouse_total integer nullable
• outside_firms_total integer nullable
• issue_areas array (default: [])
  • @type string (default: "OpensecretsLobbyingIssueArea")
  • id string nullable
  • name string nullable
  • alias string nullable
  • mention_count integer nullable
• hired_firms array (default: [])
  • @type string (default: "OpensecretsLobbyingFirm")
  • id string nullable
  • name string nullable
  • alias string nullable
  • lobbyist_count integer nullable
  • total integer nullable
• agencies array (default: [])
  • @type string (default: "OpensecretsLobbyingAgency")
  • id string nullable
  • name string nullable
  • alias string nullable
  • branch string nullable
  • filing_count integer nullable
• bills array (default: [])
  • @type string (default: "OpensecretsLobbyingBill")
  • id string nullable
  • number string nullable
  • bill_title string nullable
  • report_count integer nullable
• quarters array (default: [])
  • @type string (default: "OpensecretsLobbyingQuarter")
  • quarter string nullable
  • total integer nullable
  • filing_count integer nullable
• annual_totals array (default: [])
  • @type string (default: "OpensecretsLobbyingAnnualTotal")
  • year integer nullable
  • total integer nullable
  • lobbyist_count integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Lobbying client not found, or no lobbying reported for that year Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.