/opensecrets/industries

POST /api/opensecrets/industries

Price: 10 credits

Get an industry / interest-group money-in-politics profile by industry code

How to use it

Get the money-in-politics profile of an industry or interest group by its OpenSecrets industry code. Returns the industry name, parent sector and description, the top contributing organizations with their giving split across parties and ideological groups, the top candidate recipients of the industry's money, and the industry's top lobbying clients, for the selected election cycle.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• ind string required — Industry / interest group code (examples: "B02")
• cycle string — Election cycle (default: "2024"; one of: "a", "2026", "2024", "2022", "2020", "2018", "2016", "2014", "2012", "2010", "2008", "2006", "2004", "2002", "2000", "1998", "1996", "1994", "1992", "1990")

Response

• @type string (default: "OpensecretsIndustry")
• id string required
• name string nullable
• sector string nullable
• description string nullable
• cycle string nullable
• profile_url string nullable
• top_contributors array (default: [])
  • @type string (default: "OpensecretsIndustryContributor")
  • name string nullable
  • total integer nullable
  • to_democrats integer nullable
  • to_republicans integer nullable
  • to_liberal_groups integer nullable
  • to_conservative_groups integer nullable
  • to_nonpartisan_groups integer nullable
  • lean string nullable
• top_recipients array (default: [])
  • @type string (default: "OpensecretsIndustryRecipient")
  • name string nullable
  • chamber string nullable
  • amount integer nullable
• top_lobbying_clients array (default: [])
  • @type string (default: "OpensecretsIndustryLobbyingClient")
  • name string nullable
  • total 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 — Industry not found 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.