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 intelligence wealth intelligence 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 intelligence account, exec, investor available to other products wealth intelligence 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 coming q1 2026 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 coming q1 2026 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 coming q1 2026 index constituents coming q1 2026 s\&p capiq ids coming q3 2026 corporate experience coming q2 2026 % women on board coming q1 2026 org financial details coming q1 2026 role location & department coming q1 2026 corporate hierarchy coming q2 2026 diversity / membership associations coming q2 2026 corporate advisors & suppliers coming q2 2026 competitors coming q2 2026 wealth intelligence package included with buyer available as an add on to other subscriptions wealth data points wealth category assets wealth analysis family details private foundations coming q1 2026 family offices coming q1 2026 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 coming q2 2026 transaction advisors coming q2 2026 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 datafeed / \[package name] / \[file name] example datafeed / core data / person 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