Event ID.

Client account name.

Safekeeping account that the portfolio is associated with.

Agent party identifier.

Account code, information only field. Can be used to store custody codes which can be both internal or external safekeeping accounts.

Client defined account alias.

List of user stakeholders. Each stakeholder is an object with username (String), fullName (String) and type (String) keys.

Possible values for type: portfolioSpecialist, assistantPortfolioSpecialist, accountingOfficer.

Example:

[
    {
        "username": "jdoe",
        "fullName": "John Doe",
        "type": "accountingOfficer"
    },
    {
        "username": "janesmith",
        "fullName": "Jane Smith",
        "type": "portfolioSpecialist"
    }
]

Interested parties, each interested party is an object with partyId (String) and preferredCommType (String) keys.

Possible values for preferredCommType: SWIFT, EMAIL, FAX.

Example:

[{
		"partyId": "BIC12GB2XXX",
		"preferredCommType": "SWIFT"
	},
	{
		"partyId": "BIC12GB3XXX",
		"preferredCommType": "SWIFT"
	}
]

List of all teams, each team is an object with id (String), name (String) and displayTeams (Boolean) keys. Multiple teams can be associated with an account , all members of the associated teams have data access privileges meaning they can view the client positions. One of the teams provided can be designated as the UI display team which is then presented on the Positions and Voting screens.

Example:

[
    {
        "id": "T5678",
        "name": "Team 5678",
        "displayTeams": true
    },
    {
        "id": "T1234",
        "name": "Team 1234",
        "displayTeams": false
    }
]

Tax residency, ISO country code (2 CHARS).

Client domicile, ISO country code (2 CHARS).

Client specific attributes, each attribute is an object with type (String) and value (String) keys.

Possible values for type: managementType, portfolioType, entity, clientResidency, additionalInfo.

Possible values for value according to its type:

• managementType - One of the following values: Discretionary, Advisory, Custody, No Mandate.

• portfolioType - One of the following values: TPC (Third Party Custodian), STD (Standard).

• qib - String value.

• entity - One of the following values: LON, BNK, GUE, SGP.

• clientResidency - Client residency, String value e.g. CH, GB, etc.

• • additionalInfo - COMP Value (Mutual Funds). One of the following values: BANK, NOMI, GROS, etc.

Example:

[{
		"type": "entity",
		"value": "LON"
	},
	{
		"type": "portfolioType",
		"value": "TPC"
	}
]

List of client email addresses, each element of the array is an object with email (String) and language (String). language is an optional element in the API, when it is not provided the system will default to English. When provided, language MUST be in ISO 639-1 format, for example - en: English.

Example:

[
    {
        "email": "example@gmail.com",
        "language": "de"
    },
    {
        "email": "example1@gmail.com",
        "language": "es"
    }
]

Party name.

Party type.

Possible values: VENDOR, CUSTODIAN, INTERNAL-CUSTODIAN, ENTITY, THIRDPARTY.

Preferred comm type.

Possible values for preferredCommType: SWIFT, EMAIL, FAX, PORTAL.

List of party addresses, each party address is an object address (String) and comType (String) keys. At least one party address is required.

Possible values for comType: SWIFT, EMAIL, FAX, PORTAL. EMAIL, FAX, PORTAL should have a single entry, i.e., the party can have only 1 email address, 1 fax number and 1 portal. However, it can have multiple BIC addresses.

Example:

[{
		"address": "BIC1235PTLXX",
		"comType": "SWIFT"
	},
	{
		"address": "BIC45678PTLXX",
		"comType": "SWIFT"
	},
	{
		"address": "com@client2loans.com",
		"comType": "EMAIL"
	}
]

Eligible position date.

This parameter informs the receiver of the type of positions being requested, meeting or corporate action. Downstream logic can be different depending of the type of event. Possible values: meeting, corporate-action. When iActs sends out a position request for Meetings it will include three additional parameters that won't exist for Corporate Actions, namely: meeting-filter, meeting-type and meeting-classification (check filters field).

List of security IDs to be retrieved.

Event ID.

Portfolio account that holds the position.

Set of positions, each position is an object with qualifier (String) - type of position, e.g., traded, settled, eligible, etc - and value (Double) - information only balance to be shown in the UI - keys.

Possible values for qualifier: ELIG, SETT, TRAD, ORFC, ENCU. Note: in Meetings, SETD qualifier is used instead of SETT.

Example:

[{
		"qualifier": "ELIG",
		"value": 1234.00001
	},
	{
		"qualifier": "SETT",
		"value": 432.00001
	},
	{
		"qualifier": "TRAD",
		"value": 563.00001
	}
]

Position date.

Required for meetings only - optional for corporate actions.

Place of settlement.

Eligible position date.

This parameter informs the receiver of the type of positions being requested, meeting or corporate action. Downstream logic can be different depending of the type of event. Possible values: meeting, corporate-action. When iActs sends out a position request for Meetings it will include three additional parameters that won't exist for Corporate Actions, namely: meeting-filter, meeting-type and meeting-classification (check filters field).

Filters is an array of objects, each one with type and value (String) keys. Possible values for type: srd (Boolean), meeting-filter (String), meeting-type (String), meeting-classification (String).

Event ID.

Safekeeping Account

Agent party ID.

Set of positions, each position is an object with qualifier (String) - type of position, e.g., eligible, settled, etc - and value (Double) - information only balance to be shown in the UI - keys.

Possible values for qualifier: ELIG, SETT, TRAD, NOMI, BLOK, PENR, PEND, BORR, SPOS, COLI, COLO, REGO, UNBA, INBA, LOAN. Note: in Meetings, SETD qualifier is used instead of SETT.

Example:

[
   {
      "qualifier": "TRAD",
      "value": 1234.00001
   }
]

Nominal value of the instrument, i.e., 1 or 1000. Used to distinguish bonds and equities.

Security name, also known as the security short name.

List of market alias type and values. Each market alias is an object with type (String) and alias (String) keys. At least one market alias is required.

Possible values for type: SEDOL, ISIN, CUSIP, VALOR, TICK.

Example:

[
    {
        "type": "ISIN",
        "alias": "US1234567890"
    },
    {
        "type": "CUSIP",
        "alias": "123456789"
    }
]

Security type is an optional descriptive field that a host can use to bespoke classify their instruments, e.g., Equity, Fixed Income.

Security sub type is an optional descriptive field that a host can use to bespoke classify their instruments, e.g., Warrants, ADR, etc.

Currency, ISO currency code (3 CHARS).

Country of inc, ISO country code (2 CHARS).

Country of listing, ISO country code (2 CHARS).

List of user stakeholders associated with the security. Each stakeholder is an object with username (String), fullName (String) and type (String) keys.

Possible values for type: trader, analyst, creditOfficer.

Example:

[
    {
        "username": "jdoe",
        "fullName": "John Doe",
        "type": "trader"
    },
    {
        "username": "janesmith",
        "fullName": "Jane Smith",
        "type": "creditOfficer"
    }
]

Security issuer.

Security last price.

Unique team name.

Team e-mail address.

User's full name.

User's e-mail.

List of unique user roles identified by composite keys, combining company ID (String) and role name (String).

Example:

[
	["company1", "role1"],
	["company1", "role2"]
]

List of team IDs.

Flag that indicates whether a user is active or deactivated.

List of user functions:

- Admin - Typically system administrations: responsible for add/edit user roles, etc.

- Standard - Back office and front office users.

- Owner - Typically back office users only.

- Panoptic - Gives full visibility of events data.

A user can have multiple functions.

Allowed values: admin, standard, owner, panoptic.

User's preferred language. preferredLanguage is an optional element in the API, when it is not provided the system will default to English. When provided, preferredLanguage MUST be in ISO 639-1 format, for example - en: English.