We’ve launched two powerful new POST endpoints that allow you to query rich B2B contact and company data using highly flexible filters. This update enables users to programmatically retrieve structured data on millions of companies and decision-makers with pinpoint control.

Example Use cases:

1. Find sales leaders at Microsoft in California. Use filters like domain, department, and location to surface precise outreach targets—no manual research required.
2. Find every Chief Revenue Officer at $200M+ companies. Combine title and revenue filters to instantly identify senior buyers—ideal for pipeline building or TAM analysis.
3. Product Managers can build a contact suggestion feature. Show users the right people to reach out to when they land on a target account page—powered by dynamic queries to our B2B contact API.
4. RevOps teams can enrich contacts in a territory automatically. Run scheduled queries by geo, title, or company size to keep CRM records fresh and actionable—no CSVs required.

🧑‍💼 POST /filter-contacts

Search B2B contact records using attributes like:

• Demographic filters: FirstName, LastName, PersonalCity, PersonalState, PersonalZip, Gender, AgeRange, etc.
• Professional filters: JobTitle, Department, SeniorityLevel, LinkedInUrl
• Company context filters: CompanyDomain, CompanyName, CompanyNaics (partial support), and more

Each response includes rich fields like email, phone, LinkedIn, location, and job-level metadata. Supports pagination and sorting by fields such as FirstName, LastName, and UpId.

📄 View docs: Get Contacts

🏢 POST /filter-b2b

Retrieve B2B company records filtered by:

• Firmographics: CompanyName, Domain, Revenue, EmployeeCount
• Location: State, City, Zip, Country
• Industry & NAICS: PrimaryIndustry, CompanyNaics

These filters enable flexible firmographic targeting, great for GTM use cases like ICP building, TAM mapping, or competitive research.

📄 View docs: Get B2B Companies

✅ Highlights:

• Flexible Filters array for combining multiple field conditions
• Supports equals, not_equals, contains, and not_contains operators
• Pagination via Page and PageSize query params

We’ve introduced a new insight subtype that highlights where your prospects have lived or worked and where their company is headquartered. By revealing these geographic details, you can tailor your outreach to resonate with local references, market concerns, or regional events.

Key Features

Current Location: Understand exactly where a prospect is based today, so you can reference local events, communities, or news.
Past Locations: Quickly see prior places they’ve worked or lived, which might offer shared experiences or networking ties.
Company HQ: Recognize which region the company calls home, providing context for corporate culture, local market conditions, and potential scheduling considerations.
Contextual Relevance: Leverage location data to build stronger rapport, especially if you share a common location or have local customer references.
Customizable Control: Enable or disable location insights in your requests so you only get data when needed.

Example Usage

Generate Content API

{
  "enabledInsights": ["workExperienceLocationProfile"],
  "disabledInsights": []
}

When workExperienceLocationProfile is in enabledInsights, your API responses may include personalized mention of the prospect’s geographic history.

Generate Insights API

{
  "insightSubtype": "workExperienceLocationProfile"
}

Specify "insightSubtype": "workExperienceLocationProfile" to retrieve the new location profile insight directly.

Example Payload

Below is a sample data block illustrating the information we gather under the workExperienceLocationProfile subtype:

{
  "locationProfile": {
    "currentLocation": "Orange County, California, United States",
    "previousLocations": [
      "Greater Chicago Area",
      "Tel Aviv, Israel",
      "Herzliyya, Tel Aviv, Israel",
      "Ramat Aviv, Israel"
    ],
    "companyLocation": "Chicago, US"
  }
}

Example Output

"I noticed you’re currently in Orange County – we’re hosting a local event on creating pipeline with genAI. Thought you might be interested!"

By referencing a prospect’s move from Chicago to Orange County, for instance, you can spark meaningful dialogue that acknowledges their new region and establishes deeper rapport.

Unlock Location-Driven Personalization

Connect your data sources or CRM to automatically surface location context for every prospect. Whether you’re inviting them to an event, referencing a shared city, or acknowledging prior workplaces, the Work Experience Location Profile insight streamlines your ability to speak your prospect’s language in every outreach.

Our new Email History insight transforms your inbox data into actionable relationship intelligence. Now you can programmatically access comprehensive engagement metrics and conversation context with prospects across your entire organization.

Key Features:

• Complete Relationship View: Access metrics on total emails, response rates, and engagement patterns across all team communications
• Thread-Level Intelligence: Analyze which conversations gained traction with detailed metrics on each email thread
• Team-Wide Visibility: Track interactions between all team members and prospect organizations to identify the strongest relationship channels
• Clean, Structured Data: Receive optimized API responses focused on meaningful engagement, with threads categorized by response status
• Automated Processing: Connect your inbox at https://app2.autobound.ai/settings via OAuth (Gmail/Outlook supported) with nightly updates

Example Output:

Example response showing engagement metrics and thread details for a sales rep with an active prospect conversation about partnership opportunities:

{
  "metrics": {
    "total_emails": 20,
    "total_threads": 8,
    "auto_response_count": 0,
    "prospect_to_user": 5,
    "user_to_prospect": 2,
    "response_rate": "12.5%",
    "threads_with_responses": 1,
    "threads_without_responses": 7
  },
  "threads": {
    "responded": [
      {
        "thread_id": "abc123def456",
        "email_count": 3,
        "response_count": 1,
        "auto_responses": 0,
        "latest_from": "prospect@company.com",
        "latest_subject": "sync up?",
        "latest_date": "2025-02-25T20:22:15.000Z",
        "latest_body": "Let's sync up sometime this week? I want to see the platform and discuss potential partnership opportunities..."
      }
    ],
    "no_response": [
      {
        "thread_id": "xyz789uvw321",
        "email_count": 2,
        "latest_subject": "Product demo follow-up",
        "latest_date": "2025-02-20T14:30:22.000Z"
      }
    ]
  }
}

The API delivers both high-level metrics and granular thread details, including email content previews, enabling truly personalized follow-ups based on actual conversation history. Whether integrated into your existing workflow tools or accessed via our platform, Email History empowers sales teams to make data-driven decisions about when, how, and what to communicate to prospects.

Connect your team's inboxes today and transform random email exchanges into your most strategic sales asset.

We're excited to introduce our new Employee Breakdown & Growth insight, giving you valuable visibility into your prospects' organizational structure and priorities.

This insight provides:

• Detailed departmental headcount distribution
• Year-over-year growth rates across 25+ departments
• Overall company growth metrics (6-month, 1-year, 2-year)
• Smart analysis to quickly identify focus areas and strategic shifts

Use these metrics to create more relevant outreach by referencing actual organizational priorities, spotting departmental investments, and naturally connecting your solution to their growth areas.

Available now via employeeBreakdownAndGrowth subtype in both generate-insights and generate-content endpoints.

We've standardized the way you control insight generation across our APIs by improving our insightSubtypes parameter on the generate-insights endpoint. This brings the same granular insight control you're familiar with from generate-content endpoint to our generate-insights endpoint.

Feature Details

You can now specify which insights you want using the insightSubtypes array parameter in generate-insights requests, just like you do in generate-content:

{
  "insightSubtypes": [
    "companyMarketTrends",
    "behavioralProfile",
    "socialMediaProspectRecentLinkedInPosts"
  ],
  "contactEmail": "daniel@acme.com"
}

The API will return only the requested insight types in the response:

{
  "insights": [
    {
      "type": "companyMarketTrends",
      "value": "Acme Corp is experiencing 40% YoY growth in the enterprise segment...",
      "confidence": 0.89
    },
    {
      "type": "behavioralProfile",
      "value": "Decision maker who prioritizes ROI and technical excellence...",
      "confidence": 0.85
    },
    {
      "type": "socialMediaProspectRecentLinkedInPosts",
      "value": "Recently shared thoughts on AI adoption in manufacturing...",
      "confidence": 0.95
    }
  ]
}

Availability

This standardization is available in:

• generate-insights v3.2 and newer

We've added support for Gemini Flash 1.5 as a new model option while deprecating fine-tuned models across all endpoints. This update brings ultra-fast generation capabilities to our API while streamlining our model offerings.

New Model Details

The Gemini Flash 1.5 model offers:

• 1-3 second response latency
• High-quality output comparable to base models
• Optimized for high-volume requests and real-time applications

Example usage in generate-content

{
  "model": "gemini_flash_1.5"
}

Important Deprecation Notice

All fine-tuned model endpoints have been deprecated. Requests to these endpoints will now return an error. Please migrate your applications to use our base models instead.

Availability

This update is available on all active endpoints.

We've standardized our insight taxonomy to make it more intuitive and powerful. You can now use the same subtype names across both our generate-insights and generate-content APIs. Each request can include multiple subtypes, giving you more precise control over which insights appear in your responses.

Check out our complete list of available subtypes to see what's possible. Here's a quick example of using multiple subtypes in a single request:

{
  "enabledInsights": [
    "companyMarketTrends",
    "behavioralProfile",
    "socialMediaProspectRecentLinkedInPosts"
  ]
}

This standardization makes our APIs more predictable and easier to use while giving you more granular control over your insight generation.

Availability

This functionality is available in the following endpoints and onwards:

• generate-content v3.6
• generate-insights v3.2

Insight Control is a feature that allows you to manage which types of insights are included in responses from the generate-insights API.

As of today, only the insights toggled on will show when making a generate-insights query, assuming insightSubtype isn't used as a parameter.

By enabling or disabling specific insights, you can tailor results to align with your strategy.

1. Default Behavior: Retrieve Top 20 Insights

By default, when no insightSubtype is specified, the generate-insights API will return up to 20 insights ranked by relevance, but only from the types you have enabled in Insight Control.

2. Retrieve Insights by Subtype

If an insightSubtype is explicitly specified in your request (e.g., "podcast" or "financial"), the API will attempt to retrieve and return those insights even if the subtype is disabled in your settings.

Autobound's generate-insights API now offers enhanced precision with a new insightSubtype parameter, allowing users to request specific insight types for their contacts.

This new feature streamlines data retrieval by focusing on the exact insights users need, such as "Hiring SDRs" or "Negative quarterly revenue growth." Without specifying a subtype, the API will continue to return a ranked list of the 20 most relevant insights for the contact.

This update provides greater control and flexibility, enabling users to tailor their data requests for more targeted and effective sales outreach. Developers can easily implement this new parameter using a simple string input, and comprehensive error handling ensures smooth integration.

For a complete list of valid subtypes, refer to this Google Sheet.

Welcome to the developer hub and documentation for Autobound API! You can find info on recent API and schema improvements here.