|
Exegy instrument key strings may include an (optional) namespacing element, as indicated in the table below. The namespace token is simply preprended to the symbol portion of the Exegy key string or key.
| Namespace | Valid ASCII Tokens |
| "Search All" (default) | SEARCH |
| "Exegy Native" | NATIVE, NAT, N |
| "Alternate ID 1" | 1, A1, ALT1, ALTERNATE1 |
| "Alternate ID 2" | 2, A2, ALT2, ALTERNATE2 |
For example, where "CC" is the 2-character Exegy Country Code, "EX" the 1 or 2 character Exegy Exchange Code, "NN" one of the namespace tokens from the table above, and <SYMBOL> an Exegy symbol or a valid alternate ID, the standard fully qualified Exegy key string syntax is as follows:
CC:EX:[NN]<SYMBOL>Note that when an application requests a subscription with a key string of the form CC:EX:<SYMBOL>, the Ticker Plant searches its resident symbol lists is the following order: native Exegy symbol, alternate ID 1, alternate ID 2. When using alternate IDs, then, the scope of the search can be significantly narrowed (and thus sped up) by pre-pending the appropriate alternate-ID-namespace token to your alternate ID. Specifying the namespace also allows users to employ the following "short form" of key string for data requests:
[NN]<ALT ID>where "NN" is one of the appropriate ASCII namespace tokens and <ALT ID> is a valid alternate ID for your Ticker Plant installation.
Please see the Exegy Feed Reference for detailed information on Exegy symbology, provided there on a per-feed basis. Note also that the "WO" (WRITEONLY) objects are available to create alternate IDs.