The Acuris ETF Ideas API gives you live push of ETF idea open and close event messages from contributors in all regions
The API supports a wide set of mapping identifiers, allowing you to use the data with confidence in your quantitative models.
The API supports a wide set of “as-at” mapping identifiers, allowing you to use the data with confidence in your quantitative models.
Why have we chosen HTTP Long Polling and event sourcing as our distribution API?
Previously this was not the case and our first version was an actual push rather than a logical push. Our learning from this was that most clients preferred to have as much control as possible. Long polling with a consistent event numbering achieves this and gives a good tradeoff between latency and simplicity.
You own the checkpoint, giving you the freedom to replay events at any time, bootstrap new systems without depending on us, and removes the need for reconciliation processes.
You can also upgrade your clients without depending on us to update any configuration – you don’t have to give us access to your systems making them more secure.
How do we ensure that it goes out to all buy-sides at same time?
Open long poll connections are all treated equally, so when a new event is received it is pushed to all open connections. Whilst there can be small differences on individual messages, on average delays will be equally distributed across clients.
What is actually taking place when a contributor puts an idea into the system?
When an author sends an idea from our Web UI we record the idea event in our event store database. It is then processed by our event pipeline and served to any open long poll connections. Messages are published with the timestamp of when the data was entered into the Web UI.
How do you treat author IDs when two companies merge?
If two companies merge, we move the authors from one company to another so the same author ID will be present for more than one company ID.
What is the uptime/availability of your system?
In the last 6 months we had more than four nines availability outside of scheduled maintenance windows (which are always outside trading hours).
Where is the API hosted?
We run in two DCs in London (Equinix and Digital Realty).
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.|