API Overview

The iSearchFrom API lets teams automate selected organization workflows such as creating searches, listing search history, managing projects, reading token data, and working with tracker or AI Visibility campaign data.

Most customers can use the app without the API. Use the API when you need integration, automation, reporting pipelines, or internal tooling. If you want an AI agent to call iSearchFrom instead of writing code, use the MCP server — same capabilities, no HTTP plumbing.

This page is orientation — the base URL, auth, and a first request. For the complete, interactive reference, open the API explorer:

Interactive API Reference ↗Every endpoint, parameter, request and response schema, and error — generated directly from the live API and browsable in your browser. This is the authoritative contract; start here to build against a specific endpoint.

Customer API scope

Admin endpoints are intentionally omitted. The reference above shows only the customer-facing, API-key-accessible surface.

Base URL

All API requests go to a single base URL:

https://api.isearchfrom.com/v1

Authentication

App requests

App-driven requests use browser session cookies and the active organization selected in the app.

Server automation

Server-to-server automation should use an API key in the X-API-Key header. For API key setup, see Authentication and API Keys.

Endpoints

Every customer-facing endpoint — Projects, API keys, Direct Search, Search Engine Proxy, the Position and Ad trackers, AI Visibility, Tokens — with its exact methods, parameters, request and response schemas, and errors, is in the API Reference. It’s generated from the live API, so it’s always current. The examples below are just enough to get a first request working.

Examples

These examples assume:

BASE_URL="https://api.isearchfrom.com/v1"

Direct Search

curl -X POST "$BASE_URL/tools/serp/direct-search" \
  -H "X-API-Key: $ISEARCHFROM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "best rank tracker",
    "country": "US",
    "language": "en",
    "engine": "google"
  }'

Proxy Search

curl -X POST "$BASE_URL/tools/serp/proxy-search" \
  -H "X-API-Key: $ISEARCHFROM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "best local seo software",
    "country": "US",
    "language": "en",
    "engine": "google",
    "device": "desktop",
    "pages": [1]
  }'

Required request context

Most endpoints operate inside the active organization or an explicit {organizationId} path parameter. Before building an integration, confirm:

• the API key belongs to the organization you want to automate
• the key has the smallest required permission set
• the target organization has enough token balance and the needed product feature enabled
• search requests use the same country, language, engine, device, and SafeSearch rules your app workflow would use

Response shape

List endpoints return a { data, pagination } envelope. Object endpoints return the requested resource. Errors return a stable numeric code and a human-readable message, plus statusCode, timestamp, and path.

For the exact pagination envelope, the real rate limits, and the error codes, see Errors, Pagination, and Rate Limits.

Open in iSearchFrom

Open API Keys in the app. Create API keys in the app before building server-side integrations. Use the key only from trusted server code.

Related docs

Authentication and API KeysCreate and use API keys for server-to-server requests.

Errors, Pagination, and Rate LimitsHandle list responses, failures, and request limits.

Search ParametersUnderstand shared search settings used by API endpoints.

WebhooksReceive campaign alert events at your own endpoint.

MCP ServerLet an AI agent call iSearchFrom directly over the Model Context Protocol.