Schemas

SpiderRock schemas and their related live data objects, records, messages, classes, and instances are a key part of the SpiderRock open message architecture. SpiderRock Connect has hundreds of schemas, and while most schemas and their instance objects or messages can only be viewed or received by clients, some can also be created or updated as well depending on the schema's permissions and the client's user configurations.

The schemas themselves are organized into topics for convenience.

Schemas are also assigned either an MLink Token or a SRSE Product Code which is part of how they are provisioned. When you connect through one of our APIs (MLink or SRSE) your access to messages or records will be restricted to only those for which an associated MLink Token or SRSE Product Code has been provisioned for your username.

Some schemas contain market and related data that is distributed under license from an exchange or other market data organization or vendor. Individual message or record instances will only be available if you have the associated access codes provisioned for your username.

Finally, many messages or records contain private client information (the schema will either have an accnt or clientFirm field in the message). These messages or records are only visible if your username is provisioned to access them.

The best way to understand SpiderRock schemas if you are approaching them for the first time is to explore this Schema site. Gain access to one of our MLink or SRSE APIs and splunk around.

NOTE: Almost all of the information in the Message Schemas section of this site is code generated and might change as we release newer versions of the system. As a result, a best practice would be, when writing code against our APIs, to use techniques that would not be 'fragile' to simple schema changes such as adding a field to a schema or a value to an enum.

Happy exploring!
The SpiderRock Team