Market:Security

Announces the current state of a Security.

This subscription is only available for symbols that offer Asset in their SubscriptionData.

**Controller:**Market
Topic: Security![Code].[Market]
Action: Sub
Permissions: Zenith/Market
Server-side Unsubscribe: Yes

Topic Format

Fields

Payload

The server will always send out the full state of a Security immediately after subscribing, as well as during a server resynchronisation and upon a new trading day.

As the Code and Market are only sent with a full state, the consumer must use the topic to identify the symbol updates are for.

All other updates besides the first should be treated as diff updates, identifying any fields that have changed. The Output column in the table below describes the potential values for each field.

• Fixed: This field does not change, and will never be null in an update. Always supplied in the first update.
• Optional: This field can change, and updates will never be null.
• Nullable: This field can change, and updates can be null to clear its value.

A field that is not included in an update should be considered unchanged from its previous value.

If an Optional or Nullable field is never supplied, the default for that field applies.

Symbol Leg object

Code Example:

websocket.send(JSON.stringify(
{
 Controller:"Market",
 Action:"Sub",
 Topic:"Security!BHP.ASX",
 Confirm:true
});

Sample Responses:

//First publication provides all fields (majorityomitted for brevity)
{
 "Controller":"Market",
 "Topic":"Security!BHP.ASX",
 "Data":
 {
  "Code":"BHP",
  "Market":"ASX",
  "Last":10.0
 }
}
//Confirmation will be sent after the first response
{
 "Controller":"Market",
 "Topic":"Security!BHP.ASX",
 "Action":"Sub",
 "Confirm":true
}
//Subsequent publications provide only the changed fields
{
 "Controller":"Market",
 "Topic":"Security!BHP.ASX",
 "Data":
 {
  "Last":10.1
 }
}