Upload Restrictions, Rules and Associations via .csv File

Upload a .csv file to quickly add, modify and delete restrictions, add and delete rules from restrictions, add and remove associations between restrictions and entities and add, modify and delete lists.

File size is limited to 512 KB and 10,000 lines.

Requirements:
  • All lines must begin with an ACTION followed by NAME, with each entry separated by a comma.

  • All restrictions must include at least one rule.

Supported Actions:

 

Actions and Requisite Parameters

RESTR_ADD - Add a new restriction.

Prerequisite: The restriction name must be unique (not exist).

Parameters:

  • Required: Restriction name, e.g. Disallow IBM and BRK A,

  • Optional: Description, e.g. Description="descriptive text",

  • Optional: Message for traders, e.g. Message="message for traders when restriction is triggered",

  • Optional: Allow_Restrict valid values include: Allow|Restrict, e.g. Allow_Restrict="Allow",

  • Optional: RuleMatch valid values include: Any|All, e.g. RuleMatch="Any",

  • Required: At least one rule. Rule syntax is:

RULE_BEGIN,

  • Required: Rule_type e.g. rule_type="valid rule type", (see Rule Types below).

  • As needed: Parameters for rule type.

  • Required: TIF valid values include GTC | GTD e.g. TIF="GTC"

    • GTD requires START=YYYYMMDD, END=YYYYMMDD

RULE_END

See an example of RESTR_ADD

 

RESTR_MODIFY - Modify a restriction.

Prerequisites:

  • The restriction must exist.

  • The restriction name you use must exactly match the current restriction name in all aspects.

Parameters:

Required: Restriction name, which must exactly match name of restriction you are modifying, e.g. Disallow IBM and BRK A,

If included, the below will either be added to the restriction, or replace the current values:

  • Name="new name", will replace existing restriction name.

  • Description, e.g. Description="descriptive text",

  • Message for traders, e.g. Message="message for traders when restriction is triggered",

  • Allow_Restrict valid values include: Allow|Restrict, e.g. Allow_Restrict="Allow",

  • RuleMatch valid values include: Any|All, e.g. RuleMatch="Any",

See an example of RESTR_MODIFY

 

RULE_ADD - Add a rule to a restriction.

Prerequisites:

  • The restriction to which you are adding the rule must exist.

  • The restriction name you use must exactly match the current restriction name in all aspects.

Parameters:

  • Required: Restriction name, e.g. Disallow IBM and BRK A,

  • Required: At least one rule using the syntax:

RULE_BEGIN,

  • Required: Rule_type e.g. rule_type="valid rule type", (see Rule Types below).

  • As needed: Parameters for rule type.

  • Required: TIF valid values include GTC | GTD e.g. TIF="GTC"

    • GTD requires START=YYYYMMDD, END=YYYYMMDD

RULE_END

See an example of RULE_ADD

 

RULE_DELETE - Delete a rule from an existing restriction.

Prerequisites:

  • The restriction and rule must exist.

  • The restriction name, rule type and rule parameters must exactly match the current restriction name in all aspects.

    NOTE: If the restriction includes only one rule, deleting the rule will result in deleting the restriction.

Required: At least one rule using the syntax:

RULE_BEGIN,

  • Required: Rule_type e.g. rule_type="valid rule type", (see Rule Types below).

  • As needed: Parameters for rule type.

  • Required: TIF valid values include GTC | GTD e.g. TIF="GTC"

    • GTD requires START=YYYYMMDD, END=YYYYMMDD

RULE_END

See an example of RULE_DELETE

 

RESTR_DELETE - Delete an existing restriction. This action will also delete all assocations.

Prerequisites:

  • The restriction must exist.

  • The restriction name you use must exactly match the current restriction name in all aspects.

Parameters:

  • Required: Restriction name, e.g. Disallow IBM and BRK A,

See an example of RESTR_DELETE

 

ASSOC_ADD - Associate a restriction with entities.

Prerequisites:

  • The restriction must exist.

  • Entities used must be accessible to you when logged in for setting trading permissions.

  • The restriction name you use must exactly match the current restriction name in all aspects.

Parameters:

  • Required: Restriction name, e.g. Disallow IBM and BRK A,

  • Required: AssocType, valid values:

    • all

    • accounts, e.g. Assoctype=accounts,U1244,U1766

    • users, e.g. Assoctype=users,johndoe,janedoe

See an example of ASSOC_ADD

 

ASSOC_DELETE - Remove the association between a restriction and entities.

Prerequisites:

  • The restriction must exist.

  • Entities used must be accessible to you when logged in for setting trading permissions.

  • The restriction name you use must exactly match the current restriction name in all aspects.

Parameters:

  • Required: Restriction name, e.g. Disallow IBM and BRK A,

  • Required: AssocType, valid values: all | accounts | users (example: see above at ASSOC_ADD)

See an example of ASSOC_DELETE

 

LIST_ADD - Create a new list.

Prerequisite: The list name must be unique (not exist).

Parameters:

  • Required: ListName, e.g. South American Countries,

  • Optional: Description, e.g. Description="descriptive text",

  • Required: List_Type, e.g. list_type =country

  • Required: List_Type must contain at least one list entry. List entry syntax is:

ENTRY_BEGIN,

  • Required: entry_type e.g. entry_type=country, country_code=BG,

  • As needed: Parameters for entry type, e.g. country requires country_code=

ENTRY_END

See an example of LIST_ADD

 

LIST_MODIFY

Prerequisites:

  • The list must exist.

  • The list name you use must exactly match the current name in all aspects.

Parameters:

Required: List name, which must exactly match name of the list you are modifying, e.g. Restricted Stock Countries

If included, the below will either be added to the list, or replace the current values:

  • Name="new name", will replace existing list name.

  • Description, e.g. Description="descriptive text",

See an example of RESTR_MODIFY

 

LIST_DELETE - Delete a list that is not used in any rule.

Prerequisites:

  • The list must exist.

  • The list cannot currently be used in any rule. To find out whether a list is in use, click Lists in the menu and check the "In use" column.

  • The list name you use must exactly match the current name in all aspects.

See an example of LIST_DELETE

 

LISTENTRY_ADD - Add one or more entries to an existing list.

Prerequisites:

  • The list to which you are adding the entry must exist.

  • The list name you use must exactly match the current list name in all aspects.

Parameters:

  • Required: List name, e.g. Restricted US Stock Countries

ENTRY_BEGIN,

  • Required: entry_type e.g. entry_type=country, country_code=BG,

  • As needed: Parameters for entry type, e.g. country requires country_code=

ENTRY_END

See an example of LISTENTRY_ADD

 

LISTENTRY_DELETE - Delete one or more entries from an existing list.

Prerequisites:

  • The list from which you are deleting the entries must exist.

  • The list name you use must exactly match the current list name in all aspects.

  • The entry you are deleting must exactly match the current entry.

Parameters:

  • Required: List name, e.g. Restricted US Stock Countries

ENTRY_BEGIN,

  • Required: entry_type e.g. entry_type=country, country_code=BG,

  • As needed: Parameters for entry type, e.g. country requires country_code=

ENTRY_END

See an example of LISTENTRY_DELETE

 
Supported List and Entry Types
Issuer/Underlying
  • List type: ISSUERORCONID or CONID

    • ISSUERORCONID restricts all contracts of an issuer (eg.: all contracts involving IBM);

    • CONID only restricts a specific contract, specified by ISIN or CUSIP.

  • Allowed entry types:

    • within ISSUERORCONID list: ISSUER, CONID

    • within CONID list: CONID

  • Required parameters: (one of the following)

    • isin = ISIN

    • cusip = CUSIP

  • Optional parameters:

    • majorExch="*" (allows all primary listing exchanges) or an exchange, eg. "NASDAQ", "ARCA", "EBS"

    • currency="*" (allows all currencies) or a 3-letter currency abbreviation, eg. "USD", "CHF", "EUR"

  • Error: If 0 contracts are found or more than 1 issuerIDs are included within the list entry

    • Note: multiple contracts (with different primary listing exchange and/or currency) can correspond to a given ISIN or CUSIP.

Product Category
Security Type
Country
  • List type: COUNTRY

  • Allowed entry type: COUNTRY

  • Required parameters:

    • country_code

Industry
  • List type: INDUSTRY

  • Allowed entry type: INDUSTRY

  • Required parameters

    • sector|indgroup|indsubgroup

Supported Rules

Restrictions require at least one rule. Some rules included required parameters. Indicate rules using RULE_BEGIN, and RULE_End tags.

Concentration Limit
  • Rule type: CONCENTRATIONLIMIT

  • Required parameters:

    • conctype = "MARGIN | NETVALUE | POSITION | ISSUER | UNDERLYING | PRODCATEGORY | NEGNETCASH | INITIALMARGIN"

    • valtype = "PERC | PERCSHOUT | AMOUNT" (PERCSHOUT stands for % Shares Outstanding and supported only for conctypes UNDERLYING and PRODCATEGORY)

    • val = integer >= 0. If valtype is "PERC" or "PERCSHOUT", it has to be <= 100

    • currency = three-letter abbreviation of currency. Mandatory if valtype is "AMOUNT". Possible values: AUD, CAD, CHF, CNH, CZK, DKK, EUR, GBP, HKD, HUF, ILS, INR, JPY, MXN, NOK, NZD, RUB, SEK, SGD, USD.

  • Conditional parameters

    • side = "SHORT | LONG"

    • productcategory (see below the allowed categories)

    • isin

    • cusip

  • Optional parameter

    • use_ultimate_issuer = true | false (the default is false)

  • Concentration types (the GUI equivalent in bracket) and additional parameters

    • MARGIN (Net Margin)

    • NETVALUE (Net Portfolio)

    • POSITION (Concentration of Position): side

    • ISSUER (Concentration of Issuer): side AND (isin OR cusip) AND use_ultimate_issuer (optional)

    • UNDERLYING (Concentration of Symbol): side AND (isin OR cusip)

    • PRODCATEGORY (Concentration of Product or Security): side AND productcategory

    • NEGNETCASH (Limit Negative Net Cash Balance)

    • INITIALMARGIN (Limit Initial Margin)

  • Example:

    • RULE_BEGIN,rule_type=CONCENTRATIONLIMIT,tif=gtc,conctype=MaRgIn,valtype=amount,currency=USD,val=10000,RULE_END

    • RULE_BEGIN,rule_type=CONCENTRATIONLIMIT,tif=gtc,conctype=MARGIN,valtype=perc,val=12,RULE_END

Custom Trading Hours
  • Rule type: RESTRICTEDHOURS

  • Required parameters:

    • starttime: in format hh:mm:ss, e.g. 09:00:00

    • endtime: in format hh:mm:ss, e.g. 14:00:00; endtime should be later than starttime

    • timezone: the same possibilities are supported as on the web GUI, e.g. US/Eastern. This is case sensitive, so it should be put into quotation marks, e.g. "US/Eastern".

  • Example:

    • RULE_BEGIN, rule_type=RESTRICTEDHOURS, starttime=09:00:00, endtime=14:00:00, timezone="US/Eastern", tif=GTC, RULE_END

Liquidation / Closing Only
  • Rule type: CLOSINGONLY

  • Parameters: None

  • Example:

    • RULE_BEGIN, rule_type=CLOSINGONLY, tif=GTC, RULE_END

Restricted Product Category
  • Rule type: RESTRICTEDPRODCATEGORY

  • Required parameters

  • Optional parameters:

    • orderside = "ALL | BUY | SELL| SELLSHORT"

  • Example:

    • RULE_BEGIN, rule_type=RESTRICTEDPRODCATEGORY, productcategory=ADR, tif=GTC, RULE_END

Restricted Security Type
  • Rule type: RESTRICTEDSECURITYTYPE

  • Required parameters

  • Optional parameters:

    • orderside = "ALL | BUY | SELL| SELLSHORT"

  • Example:

    • RULE_BEGIN, rule_type=RESTRICTEDSECURITYTYPE, securitytype=STK, tif=GTC, RULE_END

Issuer / Underlying
  • Rule type: ISSUER or UNDERLYING

    • ISSUER restricts all contracts of an issuer (eg.: all contracts involving IBM);

    • UNDERLYING only restricts a specific contract, specified by ISIN or CUSIP.

  • Required parameters: (one of the following)

    • isin = ISIN

    • cusip = CUSIP

  • Optional parameters:

    • orderside = "ALL | BUY | SELL | SELLSHORT"

    • nonmarginable = "T|F"

    • majorExch="*" (allows all primary listing exchanges) or an exchange, eg. "NASDAQ", "ARCA", "EBS"

    • currency="*" (allows all currencies) or a 3-letter currency abbreviation, eg. "USD", "CHF", "EUR"

  • Run query for and accept issuer for specified ISIN

    • Note: multiple contracts (with different primary listing exchange and/or currency) can correspond to a given ISIN or CUSIP.

  • Error: If 0 or more than 1 conids/issuerIDs found

  • Example:

    • RULE_BEGIN, rule_type=ISSUER, isin=US449276AG99, tif=GTC, RULE_END

    • RULE_BEGIN, rule_type=UNDERLYING, isin=LU0231203729, tif=GTC, RULE_END

No Cross Trades
  • Rule type: NOCROSSTRADES

  • Required parameters: None

  • Example:

    • RULE_BEGIN, rule_type=NOCROSSTRADES, tif=GTC, RULE_END

Restrict All Orders
  • Rule type: RESTRICTALLORDERS

  • Required parameters:

    • orderside = "ALL | BUY | SELL | SELLSHORT"

  • Example:

    • RULE_BEGIN, rule_type=RESTRICTALLORDERS, orderside=SELLSHORT, tif=GTC, RULE_END

No Negative Cash
  • Rule type: NONEGCASH

  • Parameters: None

  • Example:

    • RULE_BEGIN, rule_type=NONEGCASH, tif=GTC, RULE_END

Days to Expiration
  • Rule type: DAYSTOEXPIRATION

  • Parameters:

    • relation: le, lt, eq, gt, ge, ne, meaning(respectively): "less than or equal", "less than", "equal", "greater than", "greater than or equal", "not equal"

    • numdays: integer, greater than zero

  • Example:

    • RULE_BEGIN,rule_type=daystoexpiration,tif=gtc,relation=le,numdays=5,RULE_END

    • matches orders where days to traded contract's expiration is less than or equal to5 day

Gross Exposure Value Limit
  • Rule type: EXPOSUREVALUE

  • Parameters:

    • exp_type="TRADED | OUTSTANDING"

    • exp_target="TOTAL | UNDERLYING"

    • val: nonnegative integer

    • currency: see concentration limit above

    • If exp_target is UNDERLYING, then either ISIN or CUSIP is mandatory

  • Example:

    • RULE_BEGIN, rule_type=EXPOSUREVALUE, exp_type=OUTSTANDING, exp_target=UNDERLYING, isin=US449276AG99, val=180, currency=USD, tif=GTC, RULE_END

Trade Frequency
  • Rule type: TRADEFREQUENCY

  • Parameters:

    • tradecount: nonnegative integer

    • duration: nonnegative integer

    • unit = "day | hour | minute" (important note: this should be all lowercase and put into quotation marks)

  • Example:

    • RULE_BEGIN, rule_type=TRADEFREQUENCY, tradecount=5, duration=2, unit="hour", tif=GTC, RULE_END (meaning: 5 trades are allowed in every 2 hours)

Trading In Fractions
  • Rule type: TRADINGINFRACTIONS

  • Parameters: None

  • Example:

    • RULE_BEGIN, rule_type=TRADINGINFRACTIONS, tif=GTC, RULE_END

Triggered By Loss
  • Rule type: LOSSTRIGGERED

  • Parameters:

    • valtype = "PERC | AMOUNT"

    • val = integer between 0 and 100 if valtype is PERC, nonnegative integer if valtype is AMOUNT

    • currency: mandatory if valtype is AMOUNT. See the available currencies at Concentration Limit rule.

    • action = "RESTRICTALLORDERS | CLOSINGONLY"

    • effective = "ONLYWHENBREACHED | RESTOFDAY"

    • reallow_val: mandatory if effective is ONLYWHENBREACHED; the same applies as to val in this case

  • Example:

    • RULE_BEGIN, rule_type=LOSSTRIGGERED, valtype=AMOUNT, val=185, currency=EUR, action=CLOSINGONLY, effective=ONLYWHENBREACHED, reallow_val=370, tif=GTC, RULE_END

Minimum Holding Period
  • Rule type: MINHOLDINGPERIOD

  • Parameters:

    • val: nonnegative integer

    • side (optional): it can be either SHORT or LONG if present

    • conctype (optional): it can be either CONID or UNDERLYING

    • isin, cusip or conid is mandatory of conctype is present. The parameter use_ultimate_issuer is also supported for UNDERLYING case.

  • Example:

    • RULE_BEGIN, rule_type=MINHOLDINGPERIOD, val=4, side=SHORT, conctype=ISSUER, isin=US46435U2592, use_ultimate_issuer=true, tif=GTC, RULE_END

Filled Order Frequency
  • Rule type: FILLEDORDERFREQ

  • Parameters:

    • num_orders: nonnegative integer

    • period = "MONTH | QUARTER"

    • duration: 1, 2 or 3 if period is MONTH; 1 of period is QUARTER

  • Example:

    • RULE_BEGIN, rule_type=FILLEDORDERFREQ, num_orders=80, duration=2, period=MONTH, tif=GTC, RULE_END

No Negative Cash Balance
  • Rule type: NONEGNETCASH

  • Parameters: none

  • Example:

    • RULE_BEGIN, rule_type=NONEGNETCASH, tif=GTC, RULE_END

Minimum Position Limits
  • Rule type: MINPOSLIMIT

  • Parameters:

    • conid

    • val: nonnegative integer

  • Example:

    • RULE_BEGIN, rule_type=MINPOSLIMIT, conid=8314, val=54321, tif=GTC, RULE_END

Exclusion
  • Rule type: EXCLUSION

  • Special rule type that specifies exclusion from non-Exclusion rules within restriction

  • TIF has to be set to GTC in all cases

  • Required parameters:

    • exclusion_type

      • AllowClosingExistingPos

      • AllowExistingSymbol

      • ExcludeCashEquivFromCalc

      • MARGINIMPACT

      • CHECKONLYACCOUNTPROP

        • propname (possible values: "IBEntity", "MIFIDCategory", "Residence"; all case-sensitive)

        • relation (possible values: "eq", "ne", case sensitive)

        • propvalue (possible values depend on the propname; "IBEntity": IB-CAN, IB-UK, IBLLC-US, IB-CA, IB-UKL, IB-IN, IB-IE, IB-CE, IB-JP, IB-HK, IB-AU, IB-EU, IBKRFS, IB-SG; "MIFIDCategory": PRO (stands for Professional); "Residence": 3 letter country code, e.g. USA, CHE (Switzerland), GBR (United Kingdom))

    • CHECKONLYPLATFORM

      • relation (like above)

      • platform (possible values: API, CP, CTCI, MOBILE, TWS, WEBAPI)

    • CHECKONLYUSERTYPE

      • relation (like above)

      • user_type (possible values: "client", "fa", "iBroker", "mm"; case sensitive)

    • CHECKONLYHYBRIDFIELD, hybrid_field (must be 234), hybrid_name (must be "Grandfathered", case sensitive), relation (like above), hybrid_value (must be 1)

  • Example: RULE_BEGIN,rule_type=exclusion,tif=gtc,exclusion_type=AllowClosingExistingPos,RULE_END

Whitelist
  • Rule type: WHITELIST

  • This rule whitelists a symbol from restrictions.

  • TIF has to be set to GTC in all cases.

  • One of the following parameters is mandatory: conid, isin, list_name.

  • Optional parameter: orderside.

  • A restriction may contain exactly one whitelist rule (and no other rules in this case).

  • A restriction may have an optional parameter whitelist_exclusions, and this excludes some rules under the whitelist. Its value is a semicolon list of restriction names within square brackets.

  • Example: RESTR_ADD, my-whitelist, RULE_BEGIN, rule_type=WHITELIST, isin=LU0231203729, orderside=SELL, tif=GTC, RULE_END, whitelist_exclusions=[my-restriction-1; my-restriction-2]

Sample .csv lines:

Example 1: Add a restriction

Add a restriction called "Disallow IBM and BRK A" Add a description "Restrict some trading." Include two rules: the first is ISSUER using the isin to identify IBM. The second is another ISSUER that uses the isin to identify BRK A, and use a time-in force of good till date, starting August 1, 2017 and ending January 1, 2018.

RESTR_ADD, "Disallow IBM and BRK A", Description="Restrict some trading", RULE_BEGIN, rule_type=ISSUER, isin=US4592001014, tif=gtc, RULE_END, RULE_BEGIN, rule_type=ISSUER, TIF=GTD,START=20170801,END=20180101,isin=US0846701086, RULE_END

Example 2: Modify a restriction

Modify the restriction, "Disallow IBM and BRK A" to also include AMZN. Also, make the description more helpful and change the name of the restriction.

RESTR_MODIFY,"Disallow IBM and BRK A", message="Trade is rejected as IBM, AMZN and BRK A are not allowed.", description="Restrict trading for IBM, AMZN and BRK A", name="Disallow IBM, AMZN and BRK A"

Example 3: Add a rule

Add a rule to the above restriction that will actually include AMZN.

RULE_ADD, "Disallow IBM, AMZN and BRK A", RULE_BEGIN, rule_type=issuer, isin=US0231351067, tif=GTC, RULE_END

Example 4: Delete a rule

On second thought, delete the rule for amazon. Note that if you delete a rule and it's the only rule in a restriction, you have also deleted the restriction.

RULE_DELETE, "Disallow IBM, AMZN and BRK A", RULE_BEGIN, rule_type=issuer, isin=US0231351067, tif=GTC, RULE_END

Example 5: Delete a restriction

Delete the restriction that rejects orders for short sells, called "No short sells."

RESTR_DELETE, "No short sells"

Example 6: Add an association

Apply the restriction to disallow IBM, AMZN and BRK A to all or specific accounts.

ASSOC_ADD, "Disallow IBM, AMZN and BRK A", ALL

Example 7: Delete an association

Delete the restriction to disallow IBM, AMZN and BRK A from all accounts.

ASSOC_DELETE, "Disallow IBM, AMZN and BRK A", ALL

Example 8: Create a list

I want to include a list of many countries in a rule for two of my restrictions.

LIST_ADD, "Restricted Stock Countries", description="List of countries in which we restrict trading of certain stocks", list_type=country, ENTRY_BEGIN, entry_type=country, country_code=BG, ENTRY_END, ENTRY_BEGIN, entry_type=country, country_code=AU, ENTRY_END, ENTRY_BEGIN, entry_type=country, country_code=BE, ENTRY_END

Example 9: Modify a list

You can change the name or description of a list. I want to change the name of my list from Restricted Stock Countries to Restricted US Stock Countries.

LIST_MODIFY, "Restricted Stock Countries", name="Restricted US Stock Countries"

Example 10: Delete a list

LIST_DELETE, "Restricted US Stock Countries"

Example 11: Add an entry to a list

LISTENTRY_ADD, "Restricted US Stock Countries", ENTRY_BEGIN, entry_type=country, country_code=DE, ENTRY_END

Example 12: Delete an entry from a list

LISTENTRY_DELETE, "Restricted US Stock Countries", ENTRY_BEGIN, entry_type=country, country_code=BE, ENTRY_END

 

Product Categories
  • ADR

  • "BINARYCONTRACTPROP:j3_PTP1446" (note the quotation marks)

  • BLOOMBERGSECTYPE st2=stock type 2, e.g. BDR

  • CALLABLEBOND

  • CLEARINGHOUSE

  • CLP

  • CMDTYFUT

  • CONVPREFERRED

  • CORPBOND

  • EFP

  • ETF

  • EVENTCONTRACTS

  • EXCHANGENSECTYPE exchange_sectype=trading venue and security type, e.g. AMEX/COMB

  • FXCFD

  • INDOPT

  • INDUSTRY sector|indgroup|indsubgroup="industry", e.g. indgroup="Broad Range Equity Index"

  • INVETF

  • ISSUERCOUNTRY country_code=2 letter country code, e.g. US

  • JUNKBOND

  • LEVETF

  • LEVFX

  • LIPPERSECTOR lipper_sector=lipper sector, e.g. "Telecom"

  • LISTCOUNTRY country_code=2 letter country code, e.g. US

  • LP

  • MKTCAP mktcap=market cap in millions, e.g. 100, currency=3 letter currency code, e.g. JPY

  • MUNIBOND

  • NONUS

  • PREFERRED

  • PUTTABLEBOND

  • SSF

  • STKOPT

  • SUBORDINATEBOND

  • TRADINGCURRENCY tradingcurrency=3 letter currency code, e.g. JPY

  • UNCOVOPT

  • USMICROCAPSTK

  • USOTCSTK

Security Types

These are also referred as asset classes.

  • BAG

  • BILL

  • BOND

  • CASH

  • CFD

  • CMDTY

  • CRYPTO

  • FOP

  • FUND

  • FUT

  • FWD

  • IOPT

  • OPT

  • STK

  • WAR

 

Additional Resources

Learn About the Pre-Trade Compliance at IBKR Campus