Response categories
Each business risk response is built from sections you can request individually or run together.
Overview
A single POST /v1/business/risk call can return firmographics, filings, reviews, risk flags, a summary, and more. Each block of data is a response section, selected through the categories array on your request.
Which sections you can receive depends on what is enabled for your organization. Which sections you do receive depends on your request and that configuration together. See Your access for how contracts and entitlements work.
Your access
Access to response categories is set by your agreed contract with Relativity6, not by the API alone. Your organization’s enabled sections appear in categoryAccess.entitled on every business risk response. You can request any section name in categories, but only entitled sections are evaluated and returned.
Typical contract decisions include which data sections are in scope, whether property insights or specialized review configurations apply, and how your custom risk profile is maintained. If you need a section that is not enabled today, your account team can update your configuration after your agreement is amended.
Available sections
Use these values in the categories array:
| Request value | What you get |
|---|---|
firmographic | Legal identity, location, scale estimates, and industry classification |
reviews | Public review and rating data (see Reviews below) |
publicFilings | Corporate registrations, licenses, and related government filings |
adverseMedia | Negative news and media findings with supporting references |
digitalAssetHealth | Website security, technology, and digital risk signals |
corporateStability | Business history, longevity, and stability indicators |
riskAssessment | Custom risk flags from your organization’s active risk profile |
summary | Business description, overall risk verdict, and section-level review |
propertyInsights | Property and co-tenant context when enabled for your account |
If a section is not enabled for your account, it will not appear in categoryAccess.effective even if you request it. Sections you are not contracted for remain unavailable until Relativity6 updates your organization configuration.
Requesting sections
Run everything you are entitled to — omit categories. The API runs all sections enabled for your organization.
Run a subset — send a categories array with the section names you need:
Request three sections
Only sections that are both requested and entitled are included. Unknown section names return HTTP 400.
Request nothing — send categories": []. The API runs no sections and returns an empty company object (aside from metadata). Use this only when you intentionally want a no-op assessment.
Custom risk flags use two different controls
| Control | What it does |
|---|---|
categories (include riskAssessment) | Turns the risk-flag section on or off in the response (company.riskAssessment). Same idea as requesting firmographic or summary. |
category_filter / flag_filter | Optional. Only apply inside riskAssessment. They limit which profile groups or named flags are evaluated — they do not add response sections. |
To run any custom flags, include riskAssessment in categories. To run only part of your profile (for example one flag group), add filters on the same request — see Risk profiles.
Do not put profile group names in categories. Those belong in category_filter.
Reviews
Send reviews in categories whenever you need review and rating data. You do not need to request onlinePresence or publicReviews separately.
The API maps reviews to the review section enabled for your organization. The response appears under company.onlinePresence or company.publicReviews, never both.
"categories": ["firmographic", "reviews", "summary"]
If review data is not enabled for your organization, reviews is omitted from the response.
categoryAccess in the response
Every response includes categoryAccess so you can see what happened:
{
"requested": ["firmographic", "riskAssessment"],
"entitled": ["firmographic", "riskAssessment", "summary", "publicFilings"],
"effective": ["firmographic", "riskAssessment"]
}
requested— what you asked for (empty if you omittedcategories)entitled— sections enabled under your Relativity6 agreementeffective— section ids included in this response, such asonlinePresenceorpublicReviewswhen review data ran
Use effective to drive UI layout and downstream parsing so you only read sections that are present.
Section reference
Each card below describes one response section: how to request it, what underwriters typically use it for, important fields, and a trimmed JSON example.
Most scalar and structured fields use a DataPoint object:
| Property | Meaning |
|---|---|
value | The normalized answer (string, number, object, or array) |
confidence | Model or source confidence from 0 to 1 |
sources | Where the data came from, including source category and trust level |
verificationStatus | verified, unverifiable, no_evidence, not_searched, or pending |
conflicts | true when sources disagree; see conflictData when present |
Examples are abbreviated. Your responses may include additional fields depending on which sections are enabled for your organization and what data is available for the business.
Response path: company.firmographic
What to expect
- Industry codes such as NAICS tiers, plus SIC, MCC, or workers comp when included in your configuration
- Scale signals such as employee count and revenue as ranges
- Location, contact, ownership, and products or services when available
- Most fields use the standard DataPoint shape: value, confidence, sources, and verificationStatus
| Field | Meaning |
|---|---|
| legal_name | Registered or commonly used legal name |
| industryClassification | NAICS and related classification codes with confidence per tier |
| employee_count / annual_revenue | Estimated ranges with source attribution |
| headquarters | Structured address when verified |
| ownersAndOperators | Key people tied to the business |
Example response fragment
Response path: company.onlinePresence | publicReviews
What to expect
- Send reviews in categories; the response includes company.onlinePresence or company.publicReviews, not both
- categoryAccess.effective lists onlinePresence or publicReviews when review data is included
- If review data is not enabled for your organization, reviews is omitted from the response
| Field | Meaning |
|---|---|
| reviews | Request value in the categories array |
| onlinePresence | Website, social profiles, and review analysis |
| publicReviews | Public ratings and review summaries from listing sources |
Example response fragment
Response path: company.onlinePresence
What to expect
- Included when you request reviews and your organization receives this section, or when you request onlinePresence directly
- Review summaries and trend windows for 3, 6, and 12 months when review data is available
- Site metadata such as title, description, and hero imagery when the domain is available
| Field | Meaning |
|---|---|
| companyWebsite | Primary site URL |
| socialMediaLinks | Known social profiles |
| publicReviews / reviewAnalysis | Aggregated ratings and narrative analysis |
| pageTitle / pageDescription | Homepage signals when extracted |
Example response fragment
Response path: company.publicReviews
What to expect
- Included when you request reviews and your organization receives this section, or when you request publicReviews directly
- Focused on reviewSummary and reviewAnalysis
- Useful when you need listing-level review stats without the broader online presence bundle
| Field | Meaning |
|---|---|
| reviewSummary | Average rating, count, and platforms |
| reviewAnalysis | Trend slices and short narrative summary |
Example response fragment
Response path: company.publicFilings
What to expect
- Registration status, entity type, and incorporation date when a match is found
- A filings array of registry rows with number and register name
- Fields may be empty or show verificationStatus no_evidence when registries have no match
| Field | Meaning |
|---|---|
| companyRegistration | Incorporation and entity status |
| companyAliases | Known DBA or historical names |
| filings | List of registry filing references |
Example response fragment
Response path: company.adverseMedia
What to expect
- The section root uses the standard DataPoint object
- newsEvents with articles including title, url, publisher, and date when events exist
- May return verificationStatus no_evidence when no reportable coverage is found
| Field | Meaning |
|---|---|
| value.newsEvents | Grouped adverse stories with topics and event types |
| value.financialCrime / laborDisputes | Thematic flags when surfaced |
| sources | Source attribution for each finding |
Example response fragment
Response path: company.digitalAssetHealth
What to expect
- Letter or numeric grades for SSL, domain, and website security
- Growth and risk propensity scores on a consistent scale
- aiSummary narrative when the domain assessment completes
| Field | Meaning |
|---|---|
| domainAndSecurityGrades | SSL, domain, and website security grades |
| riskScores | Company, infrastructure, and website propensity scores |
| aiSummary | Plain-language digital risk overview |
Example response fragment
Response path: company.corporateStability
What to expect
- A stability block with scores and reasons such as Stable, Moderate, or Unstable
- Timeline events covering founding, registrations, and reputation milestones
- Helps distinguish new ventures from established operators
| Field | Meaning |
|---|---|
| stability.keyPersonnelStability | Leadership continuity assessment |
| stability.structuralChanges | Merger, relocation, or reorganization signals |
| timeline | Ordered events with type, title, and confidence |
Example response fragment
Response path: company.riskAssessment
What to expect
- A customFlags array with flag, category, reasoning, riskLevel, and optional evidenceLink
- The parent customFlags field includes confidence and sources
- Use category_filter or flag_filter on the request to limit which profile groups or flags are evaluated
| Field | Meaning |
|---|---|
| customFlags.value[] | Raised flags with reasoning and risk level |
| customFlags.value[].category | Profile group name; use with category_filter |
| customFlags.value[].evidenceLink | Supporting URL when provided for a flag |
Example response fragment
Response path: company.summary
What to expect
- businessDescription in plain language suitable for underwriting review
- riskProfile with riskVerdict, riskSummary, and per-section pass or flag verifications when generated
- Often requested alongside firmographic and riskAssessment for a complete narrative
| Field | Meaning |
|---|---|
| businessDescription | What the company does |
| riskProfile.riskVerdict | Overall risk signal such as Low, Medium, or High Risk |
| riskProfile.verifications | Per-section pass or flag with reasons |
| overallConfidence | Aggregate confidence for the summary block |
Example response fragment
Response path: company.propertyInsights
What to expect
- Present only when propertyInsights is enabled and included in your categories request
- geocode and structure polygon when the address resolves
- tenants list with brands, categories, and NAICS when co-tenant data is available
| Field | Meaning |
|---|---|
| geocode | Latitude and longitude for the submitted or resolved address |
| structure | Building footprint polygon when available |
| tenants | Co-located businesses with brand and category metadata |