API Docs Endpoint Extractor

Extract clean endpoint rows from API docs, snippets, OpenAPI-style text, and integration pages.

This actor is built for buyers who do not want a noisy scrape. It turns simple public text, snippets, or URLs into a compact dataset with only the fields that matter for the workflow. It is intentionally limited to clean, useful rows instead of dumping page text, actor names, internal scores, or duplicate metadata.

What it is best for

• Fast marketplace-ready research runs
• Lead qualification and enrichment workflows
• Competitive intelligence and monitoring
• CSV exports for sales, marketing, product, and operations teams
• AI-agent workflows that need predictable fields

Input

The input is intentionally simple:

• items - paste snippets, page text, job posts, review text, announcements, or public URLs.
• maxResults - choose how many rows to save, from 1 to 20.

You do not need selectors, CSS rules, browser settings, login cookies, or complicated configuration.

Output

Each saved dataset item contains only these useful fields:

• apiName - ApiName extracted or inferred from the supplied text.
• method - Method extracted or inferred from the supplied text.
• endpoint - Endpoint extracted or inferred from the supplied text.
• authType - AuthType extracted or inferred from the supplied text.
• parameters - Parameters extracted or inferred from the supplied text.
• rateLimit - RateLimit extracted or inferred from the supplied text.
• docsUrl - DocsUrl extracted or inferred from the supplied text.

Example input

{
    "items": [
        "Stripe API: GET /v1/customers requires Bearer token auth. Parameters include limit, email, starting_after. Rate limit: 100 requests per second.",
        "GitHub REST API endpoint POST /repos/{owner}/{repo}/issues supports token authentication and JSON body fields title, body, assignees.",
        "SendGrid endpoint PATCH /v3/marketing/contacts accepts API key auth and contact list identifiers."
    ],
    "maxResults": 3
}

Example output

{
    "apiName": "Stripe API",
    "method": "GET",
    "endpoint": "/v1/customers",
    "authType": "Bearer token",
    "parameters": "limit, email, starting_after",
    "rateLimit": "100 requests per second",
    "docsUrl": "manual input"
}

Why this actor is useful

Many scrapers return too much raw data. This actor is shaped for a buyer who wants a ready-to-use spreadsheet: one row per useful signal, clean columns, and no unnecessary filler fields. That makes it easier to plug into Google Sheets, Airtable, CRMs, lead scoring tools, research reports, and AI workflows.

Recommended pricing

Best model: Pay per event / per dataset item.

Recommended event: apify-default-dataset-item

Suggested price: $0.0035 per endpoint result.

This is predictable for users because every paid event maps to one visible dataset row.

Limitations

• The actor works best with public pages or pasted text.
• It does not bypass logins, paywalls, CAPTCHA, or private data restrictions.
• Fields are extracted from visible text and may need human review for high-stakes decisions.
• For very large monitoring jobs, split inputs into batches to keep results easy to inspect.

Categories

DEVELOPER_TOOLS, BUSINESS

Search keywords

api docs, endpoint extractor, developer tools, integration research