• Introduction
    • Enrichment
      POST
    • Deanonymization
      POST
    • Linkedin to Phone
      POST
    • Linkedin to HEM
      POST
    • Email to HEM
      POST
    • IP to Company
      POST
    • Organization Domain Finder
      POST
    • Keyword to Lead
      POST

    Introduction

    Getting Started#

    Welcome to the Springbolt Lead Resolution API documentation. Our API is designed to handle high-throughput Lead Identity Resolution (LIR), visitor deanonymization, contact data enrichment, and organization domain resolution.
    This guide covers the essentials you need to authenticate and start integrating our endpoints into your application.

    🔒 Authentication & Login#

    All endpoints in the Springbolt APIs requires authentication via API Key.
    We use the standard Bearer Authentication scheme. You must include your token in the Authorization header of every HTTP request.

    How to Authenticate#

    1.
    Obtain your Token: Log into your Springbolt Dashboard to get your active API key.
    2.
    Set the Header: Add the Authorization header to your request.
    3.
    Format: The value must strictly follow the format: Bearer <your_token>.

    Request Example#

    Here is a standard example of how to construct your request headers to authorize an API call:
    Next
    Enrichment
    Built with