If It’s Available via Your Website, It Should Be Available via an API
APIs are not the latest technological trend, they are the next iteration of the web. In 1998, we were wondering if we should have a website for our business, and in 2018, businesses are realizing they don’t just need to be doing business via their own website and that all their digital assets need to be available for consumption on any platform via any type of application. If there is a product, service, data set, document, or any other digital resource already available via your public website, it should also be available via an API for consumption in any other application beyond just your website and mobile applications.
Having all of your digital assets available as simple web APIs, articulated as part of your overall business strategy and available for integration across internal, partner, and public projects are how you compete across today’s digital landscape. You need all of your products, services, and other digital resources available for use in any known, or potentially unknown application that may come along. If something is available on your website, it should also be available for delivery within a mobile application without much extra work, using simple, security, but self-service web APIs. https://goo.gl/eNiFa2
Xignite’s Webhook API For Financial Alerts
#ICYMI: Our partner Xignite has launched a powerful new webhook API for getting financial market notifications pushed to the URL of your choice. Allowing developers to craft individual subscriptions to the robust financial markets data catalog Xignite brings to the table. Xignite provides a testable form for defining each of the alerts you create for the Xignite financial data APIs, allowing you define using the following data points: a href=“https://www.xignite.com/product/market-data-alerts#/DeveloperResources/request”>
– IdentifierType — The type of identifier used (ie. Symbol)
– Identifier — The specific identifier value for this alert.
– API — Which of the Xignite APIs you want to receive alerts.
– Condition — Allowing you to apply specific conditions to alerts.
– Reset — Determines the alert frequency, and if it resets itself.
– CallbackURL — The URL that the webhook alert will call when an event occurs.
– StartDate — Giving the alert a start date of when it will run.
– EndDate — Giving the alert an end date of when it will stop running. https://goo.gl/pbzgPZ
