Skip to main content

​
What is Geekflare?

Geekflare provides a suite of REST APIs for Scraping, Search, Data Extraction, Screenshots, DNS lookups, and other essential web utilities. Every request consumes credits based on the endpoint and options used. See Credit Mapping for the full breakdown.

​
Getting started

Getting up and running with Geekflare is simple. Create a free account (no credit card required) to generate your API key. Once you have your key, you can test endpoints using our Interactive Playground.

Get your API key

Sign up for a free account to generate your key.

​
API Protocol

Geekflare provides a RESTful API. It is accessed via HTTPs and ensures that all data sent and received is formatted as JSON.

​
Integration Methods

Integrate Geekflare into your applications using REST API, SDKs, MCP or No-Code platforms.

REST API

Standard HTTPS endpoints returning JSON payloads. Compatible with OpenAPI specifications.

SDKs

Accelerate development with our official Node.js/TypeScript and Python packages.

No-Code

Connect Geekflare to thousands of apps via Zapier and Make without writing a single line of code.

MCP Server

Plug Geekflare into AI IDEs and LLM agents to give them web scraping, search, screenshot and other tools.

Interactive Playground

Use all our APIs directly in your browser.

​
Rate Limits

Rate limits depend on your subscription plan. If you exceed your limit, the API returns an HTTP 429 Too Many Requests error — see Rate Limit Exceeded for how to handle this gracefully.

​
Proxy & Geolocation

Several Geekflare endpoints (such as Scraping, Site Status, PDF Generator, Load time, etc.) support request routing via specific locations. To use this, pass the target country code in the proxyCountry parameter. View supported APIs Note: Using proxies incurs additional credit costs. We recommend using this feature only when geolocation is required.
Proxy is available to paid users only.

​
Request

​
Authentication

Every request must include your API key in an x-api-key request header:
See our Security page for details on how we protect your API keys and data.

​
Base URL

For all the endpoints listed in this documentation, the base URL is:

​
Response

The API response follows some common formats for the sake of clarity and consistency. Depending on the request status, the response structures are as given below. See the Error Code Reference for the complete list.

​
Success Response

On successful processing of a request, the API returns a response in the following format:
200 - Success

​
Missing API Key

When no API key is provided in the request, the following response structure is returned:
401 - Unauthorized. See Unauthorized for how to resolve this.

​
Invalid API Key

When an invalid or incorrect API key is provided:
401 - Unauthorized. See Unauthorized for how to resolve this.

​
Forbidden Response

If you are under a free plan and try to access a paid-only API like Port Scanner, it would return an error in the following format:
403 - Forbidden. See Forbidden for how to resolve this.

​
Not Found Response

If a wrong endpoint or wrong request type (POST instead of GET, for example) is provided, the API returns an error in the following format:
404 - Not Found

​
Next Steps

Quickstart

Make your first API call in your language or framework of choice.