Daily API RoundUp: Route 360, Cenit IO, Cisco Flare

Every day, the ProgrammableWeb team is busy, updating its three primary directories for APIs, clients (language-specific libraries or SDKs for consuming or providing APIs), and source code samples. If you have new APIs, clients, or source code examples to add to ProgrammableWeb's directories, we offer forms (APIs, Clients, Source Code) for submitting them to our API research team. If there's a listing in one of our directories that you'd like to claim as the owner, please contact us at editor@programmableweb.com.

Eighteen APIs have been added to the ProgrammableWeb directory in categories including Artificial Intelligence, Messaging, and iPaaS. Several APIs for returning person and company information and an API for calculating travel time and most efficient routes are highlights. Here's a rundown of the latest additions.

APIs

The Motion Intelligence Route360° Mobility Analytics API calculates travel time from one source location to many targets at once. It supports car, public transport, bicycle and walking. It calculates travel time combined with statistics data, so developers can calculate the number of reachable people in a given time and their spending power. Developers can build applications to optimize retail networks, to evaluate real estate or to calculate coverage of a public service. This API is listed under the Mapping category. See ProgrammableWeb's complete list of Mapping APIs.

The Route360° API includes a service to get travel time polygons starting from a specified source point or a list of source points

The Route360° API allows users to get travel time polygons starting from a specified source point or a list of source points. Image: Motion Intelligence

Pushover is a mobile and desktop notifications service from Superblock. The Pushover Receipts and Callbacks API enables applications that send emergency-priority notifications to get a receipt parameter when they queue a notification. The receipt parameter is a 30-character string consisting of letter and numbers that can be used to query the status of a notification up to one week after it's been received. The Pushover Subscription API allows developers to collect subscriptions for an application in the form of Pushover user keys and then broadcast notifications to those subscribed users. These two APIs have been added to our Messaging category. See ProgrammableWeb's complete list of Messaging APIs.

Meya allows users to build cognitive chat bot apps that are powered by AI. The Meya Webhooks API provides way to be notified of certain events via Webhooks. For example notifications can be sent when a typing indicator is turned on or off by the bot, when a user message is received, when a bot message is sent, when certain user scope data is created, modified, or deleted, and when table scope data is created, modified, or deleted. A Meya REST API is also available. The Meya APIs are listed under the Artificial Intelligence category. See ProgrammableWeb's complete list of Artificial Intelligence APIs.

Meya.ai 101: Learn the basics on how to build a chat bot. Video: YouTube/Meya.ai

Cenit IO is an open platform for data and business integration. It allows the creation of custom data pipelines for process, storage and data movement between APIs. The Cenit IO Webhooks API is a simple HTTP request that contains JSON or XML formatted data relating to an event on Cenit. Cenit IO REST API is also available, and was updated in our directory recently. The Cenit IO APIs are listed under the iPaaS category. See ProgrammableWeb's complete list of iPaaS APIs.

Cisco Flare allows users to interact with things in their environment. The Cisco Flare Websocket API provides streaming, real-time interactions with the Flare mobile deployment environment. The API supports setting data values, retrieval, sending action messages, and subscribing push notifications. Data is encoded in JSON format. The Cisco Flare API is listed under the Internet of Things category. See ProgrammableWeb's complete list of Internet of Things APIs.

Cisco Flare API helps retailers create interactive customer experiences. Image Credit: Cisco DevNet

Roaring is a business contacts management service. The company provides several APIs for integrating their services with third-party applications. They have recently been added to our Contacts category and are listed below.

Roaring Company Overview API gives users a good overview about a company and provides data such as contact and address information, company form, status, tax registration, number of employees and name of the CEO.

Roaring Norwegian Company Overview API is similar to the Overview API but centered on Norwegian businesses.

Roaring SimpleSearch API allows applications to use the company name to find the company's organization number and legal form.

Roaring Signatory API contains the complete signatory text from the National Companies Registration Office and allows users to check who has the right to sign before entering an agreement with a customer or supplier.

Roaring BoardMembers API provides access to information on a company's Board, General Manager, Managing Director and authorized signatory.

Roaring Engagements API contains information about all company engagements a person has. It shows if a person is a board member, CEO or auditor. The request returned is the personal identification number.

Roaring CreditDecision API allows users to get an automatic answer to grant a credit or not.

Roaring Establishments API returns a company's geographical workplaces.

Roaring EconomyOverview API contains financial statements and financial ratios so that you get a good picture of the companies financial position. It is frequently used to make decisions if you should engage in a business relationship with a customer or supplier.

Roaring RightToSign API is used to automate customer registration and ensure users enter into binding agreements with the correct company signatory.

Roaring Event API returns information about all changes in the company data that has happened after the date you provide in the request.

 

Comments (0)