Docs
Every canonical reference surface for the apihq data APIs, one click away. The product facts themselves live on the actor pages and the shared reference pages — this index only points at them.
Start here
- What apihq is — eight pay-per-result data APIs (Apify Actors) for YouTube, Google Play, the App Store, and TripAdvisor, with one shared failure contract.
- Pick an API and run it — each actor page carries an example run, exact input and output, and a first run costs under a cent on an existing Apify account.
- How pay-per-result billing works — per delivered record, failures $0, spend caps via Apify Run Limits.
Shared reference
- Error codes reference — Every machine-readable error code the apihq actors can return, in one canonical table: what each code means, which API emits it, and why none of them are ever billed.
- What is a pay-per-result data API? — A pay-per-result data API bills per delivered record instead of per request or per month. How the billing mechanism works, how it compares to per-request APIs and subscriptions, and where the model fits.
API reference, per actor
The canonical reference for each API lives on its actor page. These links jump straight to the stable sections.
Comparisons
First-hand tested where possible, primary-source documented otherwise; each page carries its own methodology and last-verified date. The comparison policy is part of how facts are checked.
- YouTube Transcript Scraper vs youtube-transcript-api: same 11 videos, both tools — last verified 2026-07-17.
- YouTube Transcript Scraper vs the YouTube Data API captions endpoints — last verified 2026-07-17.
Task-led material lives outside the reference: integration guides and importable workflow templates.