Object Hierarchy for K-1 Aggregator
In this guide, we will walk through the basic structure of objects present in K-1 Aggregator, common keywords and phrases used to describe them, as well as how they relate to one another.
Figure 1
Tenants
The top level of our hierarchy. Your API token will be associated with a single "Parent" Tenant. You may create additional "Child" Tenants under your parent. Your API token will work for everything under your Parent. Separating data into multiple Children will allow you to segregate data based on your use case. If you have access to the Parent, you will have access to all data in the Children as well.
Instances
The next layer down is instances. Instances belong to Tenants, and they are also tax year specific. The primary purpose of the Instance is to be a container for all of the investments for that year for a particular taxable entity.
Investments
The final layer of our diagram is the Investment. Belonging to an instance, these represent the investments, or K-1s for a particular taxable entity. It's within these investments that we store all sorts of information related to a Federal K-1. Investments can be classified as any major Federal K-1 form types (e.g., 1065, 1120S, 1041, etc.) and provide access to data points according to their type. One of the major pieces of functionality that our API provides is all of the data related to this investment bundled into a neat JSON structure we call the Digital K-1.
Updated 10 days ago