getapi-nl Site Scraping API
The Site Scraping API from getapi-nl — 1 operation(s) for site scraping.
The Site Scraping API from getapi-nl — 1 operation(s) for site scraping.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/getapi-nl:getapi-nl-site-scraping-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: GetApi Site Scraping API
version: 0.0.1
description: '## Authentication
All API endpoints require authentication. Include your API key in every request using **one** of the following methods:
**Option 1 — X-Api-Key header (recommended)**
```
X-Api-Key: ga_live_xxxxxxxxxxxxxxxxxxxx
```
**Option 2 — Bearer token**
```
Authorization: Bearer ga_live_xxxxxxxxxxxxxxxxxxxx
```
You can generate and manage API keys in your dashboard.
## AI & Agent Payments (x402)
Some endpoints support direct payments for AI agents via the **x402** protocol (https://www.x402.org).
No API key or account is needed. Send a normal request without key;
the server will respond with **HTTP 402** and a `PAYMENT-REQUIRED` header:
```
PAYMENT-REQUIRED:
```
This base64 string contains, among other things, `network`, `asset`, `amount`, and `payTo`.
Your agent signs an EIP-3009 *transferWithAuthorization* for the specified `amount` of USDC to that `payTo` address,
encodes the signature as base64, and resubmits the request with:
```
PAYMENT-SIGNATURE:
```
The server verifies the signature via a facilitator, provides the data, and settles the payment on-chain.
The success response includes a `PAYMENT-RESPONSE` header containing the transaction information.
A one-time `nonce` prevents replay attacks. Payments are made in USDC on **Base**;
the price is determined by the `credit_cost` of the endpoint.'
contact:
email: info@wdnoord.nl
x-guidance: 'GetAPI.nl is een Nederlandse API-platform voor lookups en validaties (postcode,
adres, kenteken, BTW, e-mail, KVK, IBAN, energiemaatwerk, overheidsdata). Elke
endpoint accepteert een API key via de X-Api-Key header of Authorization:
Bearer <key>.
Sommige endpoints zijn ook direct betaalbaar voor AI-agents via het x402-protocol
(https://www.x402.org) zonder account of API key: stuur een verzoek zonder key,
de server antwoordt met HTTP 402 en een PAYMENT-REQUIRED header (base64 JSON met
network, asset, amount, payTo). Teken daarna een EIP-3009 transferWithAuthorization
voor het gevraagde bedrag in USDC op Base en hertrail met een PAYMENT-SIGNATURE
header. De server verifieert, levert de data en settleert on-chain.
Tips voor agents:
- Lees eerst de PAYMENT-REQUIRED header van een 402-antwoord; die is leidend.
- Geef altijd de exact door de server gevraagde parameters mee.
- Een endpoint met een "x-payment-info" blok vereist betaling voor gebruik.'
servers:
- url: https://api.getapi.nl
description: GetAPI
security:
- ApiKeyAuth: []
- BearerAuth: []
tags:
- name: Site Scraping
paths:
/v1/scraping/email:
post:
operationId: scraping.email
description: 'Uses a simple regex to extract email addresses from the HTML content of a given URL. It is not always possible
to extract email addresses due to obfuscation techniques. In such cases, the api will try to decode it.
If it still fails, it will return an empty array. Leave feedback at info@wdnoord.nl if you have a webpage that
contains email addresses but they are not extracted correctly and we will try to improve the regex or
add support for the obfuscation technique used on that webpage.'
summary: E-mail Address Extractor
tags:
- Site Scraping
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
url:
type: string
format: uri
required:
- url
responses:
'200':
description: One or more email addresses found on the page
content:
application/json:
schema:
type: object
examples:
- found: true
emails:
- example@example.com
- info@example.com
properties:
found:
type: boolean
emails:
type: array
items:
type: string
required:
- found
- emails
'422':
$ref: '#/components/responses/ValidationException'
'404':
description: Not found
content:
application/json:
schema:
type: object
examples:
- found: false
emails: []
error: not_found
message: Niet gevonden.
properties:
found:
type: boolean
emails:
type: array
items:
type: string
error:
type: string
message:
type: string
required:
- found
- emails
- error
- message
components:
responses:
ValidationException:
description: Unprocessable content
content:
application/json:
schema:
type: object
properties:
error:
type: string
description: Machine-readable error code.
message:
type: string
description: Human-readable error message.
errors:
type: object
description: A detailed description of each field that failed validation.
additionalProperties:
type: array
items:
type: string
required:
- error
- message
- errors
securitySchemes:
ApiKeyAuth:
type: apiKey
in: header
name: X-Api-Key
BearerAuth:
type: http
scheme: bearer