> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.middesk.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.middesk.com/_mcp/server.

## Business Verification / API

### Order Enhanced Screenings with International Verify

Enhanced Screenings now accepts an `international_business_verification` order as its prerequisite. Include both products in the `orders` array when you create a business, or add Enhanced Screenings later with `POST /v1/businesses/{business_id}/orders`, whether the International Verify order is pending or completed. On a business with only an International Verify order, screening starts after International Verify completes. Enhanced Screenings without an Identity, Verify, or International Verify order still returns an error. Requires access to both products. [View the international verification guide](/verify-business/international).

### Submit a person's NPI and get a People NPI Match review task

`people[].npi` accepts a person's 10-digit National Provider Identifier when you create a business with `POST /v1/businesses`. Middesk looks up the number in the CMS NPPES individual-provider registry and returns a `person_npi_match` review task (label `People NPI Match`) alongside People verification. The task reports Found, Mismatch, Not Found, or Inactive for each submitted person, and appears only when at least one person has an NPI. A malformed NPI returns `400` with `parameter` set to `npi`, and the submitted value is echoed as `npi` on the person. In sandbox, the NPI lookup returns no record. [View the create a business reference](/api-reference/business-verification/businesses/create-business).

### Test property type address risk in sandbox

Sandbox addresses that include **residential** or **commercial** in `address_line1` or `full_address` return a `property_type` address risk indicator with a `residential` or `commercial` value. If both words appear, `residential` takes precedence. Other sandbox addresses are unchanged. [View the sandbox trigger values](/environments#address-statuses).

## Monitoring / Webhooks

### Added `historical` to `bankruptcy.created` events

`bankruptcy.created` events from Bankruptcy Monitoring V2 include `data.object.historical`. The value is `false` when the filing date is on or after the monitoring cutoff, the later of the date the business's bankruptcy monitor was enabled and the date Bankruptcy Monitoring V2 was enabled for your account. It is `true` when the filing predates the cutoff or has no filing date; Middesk sends these events only to accounts opted into historical bankruptcy alerts. Events from legacy bankruptcy monitoring omit the field, so treat a missing value as unknown rather than `false`. [View the bankruptcy monitoring reference](/api-reference/business-verification/monitoring/create-business-monitor).

## Entity Management / API

### Unsupported `tax_registration_types` return `400`

`POST /v1/partner/registration_requests` returns `400` with `parameter` set to `tax_registration_types` when the request includes an unsupported type. Supported values are `state_unemployment_insurance` and `state_tax_withholdings`; when omitted, the request defaults to the types available in the requested state. Previously these requests could fail with a server error. Invalid requests no longer create an account, company, or user. [View the create registration request reference](/api-reference/entity-management/registration-requests/create-registration-request).