Federation partners can now register a single webhook endpoint at the Federation level, receiving events across all organizations and environments under their Federation.

Previously, webhook endpoints could only be registered per Organization - requiring partners to manage a separate endpoint and signing secret for each customer. The new Federation-level endpoint eliminates this overhead: one endpoint, one signing secret, all events.

Each event payload includes an enriched __event__ envelope with external_id, organization_id, application_id, and application_type fields so you can route events to the correct customer in your system.

To pre-filter delivery before events reach your endpoint, you can configure channels at creation time. Available filters include production, sandbox, Organization.<organization_id>, and Application.<application_id>. Filters can be combined.

Federation webhook endpoints can be created via the console under My Federation > Webhooks & Logs, or programmatically via POST /webhooks using your Federation API key.

For full implementation details, see the Organization Management guide.

We've optimized the web presence analysis pipeline to reduce end-to-end latency on website discovery and web scraping.

You should see noticeably faster turnaround on Web Presence and Business Search requests.

Business search and TIN verification responses now include a tin_match_type field, returning the specific type of match according to the IRS.

The possible values are EIN, SSN or UNKNOWN.

This gives you more granular insight into TIN verification results beyond a simple pass/fail, making it easier to build nuanced decisioning logic around TIN checks.

Identifying sole proprietors or individuals who have submitted a SSN in their business applications is now possible.

Reach out to your Baselayer representative for more information.

Baselayer now screens against the HHS Office of Inspector General (OIG) List of Excluded Individuals/Entities (LEIE).

The HHS OIG LEIE is a public database of individuals and organizations banned from participating in federal healthcare programs (Medicare, Medicaid) due to fraud, patient abuse, or felony convictions. Hiring an excluded entity results in civil monetary penalties.

This new watchlist source automatically surfaces in all Business Search and Person Search results alongside existing OFAC, PEP, and other sanctions checks.

No integration changes required: the new dataset is included automatically.

Web presence analysis now incorporates directory listings — such as BBB, Yelp, and Yellow Pages — as a first-class data source.

What this means for your results:

• Directory listings are now used to identify the correct business website
• Officer information is extracted from directory profiles
• Contact details (address, phone, email) found on directories are validated and matched

options: ["Order.DirectoryListings"] is now a new option in the payload that will retrieve third-party directories where the searched business appears listed.

The new found_directory_listings will return an array of objects like this one:

"found_directory_listings": [
        {
          "source": "artisanhub.co.uk",
          "url": "https://artisanhub.co.uk/store/artisan-island-ltd/?page=1",
          "category": "Consignment Store",
          "business_name": "Artisan Island Ltd",
          "phone_number": null,
          "email": null,
          "business_website": null,
          "address": "41 ST MARY STREET WEYMOUTH ENGLAND DT4 8PU UNITED KINGDOM",
          "people": []
        }
      ],

Additionally, a new DIRECTORY_LISTING source type will appear in web presence fields such as address_match_sources wherever directory data contributed to a match.

You can request directory listings via API or the console:

Contact your Baselayer representative if you'd like to learn more.

The web presence response now includes address_match_sources, phone_match_sources, email_match_sources, and people_match_sources fields.

These arrays tell you exactly which online source (one or multiple) confirmed each piece of contact information. Possible sources include:

INPUT_WEBSITE — the website you provided FOUND_WEBSITE — a website discovered during analysis SOCIAL_PROFILE — a social media profile REVIEW — an online review platform DIRECTORY_LISTING — a directory listing (e.g., BBB, Yelp)

This gives you full transparency into where Baselayer found matching data, making it easier to assess confidence in each data point.

We've improved the validation and matching logic for online reviews discovered during web presence analysis.

Review attribution is now more robust, reducing false positives and increasing the reliability of review-based signals in your results.

Batch search processing has been upgraded for improved reliability and scalability.

What's changed:

• On-demand execution and progress tracking of search batches is now supported
• CSV and JSONL generation for batch results has been updated in the console
• Better error handling for malformed CSV rows and input validation at the API tier

Now you can download and review the results of a batch search directly from the console.

Once the batch search is completed, a download can be requested to retrieve:

• CSV results
• JSONL results
• README with data dictionary

If you're already using batch searches via API, no integration changes are required.

Web presence requests now offer more granular options:

• Order.WebsiteAnalysis — in-depth analysis on the website you search, and the website we find
• Order.IndustryPrediction — industry/NAICS Code predictions for the business
• Order.Socials — social profile discovery and analysis
• Order.ReviewSummary — review platform discovery with summary data
• Order.ReviewFull — full review details including individual review text

This lets you request only the web presence components you need, giving you more control over search scope and cost.

Order.Enhanced continues to work as before for backward compatibility. However, we would recommend switching to the following request format:

options: ["Order.WebsiteAnalysis", "Order.SocialMedia", "Order.ReviewSummary"]

Please contact your Baselayer representative if you have any questions.

Lien search results now include a match_level field indicating how closely a lien filing matches the searched entity.

Possible values are EXACT (precise legal-name match) and SIMILAR (fuzzy match or name variant).

The underlying similarity calculation has also been improved, making it easier to quickly assess which lien results are most relevant to the entity you searched.

We recommend using match_level based on your operational priorities: use EXACT for high-velocity, automation-heavy flows where minimizing noise is key, and include SIMILAR matches when thoroughness is the priority — such as mid to large-ticket underwriting or deep due diligence.

For a full breakdown, see our Litigation & Bankruptcy Search: Best Practices guide.