PipedreamHQ / PipedreamHQ/pipedream

[APP] Bargo Congress Trades API

Open
#21,550 0 comments 0 reactions 0 assignees View on GitHub
app enhancement triaged
Dominant language
JavaScript
Stars
11.7k
Forks
5.8k
Avg merge
3d 10h
Merged PRs (30d)
102

Description

**Name of app / service**

Bargo Congress Trades API — https://www.bargo.ai/free-apis/congress

I'm the developer behind it, so treat this as a first-party request rather than a user asking for someone else's API.

**Link to developer documentation**

- Docs: https://www.bargo.ai/free-apis/congress
- OpenAPI 3.0: https://www.bargo.ai/free-apis/congress/openapi.json
- Free API keys: https://www.bargo.ai/free-apis/dash
- Terms: https://www.bargo.ai/free-apis/terms

REST over HTTPS, JSON responses, CORS enabled. Auth is an `X-Api-Key` header (bearer and a `token` query param also work). Keyless access is allowed at 30 requests / 100 rows per day per IP; a free key raises that to 100 requests / 1,000 rows. No paid tier gates the data.

**Is lack of support preventing you from moving forward, or do you have a workaround?**

There's a workaround today — the API is plain REST, so it works through the generic HTTP request action. Registering it as an app would mainly let users store the key as a managed connected account instead of pasting it into each step, and make it discoverable in the app list.

**Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**

Six endpoints, which map fairly directly to actions:

| Endpoint | Suggested action |
|---|---|
| `GET /trades` | List trades — filter by member, chamber, transaction type, date range |
| `GET /trades/{ticker}` | List trades for a ticker |
| `GET /members` | List members of Congress with disclosure activity |
| `GET /members/{member_slug}` | Get one member's disclosures |
| `GET /stats` | Get aggregate trading statistics |
| `GET /health` | Dataset freshness / status |

A polling trigger on new disclosures would be the natural first source — `/trades` is ordered by disclosure date and `/health` exposes `latest_disclosure`, so dedupe on filing is straightforward.

Happy to do the implementation work and open the PR myself once the app directory exists, or to answer questions about the API.

One caveat worth stating: these are STOCK Act disclosures, which can legally be filed up to ~45 days after the trade. It's a disclosure feed, not a real-time market data feed.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Contributor guide

Open the contributing guide

Research direction

Start with the linked Bargo Congress Trades API documentation and OpenAPI specification, then inspect the repository's existing app-directory integration patterns. Define the integration around the six listed endpoints and the proposed new-disclosures polling trigger; it is done when the app is discoverable and its actions and trigger work with the documented authentication and response data.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.