Data Packages & Subscription Entitlements
Data Packages & Subscription Entitlements
This page explains how Altrata data points are grouped into packages, and how those packages are delivered through product subscriptions.
This documentation describes Altrata’s full canonical data model. Your organization’s subscription determines which entities and fields you receive in APIs and data feeds.
If you see fewer fields than are documented, this is expected and controlled by your product entitlements.
Overview
Altrata data is organized as follows:
Data Points → Packages → Product Subscriptions
- Data points are individual attributes (e.g., Name, Assets, Board Roles).
- Packages group related data points.
- Product subscriptions determine which packages you receive.
Each package can be:
- Included by default in a subscription, or
- Licensed as an add-on.
Product Subscriptions
The following product subscriptions are available:
- Account
- Buyer
- Investor
- Donor
- Exec
Data Packages
Altrata currently provides the following data packages:
- Core
- Executive Insights
- Wealth Insights
- Philanthropy & Political Donations
- Private Equity & M&A
Each package may be licensed standalone or bundled within a subscription.
Package Availability by Subscription
Package | Included By Default | Add-On Availability |
|---|---|---|
Core | All subscriptions | Not required (always included) |
Executive Insights | Account, Exec, Investor | Available to other products |
Wealth Insights | Buyer | Available to other products |
Philanthropy & Political Donations | Donor | Available to other products |
Private Equity & M&A | Investor | Available to other products |
Core Package
Included with all subscriptions.
Core provides foundational identity, demographic, and organization reference data.
Person Data
- Executive Summary
- Name
- Age
- Gender
- Date of Birth
- Role
- Personal Address
- Education
- Interests & Hobbies
- Achievements / Awards - Coming Q2 2026
- Interesting Facts
- Personal & Professional Email
- Nationality - Coming Q2 2026
- Birthplace
- Relationship Status
- Earning Indicator
Organization Data
- Org Name
- Org Type
- Sector
- Organization Address
- Revenue & Market Cap
- Leadership & Board Structures
- Ticker
Executive Insights Package
Included with:
- Account
- Exec
- Investor
Available as an add-on to other subscriptions.
Executive Insights Data Points
- Board Memberships
- Time on Board
- Index Constituents
- S&P CapIQ IDs - Coming Q3 2026
- Corporate Experience
- % Women on Board
- Org Financial Details
- Role Location & Department
- Corporate Hierarchy
- Diversity / Membership Associations
- Corporate Advisors & Suppliers
- Competitors - Coming Q2 2026
Wealth Insights Package
Included with:
- Buyer
Available as an add-on to other subscriptions.
Wealth Data Points
- Wealth Category
- Assets
- Wealth Analysis
- Family Details
- Private Foundations
- Family Offices
Philanthropy & Political Donations Package
Included with:
- Donor
Available as an add-on to other subscriptions.
Philanthropy Data Points
- Charitable Donations
- Political Donations
- Wealth Category
Private Equity & M&A Package
Included with:
- Investor
Available as an add-on to other subscriptions.
Private Equity Data Points
- Detail on Private Equity Ownership
Package Behavior: API vs Datafeed
Packages are enforced differently depending on delivery method.
API (Dynamic Entitlements)
The API evaluates package entitlements dynamically at request time.
- Responses include only the entities and fields your subscription is licensed to access.
- The same endpoint may return different field sets for different clients.
- Package logic is applied automatically — no package-specific endpoints exist.
- The canonical model in this documentation represents the superset of all available fields.
This page should be used to understand which attributes belong to which package, but actual API responses are always entitlement-driven.
Datafeed (Package-Structured Files)
Datafeeds do not apply packaging dynamically.
Instead:
- Files are physically structured by universe + package.
- Each file contains the data points associated with that specific package.
- Your subscription determines which files you receive.
Example:
ExecutiveCompanyExecutiveInsights
- ExecutiveCompany → Universe
- ExecutiveInsights → Package
In the Data Dictionary section of this documentation, content is organized as:
Example:
- Core Data → Package
- Person → File
In contrast to the API:
- Datafeed structure is fixed.
- Package boundaries are reflected directly in file names and file schemas.
- You will only receive the files corresponding to your licensed packages.