extractor.sh

API keys

Sign in on the web. Use keys in integrations.

The public GET APIs allow 10 successful uncached operations per IP each UTC day without an account. New free accounts receive a one-time welcome bonus of 1,000 credits.

Website tools

After signing in, the homepage form and platform playgrounds automatically use your account balance through the secure Hanko session. You do not need to expose an API key to the page.

Create a key for integrations

  1. Sign in to the private dashboard.
  2. Create a named API key. Each account can have up to two active keys.
  3. Copy the complete ext_live_… value immediately. It is shown once and stored only as a cryptographic hash.

Send a key

curl --get 'https://extractor.sh/api/extract'   --header 'Authorization: Bearer ext_live_your_key'   --data-urlencode 'url=https://example.com/'

Use the same optional header for /api/search, /api/news, /api/images, /api/places, and compatible remote MCP clients. Never put a key in a URL or query parameter.

Cache-first behavior

The shared cache is checked before authentication. A hit is free and can be returned even when a supplied key has since been revoked. On a miss, an invalid or revoked key returns 401. Successful cacheable work uses one account credit; errors refund the reservation. When the balance is empty, the API returns 402.

Revoke a key

Revoke keys in the dashboard. Revocation applies immediately to uncached requests. Rotate a key whenever it may have been exposed.