use-apify.com
API: guides & tutorials
REST and GraphQL patterns for automation: auth, pagination, rate limits, webhooks, and when to call site APIs instead of raw HTML in Apify pipelines.
7 articles
View all tags
Calling an API is often cleaner than scraping HTML when a site exposes one. These guides cover REST and GraphQL patterns for automation: authentication, pagination, rate limits, and webhooks, plus how to spot hidden JSON endpoints behind a page.
The Apify API starts actors, streams datasets, and fits into CI, while webhooks push results downstream without polling. Below you will find tutorials on token scoping, idempotent retries, and when to call an API instead of parsing raw HTML.
Chatbase ships two REST API versions. API v1 is the original integration path; API v2 is a modern redesign with structured error codes, cursor-based pagination, Server-Sent Events (SSE) streaming, and a cleaner response contract. This guide covers v2 exclusively — it is the forward path for all new integrations in 2026. By the end, you will know how to authenticate, send streaming chat messages, paginate through conversation history, handle rate limits, and feed fresh website content scraped with Apify into your Chatbase knowledge base.
Prerequisites: API v2 requires a Standard plan or above. Free and Hobby accounts cannot use the API. Check the pricing guide to evaluate upgrading.
Web scraping APIs fall into three categories: public APIs (official, stable, no scraping needed), unofficial or reverse-engineered APIs (hidden endpoints used by the frontend), and scraping APIs (services like Apify, Bright Data, Firecrawl that handle scraping for you). This guide covers finding hidden APIs, REST and GraphQL scraping patterns, authentication, rate limiting, pagination—and when to use a scraping API service instead of building your own. Try Apify API · Firecrawl API
Yes — IPRoyal has a REST API. It lets you generate proxy credentials with geo-filters, check remaining bandwidth, manage sub-users, and build fully automated rotation pipelines without touching the dashboard.
This guide covers every API surface: authentication, proxy list generation, bandwidth polling, sub-user management, error handling, and ready-to-run Python and Node.js examples.
Yes, Make.com has a full REST API. You can create scenarios, activate them, trigger runs, and pull execution logs — all without touching the visual editor.
Most developers discover this too late. They build elaborate Make workflows manually, then wonder how to replicate them across environments, monitor them in a dashboard, or trigger them conditionally from their own code. The Make API solves all three.
This tutorial covers the complete lifecycle: authentication, scenario management, programmatic execution, and log retrieval. Every example runs with curl and Python.
The Make.com HTTP module lets you call any REST API directly from your scenario — no dedicated connector needed. If an app exposes an HTTP endpoint, the HTTP module reaches it. GET, POST, PUT, DELETE, file downloads, OAuth handshakes, and paginated data dumps are all first-class operations.
This tutorial covers every HTTP module variant, walks through request configuration in detail, and finishes with three production-ready examples that show exactly how the module behaves under real-world conditions.
