GET/v1/schema1 unit

Filter schema

Self-describing JSON. Lists every customer-facing endpoint, the filters each one accepts (with type, match semantics, and examples), the response fields each one returns, and cost units. Pull this on first integration to drive client-side validation or code generation - the prose docs are written for humans, this is for code.

Request

curl -H "Authorization: Bearer $LEADLEAP_KEY" \
  https://data.leadleap.net/v1/schema

Response shape

One endpoints array. Each entry has the path, method, purpose, cost in units, plus (where applicable) a filters array and a response_fields array.

{
  "version": "v1",
  "endpoints": [
    {
      "path": "/v1/companies/search",
      "method": "POST",
      "purpose": "Company search across the enriched directory...",
      "cost_units": 2,
      "filters": [
        { "name": "country", "type": "string[]", "match": "exact (ISO alpha-2)",
          "narrowing": true, "example": ["US","GB"] },
        { "name": "business_model", "type": "string", "match": "ilike contains",
          "narrowing": true, "example": "B2B SaaS",
          "values_hint": ["B2B SaaS","B2C","Marketplace","Platform","Services"] },
        { "name": "year_founded_min", "type": "integer", "match": ">=",
          "narrowing": true, "example": 2015 },
        ...
      ],
      "narrowing_requirement": "At least one narrowing filter required. ...",
      "response_fields": [
        { "name": "domain", "type": "string", "note": "primary domain" },
        { "name": "firm_type", "type": "string",
          "note": "AI-classified company type (Software Company, Marketplace, etc.)" },
        { "name": "business_model", "type": "string" },
        ...
      ],
      "example_request": { ... }
    },
    {
      "path": "/v1/companies/by-domain/{domain}",
      "method": "GET",
      "cost_units": 10,
      ...
    },
    ...
  ],
  "auth": { "scheme": "Bearer", "header": "Authorization: Bearer <your-llk_ext_ key>" },
  "rate_limits": { ... },
  "query_limits": { ... },
  "deprecated": { "/v1/find": { "sunset": "2026-06-16", ... } }
}

Why use it

Programmatic filter discovery. If you're generating client types or rendering a filter UI, this is the source of truth - prose docs lag.
Cost reconciliation. Every endpoint surfaces its cost_units. Match against X-Endpoint-Cost-Units on every response.
Deprecation early-warning. The deprecated block lists endpoints with sunset dates so your client can show a deprecation banner before the endpoint goes away.
Response-field discovery. Each endpoint declares what fields you can expect on a result row, with type + brief note.

What you see at data.leadleap.net/v1/schema is the entire customer-facing API: every endpoint, every filter, every accepted value type, every cost unit. Generate types from this, render filter UIs from this, validate requests against this.

See /v1/companies/search for the marquee endpoint, and Rate limits for cost mechanics.