Skip to main content
The SphereScout REST API gives you programmatic access to the contact database. Use it to search and filter millions of business contacts by location, category, and contact method; stream results into your CRM; trigger CSV exports; and manage API credentials — all over standard HTTPS with JSON request and response bodies.

Base URL

All API endpoints are served from a single origin:
Every endpoint lives under the /api/ path prefix. For example, the company search endpoint is:

Authentication methods

The API supports two ways to authenticate requests. Both use the same Authorization: Bearer header format.
For integrations and server-side scripts, use API keys. They are simpler to manage and do not require a token-refresh cycle.

Request format

All requests that include a body (POST, PATCH) must send JSON and set the Content-Type header accordingly:
GET requests pass parameters as URL query strings. Boolean filters use the string values "true" and "false".

Quick example

The following request searches for contacts in France who have an email address on file:

Search and export flow

Exporting contacts is a two-step process: you first run a search to define the result set, then trigger an asynchronous CSV export against that search and poll until the file is ready.
1

Run a search

Call GET /api/companies with the filters that describe the contacts you want (country, category, contact method, etc.). The response includes a totalCount, a paginated preview of results, and a search_id that uniquely identifies this query.Use the search_id to drive the export — there is no need to re-send the filters.
Response
2

Initiate the CSV export

Call GET /api/download-csv?search_id={search_id} to enqueue the export. This endpoint is asynchronous: it returns immediately with a task_id that identifies the background job — it does not return the CSV itself.
Response
3

Poll for completion

Call GET /api/download-status/{task_id} periodically until status becomes ready. We recommend polling every 2–5 seconds with exponential backoff; most exports complete in under a minute, but large result sets can take longer.Possible status values:
Ready response
4

Download the CSV

Fetch the file from the download_url returned in the previous step. Links remain valid for 30 days; after that, regenerate the export from your search history.
Re-running the same search returns the same search_id for a short window, so you can safely retry step 1 if the network drops. The task_id from step 2, however, is unique per export — always poll the exact task_id you received.

Rate limits

The API enforces rate limits to ensure availability for all users. Specific thresholds depend on your plan. Contact support for rate limit details relevant to your account.

Endpoint reference

The table below groups the public API surface by category.

Authentication

Account

API key management

Reference data

Exports

Export history

Next steps

API keys

Generate and manage long-lived API credentials for server integrations.

Authentication

Learn the full JWT login flow and token-refresh cycle.