Selerity is the market leader in detecting and delivering machine-readable event data in real time as events are breaking.
The Selerity Intelligence Platform pulls market-moving, factual information from primary sources using proprietary real-time search and extraction technology. The API is designed for automated investment professionals looking to incorporate events into their risk management and trading strategies.
We offer the following market-moving event data:
The real-time event data feed can be delivered via streaming API, and also as co-located data feed for low latency delivery.
What is event data and how is different from news?
Event data is highly structured factual information related to breaking events that trading firms can use to make reliable, real-time programmatic decisions. This form of information is structured and distributed more like market data than other forms of textual news.
Data What markets move from major US corporate earnings announcements?
When large public companies announce their earnings several markets can be impacted:
How does Selerity deliver its real-time event data?
Selerity has two primary data feed delivery options – ultra-low latency, UDP binary over multi-cast and the SeleritySync API, which is a JSON format over TCP/HTTPS. Most of Selerity’s latency sensitive clients take the binary feed over a fiber cross connect co-located in one of Selerity’s datacenter points-of-presence (POP)’s.
How does Selerity deliver static data such as calendar events, coverage lists, and other files?
Clients can access static data either through SeleritySync.com or the SeleritySync API.
How many datacenter POPs and data feed environments does Selerity have?
Selerity has two ultra-low latency distribution POPs – Equinix CH1 (Chicago, IL), Equinix NY2 (Secaucus, NJ). Each POP has three environments1 – production A, production B, and integration. Two production stacks allows Selerity to deliver hot-hot feeds. Selerity’s integration environment allows Selerity to test new search & extraction algorithms and also allows clients to test their parsers on simulated event data publications.
What is an Observation Message?
An observation message is a message containing a factual element associated with an event and its attributes. For example it will contain the entity the fact is related to (e.g. Microsoft), the measure (e.g. EPS), and the measurement (e.g. 2.11). It also contains other important metadata for machine-consumption. Please see the Event Data Service Specification and Data Model Document for details.
Why are there multiple Observation Messages for the same measure like EPS or Net Income?
Selerity uses multiple types of search & extraction algorithms with different characteristics to ensure ultra-low latency. For example, Selerity has an extraction algorithm based on a special technology that might take longer to produce, but has a higher accuracy score. We also run fully redundant sites that each produce their own extractions. Furthermore, there are typically several copies of a source document for a particular event that Selerity’s technology will extract from, which also creates their own Observation Messages.
Should I just focus on the Entity ID, Measure, and Measurement data fields when processing Observation Messages?
No. It is very important to always take into account the Period associated with the measure (e.g. WE-4W-2010- Nov-19) to ensure you’re looking at the desired data point and the Observation Status field. Observation Status tells you important information on how to interpret the extracted data. For more information on all of the different types of status, please refer to your Reference Data documentation.
What does the Observation Status NOT_OBSERVED mean?
All of Selerity’s relevant extraction algorithms for every event, so if an event occurs but the extraction algorithm could not find any data in the report, it will publish NOT_OBSERVED. For example, a company may choose to omit earnings guidance in their earnings release.
What does the Observation Status INVALID mean?
In very rare occasions, Selerity’s extraction algorithm will find a piece of targeted data, but will not be confident the extracted data is accurate. In these rare instances, the Observation Status will equal INVALID. These messages should always be discarded and not used.
What are .SPEC files and why do I need them for the UDP binary data feed?
Specification Files allow recipients to decode observation messages. A message specification is a data structure which explicitly defines the fields that can be expected within a given type of message and provides instructions for how to extract those fields from the underlying datagram’s payload. This allows Selerity to manage entitlements without impacting latency (i.e. all event data content sets are broadcasted over the Selerity network, but recipients need the right .SPEC files to make use of their associated messages).
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
|__cfduid||1||29 days 23 hours 59 minutes||The cookie is used by cdn services like CloudFare to identify individual clients behind a shared IP address and apply security settings on a per-client basis. It does not correspond to any user ID in the web application and does not store any personally identifiable information.|
|cookielawinfo-checkbox-necessary||0||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-non-necessary||0||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Non Necessary".|
|JSESSIONID||1||13 days 23 hours 59 minutes||Used by sites written in JSP. General purpose platform session cookies that are used to maintain users'' state across page requests.|
|vuid||1||1 years 11 months 28 days 23 hours 59 minutes||This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website.|
|XSRF-TOKEN||1||1 days 23 hours 59 minutes||The cookie is set by Wix website building platform on Wix website. The cookie is used for security purposes.|
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
|_ga||1||1 years 11 months 28 days 23 hours 59 minutes||This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site''s analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.|
|_gat_gtag_UA_45487328_32||0||This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.|
|_gat_UA-85023278-1||0||This is a pattern type cookie set by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website it relates to. It appears to be a variation of the _gat cookie which is used to limit the amount of data recorded by Google on high traffic volume websites.|
|_gid||1||23 hours 59 minutes||This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form.|
|_omappvp||1||10 years 11 months 10 days 23 hours 59 minutes||The cookie is set to identify new vs returning users. The cookie is used in conjunction with _omappvs cookie to determine whether a user is new or returning.|
|_omappvs||1||9 minutes||The cookie is used to in conjunction with the _omappvp cookies. If the cookies are set, the user is a returning user. If neither of the cookies are set, the user is a new user.|
|bscookie||1||1 years 11 months 29 days 11 hours 37 minutes||This cookie is a browser ID cookie set by Linked share Buttons and ad tags.|
|ELQSTATUS||1||1 years 1 months||This cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from, and the pages they visited. Once consent is provided, through a form submission by the visitor, we can associate a visitor's ID to individual characteristics and past behavior.|
|li_sugr||1||2 months 28 days 23 hours 59 minutes||This cookie is used to make a probabilistic match of a user's identity outside the Designated Countries.|
|lissc||1||11 months 29 days 23 hours 59 minutes||This cookie is provided by LinkedIn. This cookie is used for tracking embedded service.|
|UserMatchHistory||1||29 days 23 hours 59 minutes||Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences.|
|i18next||1||11 months 29 days 23 hours 59 minutes||No description|
|KV_CLIENT_SESSION_ID||1||11 months 29 days 23 hours 59 minutes||No description|
|pap_session||1||1 days 23 hours 59 minutes||No description|
|pap_wcaid_288||1||5 days 23 hours 59 minutes||No description|
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
|bcookie||1||1 years 11 months 29 days 11 hours 37 minutes||This cookie is set by linkedIn. The purpose of the cookie is to enable LinkedIn functionalities on the page.|
|ELOQUA||1||1 years 1 months||The domain of this cookie is owned byOracle Eloqua. This cookie is used for email services. It also helps for marketing automation solution for B2B marketers to track customers through all phases of buying cycle.|
|lang||1||session||This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website.|
|lidc||1||23 hours 59 minutes||This cookie is set by LinkedIn and used for routing.|