Trade Ideas Program API details

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.

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.

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.

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.

In the last 6 months we had more than four nines availability outside of scheduled maintenance windows (which are always outside trading hours).

We run in two DCs in London (Equinix and Digital Realty).