Use of this API is governed by your contract terms. Please consult with your Markaaz Account Manager if clarification is required.

Markaaz Verification APIs require a markaazId, which can initially be retrieved via the Advanced Match or Search APIs. This may be a markaazId retrieved in real-time via an integration workflow, or previously retrieved and saved.

Typical Verification Request

{
	"markaazId": "1020000028206755"
	"epInternalId": "123"
}

Verification APIs: Response Parameter Guidance

Complete API response specifications can be found on the Markaaz Developer Portal. Below is a selection of guidance highlights for each API.

Note that all Verification API responses include the bizInfo object, which includes the same core business data (name, address, etc.) returned with Advanced Match and Search responses.

Compliance Details

Field	Values	Definition	Recommendation and Business Context
`activeInsolvency`, `insolvencyIdNumber`	integer, string	Count of objects in the `insolvency` array of the API response. Each object contains details of a specific insolvency indicated by an `insolvencyIdNumber`.	`activeInsolvency` may be different than the bankruptcy indicator in the Business Health API response. Markaaz sources these two indicators differently. A company fresh out of bankruptcy may be a great target, while insolvency is a sign of potential future bankruptcy filing.

Firmographic

Field	Values	Definition	Recommendation and Business Context
`legalStructure`	Values vary by country.	A localized description of a business legal structure.	Markaaz does not alter or transform this data; it is reported exactly as we receive it from authoritative sources. To mitigate false positives, Markaaz will work with the customer to define a mapping between returned values and the customer's system. For example: LLC, Limited Liability, Limited Liability Company, and Private LLC may all map to a single customer-defined value.
`companyStatus`	active, inactive	As reported to Markaaz via external registry data.	Markaaz does not determine active/inactive status on its own. The definition varies by country, influenced by the company's registration status (registered or non-registered) and the reliability of the registry's company status. For registered companies in countries with dependable registry statuses, the status is standardized to reflect various non-operational conditions such as bankruptcy, liquidation, or closure. For non-registered companies, or in countries where the registry does not provide a reliable company status, the company will be marked as inactive either when the registry indicates it is inactive, or when Markaaz receives information from third-party sources that the business is no longer operational.
`registrationDate`	yyyy-mm-dd	The date the business was registered with the government.	—
`salesVolume`	integer	Markaaz's view of a company's annual revenue.	Expressed in USD regardless of where the business operates. Conversion must be handled on the client side using your preferred exchange rates. Leverage the precision indicators below for source and confidence level.
`salesVolumePrecision`, `salesVolumeLocPrecision`	ACTUAL, EST, MDL	Actual: Audited figures. Estimated: In the absence of audited figures, estimates are otherwise provided by the company. Modeled: Based on the industry type and number of employees, we can model the revenue. Trends of the industry are factored into the model.	Use ACTUAL values whenever available. Best fit for any important decisions where precision matters. Treat EST and MDL values as directional — best fit for segmentation, prospecting, relative sizing, and coverage when reported data is unavailable.
`hasCompanyHierarchy`	yes, no	Indicates whether or not Markaaz has hierarchy data for this company.	If this field is "No", you should avoid calling the Company Hierarchy API; there is no company hierarchy to be discovered. Markaaz data models upwards hierarchy relationships, not downwards. A child entity will indicate a hierarchy entity above. A parent entity will not indicate a child entity below. The top result in an Advanced Match response is not necessarily the entity with associated hierarchy data.
NAICS (multiple fields)	strings per NAICS Classification System specs	These fields hold normalized industry codes across geographies. If a country does not use NAICS, their industry codes have been converted to the NAICS codes provided.	—
`businessSize`	S, L, X	S (small): Indicates all the attributes required for the computation were available and the business qualifies as small. The computation uses US SBA rules for determining small. If it is not calculated as small, it gets assigned as large. L (large): Indicates all the attributes required for the computation were available and the business does not qualify as small. X (unknown): Indicates one or more attributes required for the computation were missing.	Although not directly linked, customers may also choose to leverage `noOfEmployees` and `salesVolume` (also in the Firmographic response), or various values in the Financials Data response as signals of business size, based on the customer's business rules.
`officers` array — `currentStatus`	1, 2	1 = current, 2 = past	—

Business Health

Note that a missing risk score does not necessarily indicate stability or instability. For example, a small or newly formed business may not have enough credit or financial data available for a reliable risk assessment, or a location under a parent headquarters does not maintain its own credit history. Markaaz recommends using the risk indicators for segmentation, prioritization, and go-to-market optimization, not for credit decisioning.

Field	Values	Definition	Recommendation and Business Context
`bankruptcy`	Y or null	Indicates a history of bankruptcy.	This flag may detect bankruptcy filings before they appear in the risk rating. Note this indicator may be different than the `activeInsolvency` indicator in the Compliance Details API response. Markaaz sources these two indicators differently. A company fresh out of bankruptcy may be a great target, while insolvency is a sign of potential future bankruptcy filing, if cash flow becomes an issue again.
`markaazBusinessFailureRiskScore`	9–1, 0, or null (0 indicates bankruptcy)	Indicates the risk of failure. The higher the score, the greater the risk of failure (0 indicates bankruptcy).	`markaazBusinessFailureRiskScore` estimates the likelihood a business will cease operations or enter bankruptcy within the next 12 months.
`markaazCreditRiskScore`	103–600 or null	A USA business credit risk score. The lower the value, the greater the risk.	`markaazCreditRiskScore` estimates the directional likelihood that a business will become severely delinquent on a non-financial trade payment within the next 12 months. Lower scores (1–3) indicate higher payment risk, while higher scores (8–10) indicate lower risk. Markaaz recommends using `markaazBusinessFailureRiskScore` and `markaazCreditRiskScore` together — these indicators help teams segment and prioritize accounts, identify higher-risk businesses earlier, and support more effective GTM and revenue strategies. While both reflect important aspects of financial risk, they are directional signals for targeting and prioritization, not full business-health assessments or credit-decision tools.
`markaazGlobalCreditRiskScore`	1–5 or null	A normalized credit risk score. The lower the value, the greater the risk.	—

Company Hierarchy

At the top of most company hierarchy ladders are large public companies. Even when large shareholders of a public company are known (e.g. a pension fund owning a 15% stake, or a national government owning a 10% stake), hierarchy relationships beyond the topmost public company may not be available.

In the case of acquisitions, if the acquisition involves the legal dissolution of the acquired company, then company hierarchy does not apply; there used to be a company, and now there is not. However, if the acquisition does not change anything about the legal situation of the company (i.e. a change in ownership), then company hierarchy does apply. The acquired company is now a child entity of the acquiring company (which is now a parent, if it was not previously).

Markaaz data models upwards hierarchy relationships, not downwards. A child entity will indicate a hierarchy entity above. A parent entity will not indicate a child entity below.

Field	Values	Definition	Recommendation and Business Context
`parentMarkaazId`	string	Unique identifier for the parent company.	Capture this number to pass as `markaazId` in subsequent Verification API requests for further business data. These IDs do not change, so they can be stored long-term on the customer's platform and used again later to re-verify and see the most up-to-date data for a business. Markaaz's hierarchy data is dyadic, meaning we link only two entities together directly; these entities each have a unique ID. A parent company may have multiple direct children at the same time. A child company can have only one direct parent, but that parent can itself have parents, so the child can have multiple indirect parents.
`markaazId` (child company)	string	Unique identifier for the child company in the Markaaz Global Directory.	Capture this number to pass to subsequent Verification API requests for further business data.
`companyLegalName`	string	The company's legal/registered business name.	—
`contact`	object, strings	Contact information associated with the parent company (`parentMarkaazId`).	—
`parentTypeCode`	9000, 9001, 9002, 9003	9000 — Immediate Parent (aka Subsidiary Parent): The direct legal owner of the child entity. 9001 — Domestic Parent: The highest link in the legal ownership chain that is registered in the same country as the child entity. 9002 — Global Parent (aka Ultimate Parent): The highest link worldwide in the legal ownership chain. 9003 — Affiliate Global Parent: The highest entity worldwide with influence over the child entity, but NOT through direct legal ownership (e.g. a franchising model, a shared branding model, etc.).	Markaaz recommends using the hierarchy structure in various customer use cases summarized above. A parent entity may have one or more associated type codes — for example, a parent may be classified as both a domestic and global parent.
`companyName`	string	Business Name (DBA, or Legal Name if DBA not available).	—
`addresses`	object, strings	Address information associated with the parent company (`parentMarkaazId`).	—