Leadfeeder API
    • Introduction
    • Authentication
    • Getting Started
    • Rate Limits
    • Relationships
    • Company ID Lifecycle
    • OpenAPI Specification Access
    • List of NACE / WZ codes
    • List of Industries
    • Account
      • List Accounts
    • Companies
      • Get Company Details
      • Retrieve Companies
      • Company Financial Reports
      • Search Company Signals
      • Search Companies
      • Match Companies
      • Retrieve Company IPs
      • Add Company to Lists
      • Remove Company from Lists
      • Assign Tags to Company
      • Unassign Tags from Company
    • Contacts
      • Get Contact Details
      • Retrieve Contacts
      • Search Contacts
      • Add Contact to Lists
      • Remove Contact from Lists
    • Web Visits
      • How to Create Custom Feed
      • Custom Feed - Filter Reference
      • Search Web Visits
      • Retrieve Custom Feeds
      • Create a Custom Feed
      • Get Custom Feed Details
      • Update Custom Feed
      • Delete a Custom Feed
      • Retrieve Custom Feeds Folders
      • Retrieve Web Visits Tracker Script
      • Retrieve Visitor Companies
    • IP
      • Enrich Company IP Address
    • Buyer Personas
      • Retrieve Buyer Personas
      • Get Buyer Persona Details
    • Ideal Customer Profiles
      • Retrieve Ideal Customer Profiles
      • Get Ideal Customer Profile Details
    • Tags
      • Retrieve Tags
      • Create Tag
      • Get Tag Details
      • Update Tag
      • Delete Tag
    • Lists
      • Retrieve Lists
      • Create a List
      • Get List Details
      • Update List
      • Delete List
    • Custom Fields
      • Retrieve Custom Fields
      • Create Custom Field
      • Get Custom Field Details
      • Update Custom Field
      • Delete Custom Field
    • Usage
      • Get Endpoints Usage
    • Schemas
      • VisitLocationV1
      • LocationV1
      • CRMUserV1
      • CRMOrganizationV1
      • ICPV1
      • CRMContactV1
      • IpAddressExtendedV1
      • CompanyIpV1
      • CRMLeadV1
      • WebVisitV1
      • BuyerPersonaV1
      • CRMConnectionV1
      • CRMSuggestionV1
      • IpLocationV1
      • CRMGroupConnectionV1
      • CustomFeedRequestV1
      • AccountV1
      • MaskedContactSummaryV1
      • CustomFeedV1
      • CustomFeedFolderV1
      • WebVisitsTrackerScriptV1
      • CompanyLocationV1
      • AccountSummaryV1
      • ErrorObjectV1
      • MaskedCompanySummaryV1
      • CompanyV1
      • NetworkV1
      • CompanyFinancialsV1
      • SignalV1
      • CompanySummaryV1
      • TagV1
      • ListV1
      • CompanyMatchV1
      • CustomFieldV1
      • ContactV1
      • ContactSummaryV1
      • EnrichedIpV1
      • ApiUsageV1

    OpenAPI Specification Access

    The Leadfeeder API provides publicly accessible endpoints that expose the OpenAPI specification and metadata used to generate the API documentation.
    These endpoints allow developers and tools to programmatically retrieve the API schema, enabling use cases such as:
    Powering LLM-based tools and AI agents that require structured API schemas for function calling or tool usage
    Generating client SDKs
    Importing the API into API tools (e.g., Postman, ApiDog, Insomnia)
    Validating requests against the official schema
    Building automated integrations

    Available Endpoints#

    OpenAPI Schema#

    GET https://api.leadfeeder.com/openapi.yaml
    Returns the OpenAPI specification used to power the public API documentation in YAML format.
    This endpoint provides the full machine-readable API schema including:
    Available endpoints
    Request parameters
    Response schemas
    Authentication requirements
    Error formats
    This endpoint is useful when importing the Leadfeeder API into API development tools, or generating SDKs.

    OpenAPI Schema Alias#

    GET https://api.leadfeeder.com/.well-known/openapi.yaml
    This endpoint is an alias of the primary OpenAPI schema endpoint.
    It exists to support tooling and integrations that expect the OpenAPI specification to be available under the .well-known path.
    The response content is identical to:
    https://api.leadfeeder.com/openapi.yaml

    API Metadata#

    GET https://api.leadfeeder.com/
    Returns basic API metadata describing the API service.
    This endpoint can be used by tools or developers to verify that the API service is reachable and to retrieve general information about the API environment.
    The metadata includes information such as:
    Version
    Link to .yaml
    Description

    Common Use Cases#

    Using with LLMs and AI Agents#

    The OpenAPI specification can be used to enable LLM-powered integrations, where models interact with the Dealfront API via structured tool definitions.
    Common patterns include:
    Converting the OpenAPI schema into tool/function definitions for LLMs
    Enabling AI agents to query Dealfront data autonomously
    Supporting natural language interfaces on top of the API
    This is particularly useful for:
    Internal AI copilots
    Workflow automation agents
    Conversational data access tools

    Importing the API specification into API Tools#

    Many API tools allow you to import an API specification directly from a URL.
    To do this, you can use the following schema endpoint:
    https://api.leadfeeder.com/openapi.yaml
    Examples of tools supporting this workflow include:
    ApiDog
    Postman
    Insomnia
    Swagger UI

    Generating Client SDKs#

    The OpenAPI specification can also be used to generate API clients automatically using tools such as:
    OpenAPI Generator
    Swagger Codegen
    This enables faster integration with the Dealfront API in most major programming languages.
    Modified at 2026-03-25 10:06:10
    Previous
    Company ID Lifecycle
    Next
    List of NACE / WZ codes
    Built with