Business automation: request dependencies are the hard part
API Parrot’s maker turned recurring request-correlation work into a visual flow and code-export tool.
The takeaway
Look for repeated investigative work, not just more endpoints.
The context
The maker describes time-consuming manual tracing between requests, including values originating in pages or JavaScript objects. Their tool records requests, identifies correlations, and exports parts or all of a flow as JavaScript. The useful pattern is making hidden dependencies visible.
Steps worth trying
Editorial suggestions, not promises made by the original author.
- 01
In an authorized system, record a recurring workflow and mark inputs, outputs, and cross-step variables.
- 02
Automate well-understood dependencies first and use test accounts to check retries, expiry, and errors.
Where this applies — and where it may not
Features are the author’s launch description and were not independently tested; accessible endpoints do not imply authorization to automate them.
From the discussion
“I built a tool called API Parrot”
@pvarghav · View source
Show HN: API Parrot – Automatically Reverse Engineer HTTP APIs
@pvarghav · 456 points · 117 comments
Read the Hacker News threadSource: OpenIndex Hacker News dataset (ODC-By). Original content belongs to its authors. Summaries, translations, and suggested steps are AI-assisted editorial work. Read the sources; individual outcomes are not guarantees.