- Getting started
- Account management
- Security
- Destinations
- Integrations
- SaaS
- Overview
- 3PL Central
- ActiveCampaign
- AdRoll
- Amplitude
- AppsFlyer
- Asana
- Autopilot
- BigCommerce
- Braintree
- Bronto
- Campaign Manager
- Campaign Monitor
- Chargebee
- Chargify
- CircleCI
- Close.io
- Club Speed
- Codat
- COVID-19 Public Data
- Crossbeam
- Darksky
- Deputy
- Desk
- Dixa
- Doorbell.io
- eBay
- Eloqua
- Facebook Ads
- Freshdesk
- Front
- FullStory
- GitHub
- GitLab
- Google Ads
- Google Ads (AdWords)
- Google Analytics
- Google Analytics (AdWords)
- Google Analytics 360
- Google Analytics 4
- Google ECommerce
- Google Search Console
- Google Sheets
- Harvest
- Harvest Forecast
- Heap
- Help Scout
- HubSpot
- iLEVEL
- Impact
- Intacct
- Intercom
- Invoiced
- Iterable
- JIRA
- Klaviyo
- Kustomer
- Lever
- LinkedIn Ads
- Listrak
- LivePerson
- Looker
- LookML
- MailChimp
- Mailshake
- Mambu
- Marketo
- Microsoft Advertising
- Microsoft Teams
- Mixpanel
- NetSuite
- NetSuite Suite Analytics
- Onfleet
- Outbrain
- Outreach
- Pardot
- Pendo
- Pepperjam
- Pipedrive
- Quick Base
- QuickBooks
- Recharge
- Recurly
- Referral SaaSquatch
- Revinate
- RingCentral
- SaaSOptics
- Sailthru
- Salesforce
- Salesforce Marketing Cloud
- Selligent
- SendGrid Core
- ShipHero
- Shippo
- Shopify
- Slack
- Snapchat Ads
- Square
- Stripe
- SurveyMonkey
- Taboola
- TikTok Ads
- Toggl
- Trello
- Twilio
- Twitter Ads
- Typeform
- UJET
- Urban Airship
- UserVoice
- Wootric
- Workday RaaS
- Xero
- Yotpo
- Zendesk Chat
- Zendesk Support
- Zoom
- Zuora
- Databases
- Overview
- Amazon Aurora MySQL RDS
- Amazon Aurora PostgreSQL RDS
- Amazon DynamoDB
- Amazon Microsoft SQL Server RDS
- Amazon MySQL RDS
- Amazon Oracle RDS
- Amazon PostgreSQL RDS
- Amazon S3 CSV
- Google CloudSQL MySQL
- Google CloudSQL PostgreSQL
- Heroku
- Magento
- MariaDB
- Microsoft Azure MySQL
- Microsoft Azure SQL Database
- Microsoft SQL Server
- MongoDB
- MongoDB Atlas
- MySQL
- Oracle
- PostgreSQL
- Responsys
- SFTP
- Webhooks
- All integrations
- Connection cloning
- Connect other data sources
- SaaS
- Extracting data
- Loading data
- Analysis tools
- Troubleshooting
- Developers
- Changelog
Get started with a free trial today
Already have an account? Sign in
iLEVEL (v1)
iLEVEL is currently in beta. The info in this guide is subject to change.
This integration is powered bySinger's iLevel tap. For support,visit the GitHub repo orjoin the Singer Slack.
iLEVEL integration summary
Stitch’s iLEVEL integration replicates data from theiLEVEL Portfolio Monitoring Platform by IHS Markit using the2019 SOAP API WSDL. Refer to theSchema 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 theAdd Integration button.
Click theiLEVEL 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_ilevelin the destination.Note: Schema names cannot be changed after you save the integration.- In theUsername field, enter the iLEVEL API user’s username.
- In thePassword field, enter the iLEVEL API user’s password.
- Optional: If connecting to a sandbox environment, checkConnect 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 dataequal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond iLEVEL’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.
Step 3: Create a replication schedule
In theReplication Frequency section, you’ll create the integration’sreplication 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 theUnderstanding 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’sTables to Replicate tab, locate a table you want to replicate.
To track a table, click thecheckbox next to the table’s name. A blue checkmark means the table is set to replicate.
To track a column, click thecheckbox 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 theFinalize Your Selections button at the bottom of the screen to save your selections.
- Click into the integration from the Stitch Dashboard page.
Click theTables to Replicate tab.
- In the list of tables, click the box next to theTable Names column.
In the menu that displays, clickTrack all Tables and Fields:
- Click theFinalize 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, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, aPending 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 theAnchor 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 forversion 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 theLoading Guide for your destination for more info.
asset_to_asset_relations
Theasset_to_asset_relations table contains info about asset to asset relations in your iLEVEL account.
Full Table | |
Primary Key | id |
| Useful links |
| Join asset_to_asset_relations with | on |
|---|---|
| assets | asset_to_asset_relations.from_id = assets.id asset_to_asset_relations.to_id = assets.id |
| data_items | asset_to_asset_relations.from_id = data_items.asset_id asset_to_asset_relations.to_id = data_items.asset_id |
| fund_to_asset_relations | asset_to_asset_relations.from_id = fund_to_asset_relations.to_id asset_to_asset_relations.to_id = fund_to_asset_relations.to_id |
| securities | asset_to_asset_relations.from_id = securities.asset_id asset_to_asset_relations.to_id = securities.asset_id |
from_id INTEGER |
id INTEGER |
is_soft_deleted BOOLEAN |
status_id INTEGER |
to_id INTEGER |
type_id STRING |
assets
Theassets table contains info about the assets in your iLEVEL account.
Key-based Incremental | |
Primary Key | id |
Replication Key | last_modified_date |
| Useful links |
| Join assets with | on |
|---|---|
| asset_to_asset_relations | assets.id = asset_to_asset_relations.from_id assets.id = asset_to_asset_relations.to_id |
| data_items | assets.id = data_items.asset_id |
| fund_to_asset_relations | assets.id = fund_to_asset_relations.to_id assets.lead_fund_id = fund_to_asset_relations.from_id |
| securities | assets.id = securities.asset_id |
| fund_to_fund_relations | assets.lead_fund_id = fund_to_fund_relations.from_id assets.lead_fund_id = fund_to_fund_relations.to_id |
| funds | assets.lead_fund_id = funds.id |
acquisition_as_of DATE-TIME | ||||||||||
acquisition_date DATE-TIME | ||||||||||
asset_status_id INTEGER | ||||||||||
calendar_type STRING | ||||||||||
currency_code STRING | ||||||||||
description STRING | ||||||||||
excel_name STRING | ||||||||||
has_acquisition_as_of BOOLEAN | ||||||||||
id INTEGER | ||||||||||
industry_id INTEGER | ||||||||||
initial_period DATE-TIME | ||||||||||
investment_thesis STRING | ||||||||||
is_soft_deleted BOOLEAN | ||||||||||
last_modified_date DATE-TIME | ||||||||||
lead_fund_id INTEGER | ||||||||||
name STRING | ||||||||||
object_type_id STRING | ||||||||||
period_mapping OBJECT
| ||||||||||
status INTEGER | ||||||||||
type_id INTEGER | ||||||||||
url STRING |
data_items
Thedata_items table contains info about global data items in your iLEVEL account.
Key-based Incremental | |
Primary Key | id |
Replication Key | last_modified_date |
| Useful links |
| Join data_items with | on |
|---|---|
| asset_to_asset_relations | data_items.asset_id = asset_to_asset_relations.from_id data_items.asset_id = asset_to_asset_relations.to_id |
| assets | data_items.asset_id = assets.id |
| fund_to_asset_relations | data_items.asset_id = fund_to_asset_relations.to_id |
| securities | data_items.asset_id = securities.asset_id |
| periodic_data_calculated | data_items.id = periodic_data_calculated.data_item_id |
| periodic_data_standardized | data_items.id = periodic_data_standardized.data_item_id |
aggregation_null_replacement BOOLEAN |
aggregation_type_id INTEGER |
asset_i_ds_string STRING |
asset_id INTEGER |
category_id INTEGER |
conversion_type_id INTEGER |
data_value_type INTEGER |
description STRING |
enabled_capabilities_string STRING |
excel_name STRING |
format_decimals INTEGER |
format_type_id INTEGER |
formula_type_i_ds_string STRING |
id INTEGER |
is_carry_over BOOLEAN |
is_global BOOLEAN |
is_monetary BOOLEAN |
is_number_comma_separated BOOLEAN |
is_putable BOOLEAN |
is_scalable BOOLEAN |
is_soft_deleted BOOLEAN |
last_modified_date DATE-TIME |
name STRING |
object_type_id STRING |
scenario_i_ds_string STRING |
fund_to_asset_relations
Thefund_to_asset_relations table contains info about fund to asset relations in your iLEVEL account.
Full Table | |
Primary Key | id |
| Useful links |
| Join fund_to_asset_relations with | on |
|---|---|
| asset_to_asset_relations | fund_to_asset_relations.to_id = asset_to_asset_relations.from_id fund_to_asset_relations.to_id = asset_to_asset_relations.to_id |
| assets | fund_to_asset_relations.to_id = assets.id fund_to_asset_relations.from_id = assets.lead_fund_id |
| data_items | fund_to_asset_relations.to_id = data_items.asset_id |
| securities | fund_to_asset_relations.to_id = securities.asset_id |
| fund_to_fund_relations | fund_to_asset_relations.from_id = fund_to_fund_relations.from_id fund_to_asset_relations.from_id = fund_to_fund_relations.to_id |
| funds | fund_to_asset_relations.from_id = funds.id |
from_id INTEGER |
id INTEGER |
is_soft_deleted BOOLEAN |
status_id INTEGER |
to_id INTEGER |
type_id STRING |
fund_to_fund_relations
Thefund_to_fund_relations table contains info about fund to fund relations in your iLEVEL account.
Full Table | |
Primary Key | id |
| Useful links |
| Join fund_to_fund_relations with | on |
|---|---|
| assets | fund_to_fund_relations.from_id = assets.lead_fund_id fund_to_fund_relations.to_id = assets.lead_fund_id |
| fund_to_asset_relations | fund_to_fund_relations.from_id = fund_to_asset_relations.from_id fund_to_fund_relations.to_id = fund_to_asset_relations.from_id |
| funds | fund_to_fund_relations.from_id = funds.id fund_to_fund_relations.to_id = funds.id |
from_id INTEGER |
id INTEGER |
is_soft_deleted BOOLEAN |
status_id INTEGER |
to_id INTEGER |
type_id STRING |
funds
Thefunds table contains info about the funds in your iLEVEL account.
Key-based Incremental | |
Primary Key | id |
Replication Key | last_modified_date |
| Useful links |
| Join funds with | on |
|---|---|
| assets | funds.id = assets.lead_fund_id |
| fund_to_asset_relations | funds.id = fund_to_asset_relations.from_id |
| fund_to_fund_relations | funds.id = fund_to_fund_relations.from_id funds.id = fund_to_fund_relations.to_id |
business_unit_id INTEGER | ||||||||||
calendar_type STRING | ||||||||||
color STRING | ||||||||||
currency_code STRING | ||||||||||
enabled_capabilities_string STRING | ||||||||||
excel_name STRING | ||||||||||
has_logo BOOLEAN | ||||||||||
id INTEGER | ||||||||||
initial_period DATE-TIME | ||||||||||
is_soft_deleted BOOLEAN | ||||||||||
last_modified_date DATE-TIME | ||||||||||
object_type_id STRING | ||||||||||
owner_type_id INTEGER | ||||||||||
period_mapping OBJECT
| ||||||||||
status INTEGER | ||||||||||
status_id INTEGER | ||||||||||
total_committed_capital NUMBER | ||||||||||
type_of_plan_id STRING | ||||||||||
url STRING | ||||||||||
vintage INTEGER |
investment_transactions
Theinvestment_transactions table contains info about investment transactions in your iLEVEL account.
Key-based Incremental | |
Primary Key | id |
Replication Key | last_modified |
| Useful links |
| Join investment_transactions with | on |
|---|---|
| investments | investment_transactions.investment.id = investments.id investment_transactions.security.id = investments.id |
| periodic_data_calculated | investment_transactions.scenario.id = periodic_data_calculated.scenario_id |
| periodic_data_standardized | investment_transactions.scenario.id = periodic_data_standardized.scenario_id |
| scenarios | investment_transactions.scenario.id = scenarios.id |
| securities | investment_transactions.security.id = securities.id |
amount NUMBER | ||||||
as_of DATE-TIME | ||||||
client OBJECT
| ||||||
cost_per_share NUMBER | ||||||
currency STRING | ||||||
custom1 STRING | ||||||
custom2 STRING | ||||||
custom3 DATE-TIME | ||||||
custom4 DATE-TIME | ||||||
custom5 STRING | ||||||
custom6 STRING | ||||||
description STRING | ||||||
group_id INTEGER | ||||||
id INTEGER | ||||||
internal_id STRING | ||||||
investment OBJECT
| ||||||
is_soft_deleted BOOLEAN | ||||||
last_modified DATE-TIME | ||||||
last_modified_by OBJECT
| ||||||
local_amount NUMBER | ||||||
local_currency STRING | ||||||
original_id INTEGER | ||||||
owner OBJECT
| ||||||
scenario OBJECT
| ||||||
security OBJECT
| ||||||
shares NUMBER | ||||||
transaction_category OBJECT
| ||||||
transaction_date DATE-TIME | ||||||
transaction_type OBJECT
| ||||||
value_per_share NUMBER |
investments
Theinvestments table contains info about the investments in your iLEVEL account.
Key-based Incremental | |
Primary Key | id |
Replication Key | last_modified_date |
| Useful links |
| Join investments with | on |
|---|---|
| investment_transactions | investments.id = investment_transactions.investment.id investments.id = investment_transactions.security.id |
| securities | investments.id = securities.id |
acquisition_date DATE-TIME |
commitment NUMBER |
currency STRING |
from_id INTEGER |
id INTEGER |
is_soft_deleted BOOLEAN |
last_modified_date DATE-TIME |
ownership_percentage NUMBER |
security_id INTEGER |
status_id INTEGER |
to_id INTEGER |
type_id STRING |
periodic_data_calculated
Theperiodic_data_calculated table contains calculated data using the following dimensions:
- Entities: Assets
- Scenarios: Actual
- Currency: USD
- Period: Fiscal quarter
Key-based Incremental | |
Primary Key | hash_key |
Replication Key | reported_date_value |
| Useful links |
| Join periodic_data_calculated with | on |
|---|---|
| data_items | periodic_data_calculated.data_item_id = data_items.id |
| periodic_data_standardized | periodic_data_calculated.data_item_id = periodic_data_standardized.data_item_id periodic_data_calculated.scenario_id = periodic_data_standardized.scenario_id |
| investment_transactions | periodic_data_calculated.scenario_id = investment_transactions.scenario.id |
| scenarios | periodic_data_calculated.scenario_id = scenarios.id |
currency_code STRING |
data_item_id INTEGER |
data_value_type STRING |
detail_id INTEGER |
end_of_period_value DATE-TIME |
entity_id INTEGER |
excel_formula STRING |
exchange_rate_type STRING |
hash_key STRING |
period_type STRING |
reported_date_value DATE-TIME |
request_identifier INTEGER |
scenario_id INTEGER |
standardized_data_id INTEGER |
value STRING |
value_numeric NUMBER |
value_string STRING |
periodic_data_standardized
Theperiodic_data_standardized table contains info about periodic standardized data.
Key-based Incremental | |
Primary Key | hash_key |
Replication Key | reported_date_value |
| Useful links |
| Join periodic_data_standardized with | on |
|---|---|
| data_items | periodic_data_standardized.data_item_id = data_items.id |
| periodic_data_calculated | periodic_data_standardized.data_item_id = periodic_data_calculated.data_item_id periodic_data_standardized.scenario_id = periodic_data_calculated.scenario_id |
| investment_transactions | periodic_data_standardized.scenario_id = investment_transactions.scenario.id |
| scenarios | periodic_data_standardized.scenario_id = scenarios.id |
currency_code STRING |
data_item_id INTEGER |
data_value_type STRING |
detail_id INTEGER |
end_of_period_value DATE-TIME |
entity_id INTEGER |
excel_formula STRING |
exchange_rate_type STRING |
hash_key STRING |
period_type STRING |
reported_date_value DATE-TIME |
request_identifier INTEGER |
scenario_id INTEGER |
standardized_data_id INTEGER |
value STRING |
value_numeric NUMBER |
value_string STRING |
scenarios
Thescenarios table contains info about the scenarios in your iLEVEL account.
Full Table | |
Primary Key | id |
| Useful links |
| Join scenarios with | on |
|---|---|
| investment_transactions | scenarios.id = investment_transactions.scenario.id |
| periodic_data_calculated | scenarios.id = periodic_data_calculated.scenario_id |
| periodic_data_standardized | scenarios.id = periodic_data_standardized.scenario_id |
excel_name STRING |
id INTEGER |
is_soft_deleted BOOLEAN |
name STRING |
securities
Thesecurities table contains info about the securities in your iLEVEL account.
Key-based Incremental | |
Primary Key | id |
Replication Key | last_modified_date |
| Useful links |
| Join securities with | on |
|---|---|
| asset_to_asset_relations | securities.asset_id = asset_to_asset_relations.from_id securities.asset_id = asset_to_asset_relations.to_id |
| assets | securities.asset_id = assets.id |
| data_items | securities.asset_id = data_items.asset_id |
| fund_to_asset_relations | securities.asset_id = fund_to_asset_relations.to_id |
| investment_transactions | securities.id = investment_transactions.security.id |
| investments | securities.id = investments.id |
asset_id INTEGER |
excel_name STRING |
has_data BOOLEAN |
id INTEGER |
is_active BOOLEAN |
is_ownership BOOLEAN |
is_soft_deleted BOOLEAN |
last_modified_date DATE-TIME |
name STRING |
object_type_id STRING |
security_sub_type_id INTEGER |
security_sub_type_name STRING |
security_type_id INTEGER |
security_type_name STRING |
| Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.