API Reference: B2B Company Enrichment API

Complete reference for the B2B Company Enrichment API. For a hands-on introduction, start with the Quickstart.

Base URL:

https://b2b-enrichment.p.rapidapi.com

---

Authentication

Every request to POST /api/enrich requires an API key in the X-API-Key header. Get your key by subscribing on RapidAPI.

X-API-Key: YOUR_API_KEY

The GET /api/health endpoint does not require authentication.

---

Endpoints

POST /api/enrich

Enrich a single company. Returns structured profile data based on the company's public website.

Request Headers

Request Body

Company input formats:

Use a URL or domain whenever possible. Name-only lookups depend on a simple .com guess and may fail for companies with non-obvious domains.

Supported Fields

Any field the API cannot determine from the public website is returned as null.

Success Response (200)

{
  "success": true,
  "data": {
    "name": "Stripe",
    "domain": "stripe.com",
    "industry": "Fintech / Payments",
    "size": "5001-10000",
    "description": "Stripe builds financial infrastructure and payment software for internet businesses.",
    "techStack": ["React", "Ruby", "Go", "AWS"],
    "socialLinks": {
      "linkedin": "https://www.linkedin.com/company/stripe",
      "twitter": "https://twitter.com/stripe",
      "github": "https://github.com/stripe"
    },
    "founded": "2010"
  },
  "metadata": {
    "source": "https://stripe.com",
    "enrichedAt": "2026-03-22T10:00:00.000Z",
    "responseTimeMs": 3200,
    "tokensUsed": 1250,
    "fieldsRequested": ["name", "domain", "industry", "size", "description", "techStack", "socialLinks", "founded"]
  }
}

Metadata Object

Error Responses

All errors follow this shape:

{
  "success": false,
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable description"
  }
}

Example error responses:

Missing company:

{
  "success": false,
  "error": {
    "code": "INVALID_REQUEST",
    "message": "company is required"
  }
}

Invalid fields:

{
  "success": false,
  "error": {
    "code": "INVALID_REQUEST",
    "message": "Invalid fields: location, revenue. Valid fields: name, domain, industry, size, description, techStack, socialLinks, founded"
  }
}

Rate limited:

{
  "success": false,
  "error": {
    "code": "RATE_LIMIT_EXCEEDED",
    "message": "You have exceeded 10 requests per minute."
  }
}

---

GET /api/health

Health check endpoint. No authentication required.

Response (200)

{
  "status": "ok",
  "service": "B2B Company Enrichment API",
  "version": "1.0.0",
  "timestamp": "2026-03-22T10:00:00.000Z"
}

---

Rate Limits

The API enforces 10 requests per minute per API key.

Every response (success and error) includes rate-limit headers:

When you hit the limit, the API returns HTTP 429 with the RATE_LIMIT_EXCEEDED error code. Read the X-RateLimit-Reset header to know when to retry.

Batch processing tip: Space requests at least 6 seconds apart to stay within the 10/min limit. For higher throughput, upgrade your plan for increased burst limits.

---

CORS

The API supports cross-origin requests:

Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET, POST, OPTIONS
Access-Control-Allow-Headers: Content-Type, X-API-Key

Browser-based applications can call the API directly. OPTIONS preflight requests return HTTP 204 with the appropriate CORS headers.

---

Response Times

Typical response times range from 2 to 8 seconds, depending on:

• Target website load speed
• Number of fields requested
• Server-side model processing time

The metadata.responseTimeMs field in each response tells you the exact processing time. Set client-side timeouts to at least 30 seconds to account for slow target websites.

---

Troubleshooting

Company name returns INVALID_REQUEST

Name-only lookups guess the domain by slugifying the name and appending .com. This fails for companies with non-obvious domains (e.g., Meta → meta.com works, but Notion → notion.com works while Linear might not). Always prefer domains or URLs.

Fields return null

The API extracts data from the company's public website. If the site doesn't expose certain information (founding year, team size), those fields return null. This is expected behavior, not an error.

SCRAPE_FAILED on a valid website

Some websites block automated requests with CAPTCHAs, bot detection, or geo-restrictions. The API uses a standard User-Agent and does not bypass anti-bot measures. Try the company's main domain rather than a subdomain.

ENRICHMENT_FAILED (422)

The website loaded but had less than 50 characters of extractable text content. This happens with JavaScript-heavy single-page apps that don't render content server-side, or with login-gated pages.

Tech stack looks incomplete

The API detects technologies from client-side signals: script tags, framework-specific attributes, meta tags, and known third-party domains. Server-side technologies (databases, backend frameworks) are only detected when mentioned in the page content.