iLEVEL is currently in beta. The info in this guide is subject to change.
This integration is powered by Singer's iLevel tap. For support, visit the GitHub repo or join the Singer Slack.
iLEVEL integration summary
Stitch’s iLEVEL integration replicates data from the iLEVEL Portfolio Monitoring Platform by IHS Markit using the 2019 SOAP API WSDL. Refer to the Schema section for a list of objects available for replication.
iLEVEL feature snapshot
A high-level look at Stitch's iLEVEL (v1) integration, including release status, useful links, and the features supported in Stitch.
STITCH | |||
Release status |
Beta |
Supported by | |
Stitch plan |
Standard |
API availability |
Available |
Singer GitHub repository | |||
REPLICATION SETTINGS | |||
Anchor Scheduling |
Supported |
Advanced Scheduling |
Supported |
Table-level reset |
Unsupported |
Configurable Replication Methods |
Unsupported |
DATA SELECTION | |||
Table selection |
Supported |
Column selection |
Supported |
Select all |
Supported |
||
TRANSPARENCY | |||
Extraction Logs |
Supported |
Loading Reports |
Supported |
Connecting iLEVEL
iLEVEL setup requirements
To set up iLEVEL in Stitch, you need:
-
Web Services access in iLEVEL. Reach out to iLEVEL support to enable this in your iLEVEL account. Once enabled, you can continue with the setup in Stitch.
Step 1: Add iLEVEL as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the iLEVEL icon.
-
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch iLEVEL” would create a schema called
stitch_ilevel
in the destination. Note: Schema names cannot be changed after you save the integration. - In the Username field, enter the iLEVEL API user’s username.
- In the Password field, enter the iLEVEL API user’s password.
- Optional: If connecting to a sandbox environment, check Connect to a sandbox environment.
Step 2: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your iLEVEL integration. This means that:
- For tables using Key-based Incremental Replication, data equal to or newer than this date will be replicated to your destination.
- For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your destination.
Change this setting if you want to replicate data beyond iLEVEL’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.
Step 3: Create a replication schedule
In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
iLEVEL integrations support the following replication scheduling methods:
-
Advanced Scheduling using Cron (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.
Step 4: Set objects to replicate
The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.
Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.
For iLEVEL integrations, you can select:
-
Individual tables and columns
-
All tables and columns
Click the tabs to view instructions for each selection method.
- In the integration’s Tables to Replicate tab, locate a table you want to replicate.
-
To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.
-
To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.
- Repeat this process for all the tables and columns you want to replicate.
- When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
- Click into the integration from the Stitch Dashboard page.
-
Click the Tables to Replicate tab.
- In the list of tables, click the box next to the Table Names column.
-
In the menu that displays, click Track all Tables and Fields:
- Click the Finalize Your Selections button at the bottom of the page to save your data selections.
Initial and historical replication jobs
After you finish setting up iLEVEL, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
iLEVEL table reference
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for version 1 of this integration.
This is the latest version of the iLEVEL integration.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs
> customers
), while case is maintained in PostgreSQL destinations (CusTomERs
> CusTomERs
). Refer to the Loading Guide for your destination for more info.
assets
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
The assets
table contains info about the assets in your iLEVEL account.
id
The asset ID. Reference: |
||||||||||
last_modified_date
The time when the asset was last modified. |
||||||||||
acquisition_as_of
|
||||||||||
acquisition_date
|
||||||||||
asset_status_id
|
||||||||||
calendar_type
|
||||||||||
currency_code
|
||||||||||
description
|
||||||||||
excel_name
|
||||||||||
has_acquisition_as_of
|
||||||||||
industry_id
|
||||||||||
initial_period
|
||||||||||
investment_thesis
|
||||||||||
is_soft_deleted
|
||||||||||
lead_fund_id
Reference: |
||||||||||
name
|
||||||||||
object_type_id
|
||||||||||
period_mapping
|
||||||||||
status
|
||||||||||
type_id
|
||||||||||
url
|
asset_to_asset_relations
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The asset_to_asset_relations
table contains info about asset to asset relations in your iLEVEL account.
id
The relationship ID. |
from_id
Reference: |
is_soft_deleted
|
status_id
|
to_id
Reference: |
type_id
|
data_items
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
The data_items
table contains info about global data items in your iLEVEL account.
id
The data item ID. Reference: |
last_modified_date
The time the data item was last modified. |
aggregation_null_replacement
|
aggregation_type_id
|
asset_i_ds_string
|
asset_id
Reference: |
category_id
|
conversion_type_id
|
data_value_type
|
description
|
enabled_capabilities_string
|
excel_name
|
format_decimals
|
format_type_id
|
formula_type_i_ds_string
|
is_carry_over
|
is_global
|
is_monetary
|
is_number_comma_separated
|
is_putable
|
is_scalable
|
is_soft_deleted
|
name
|
object_type_id
|
scenario_i_ds_string
|
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
The funds
table contains info about the funds in your iLEVEL account.
id
The fund ID. Reference: |
||||||||||
last_modified_date
|
||||||||||
business_unit_id
|
||||||||||
calendar_type
|
||||||||||
color
|
||||||||||
currency_code
|
||||||||||
enabled_capabilities_string
|
||||||||||
excel_name
|
||||||||||
has_logo
|
||||||||||
initial_period
|
||||||||||
is_soft_deleted
|
||||||||||
object_type_id
|
||||||||||
owner_type_id
|
||||||||||
period_mapping
|
||||||||||
status
|
||||||||||
status_id
|
||||||||||
total_committed_capital
|
||||||||||
type_of_plan_id
|
||||||||||
url
|
||||||||||
vintage
|
fund_to_asset_relations
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The fund_to_asset_relations
table contains info about fund to asset relations in your iLEVEL account.
id
The relationship ID. |
from_id
Reference: |
is_soft_deleted
|
status_id
|
to_id
Reference: |
type_id
|
fund_to_fund_relations
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The fund_to_fund_relations
table contains info about fund to fund relations in your iLEVEL account.
id
The relationship ID. |
from_id
Reference: |
is_soft_deleted
|
status_id
|
to_id
Reference: |
type_id
|
investments
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
The investments
table contains info about the investments in your iLEVEL account.
id
The investment ID. Reference: |
last_modified_date
The time the investment was last modified. |
acquisition_date
|
commitment
|
currency
|
from_id
|
is_soft_deleted
|
ownership_percentage
|
security_id
|
status_id
|
to_id
|
type_id
|
investment_transactions
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified |
Primary Key |
id |
API endpoint : |
The investment_transactions
table contains info about investment transactions in your iLEVEL account.
id
The investment transaction ID. |
||||||
last_modified
The time the investment transaction was last modified. |
||||||
amount
|
||||||
as_of
|
||||||
client
|
||||||
cost_per_share
|
||||||
currency
|
||||||
custom1
|
||||||
custom2
|
||||||
custom3
|
||||||
custom4
|
||||||
custom5
|
||||||
custom6
|
||||||
description
|
||||||
group_id
|
||||||
internal_id
|
||||||
investment
|
||||||
is_soft_deleted
|
||||||
last_modified_by
|
||||||
local_amount
|
||||||
local_currency
|
||||||
original_id
|
||||||
owner
|
||||||
scenario
|
||||||
security
|
||||||
shares
|
||||||
transaction_category
|
||||||
transaction_date
|
||||||
transaction_type
|
||||||
value_per_share
|
periodic_data_calculated
Replication Method : |
Key-based Incremental |
Replication Key |
reported_date_value |
Primary Key |
hash_key |
API endpoint : |
The periodic_data_calculated
table contains calculated data using the following dimensions:
- Entities: Assets
- Scenarios: Actual
- Currency: USD
- Period: Fiscal quarter
hash_key
This column is a Stitch-generated MD5 hash that should be used as a Primary Key. The hash is created using the following columns:
|
reported_date_value
|
currency_code
|
data_item_id
Reference: |
data_value_type
|
detail_id
|
end_of_period_value
|
entity_id
|
excel_formula
|
exchange_rate_type
|
period_type
|
request_identifier
|
scenario_id
Reference: |
standardized_data_id
|
value
|
value_numeric
|
value_string
|
periodic_data_standardized
Replication Method : |
Key-based Incremental |
Replication Key |
reported_date_value |
Primary Key |
hash_key |
API endpoint : |
The periodic_data_standardized
table contains info about periodic standardized data.
hash_key
This column is a Stitch-generated MD5 hash that should be used as a Primary Key. The hash is created using the following columns:
|
reported_date_value
|
currency_code
|
data_item_id
Reference: |
data_value_type
|
detail_id
|
end_of_period_value
|
entity_id
|
excel_formula
|
exchange_rate_type
|
period_type
|
request_identifier
|
scenario_id
Reference: |
standardized_data_id
|
value
|
value_numeric
|
value_string
|
scenarios
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
The scenarios
table contains info about the scenarios in your iLEVEL account.
id
The scenario ID. Reference: |
excel_name
|
is_soft_deleted
|
name
|
securities
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
The securities
table contains info about the securities in your iLEVEL account.
id
The security ID. |
last_modified_date
The time the security was last modified. |
asset_id
Reference: |
excel_name
|
has_data
|
is_active
|
is_ownership
|
is_soft_deleted
|
name
|
object_type_id
|
security_sub_type_id
|
security_sub_type_name
|
security_type_id
|
security_type_name
|
Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.