Changelog

Added the Sub-Accounts API to the reference

Partner accounts can provision and manage customer accounts over the API. POST /v1/sub_accounts creates a sub-account and returns an initial sandbox API key, GET /v1/sub_accounts lists and filters them, and PATCH /v1/sub_accounts/{id} activates or deactivates one. Deactivating a sub-account makes its API keys return 401 while retaining its data and keys, and re-enabling restores access. external_id acts as an idempotency key unique within the parent account, so repeating a create with the same value returns the existing sub-account with 200 instead of creating a duplicate. A sub-account inherits the parent’s products by default; set inherit_products_from_parent to false to manage products independently. Separate endpoints list, create, and revoke sub-account API keys; treat every returned key value as a secret and rotate by creating a replacement, cutting traffic over, then revoking the old key. Available to accounts configured for sub-account provisioning. View the Sub-Accounts API reference.

Fixed the submitted address key in business creation examples

Address lines on POST /v1/businesses are address_line1 and address_line2. Some examples and the request schema showed address_line_1 and address_line_2, which the API ignores, so an address submitted with the underscored keys was accepted without its street lines. Check any integration built from those examples and send address_line1 and address_line2. View the connections guide.

Added sandbox support for Smart populate website lookups

POST /v1/prefill/businesses with website_url returns a business profile in sandbox instead of null. Sandbox derives the business from the submitted domain, so any domain returns a usable profile, and a domain that maps to a sandbox test business returns that business. industry_classifications is null unless the account uses enhanced sandbox data. Integrations can exercise the website lookup path before moving to Production. Production behavior is unchanged. View the Smart populate guide.

Fixed stale submitted phone numbers and email addresses after an update

The submitted object on a Business reflects phone numbers and email addresses sent on a later PATCH /v1/businesses/{id}. Previously submitted.phone_numbers and submitted.email_addresses kept the values from business creation, so a business updated with a new number or address still reported the original one. No integration changes are required. View the Business object reference.

Added International Business Verification

Middesk verifies businesses registered outside the United States and returns their registrations in the same format used for US Secretary of State data. Add an international_business_verification order when you create a business, optionally supply known registration numbers in the registrations array, and use POST /v1/businesses/{id}/registrations to add a registration to an existing business. Available to accounts with International Business Verification enabled. View the international verification guide.

Added Risk Assessment response schemas

The Risk Assessments API now documents the full assessment response, including dimensions, identifier_assessments, score, level, title, description_markdown, and the business snapshot link. Use the guide to retrieve the scored assessment behind a Business risk verdict. View Risk Assessment API guide.

Added jurisdiction validation to lien filing requests

Lien filing requests now reject unsupported jurisdictions before submission. Use the credit product jurisdiction coverage guide to confirm where lien filing, lien search, bankruptcy, litigation, criminal, and tax lien products are supported. View jurisdiction coverage.

Added webhook event schemas for business webhook payloads

Webhook event schemas let you configure which fields Middesk sends in the data.object of business webhook events while preserving the existing event envelope. Use the API or Dashboard schema builder to create, validate, and preview schemas before saving. View webhook guide.

Deprecated: orders[].package field

The orders[].package field is deprecated in favor of orders[].product. Requests that include orders[].package will continue to work but will return a deprecation warning in the response. Update your integration to use orders[].product, as orders[].package will be removed in a future release.

Enhanced Sandbox Preview

New enhanced sandbox mode available in Technology Preview. Define custom test businesses and use pre-built scenario templates to simulate specific verification outcomes directly from the Dashboard. Request access or view the enhanced sandbox guide.

Agents API

New API to retrieve specific agent details or a list of available agents on your account. Each agent has a defined type and set of capabilities for resolving business verification signals. View API reference.

Threads API

New API to create and manage agent threads. A thread holds context and history for agent work, typically associated with a business_id. Use threads to maintain state across multiple agent runs for the same Business. View API reference.

Autocomplete API

New Autocomplete API returns real-time, structured business suggestions based on partial name input—including names, addresses, people, and entity type. Integrate directly into your frontend to help users quickly find and select businesses during onboarding. View integration guide.

Smart populate API

GraphQL Preview

New GraphQL API available in Technology Preview. Query business verification data with nested relationships in a single request, reducing typical workflows from 3-5 sequential calls to one declarative query. Request access or view the GraphQL API reference.