The Latest News On The API Economy
Searching: No Search Term , No Filters
Flashpoint announced the fourth version of its business risk intelligence API. The latest feature added to the API is Risk Intelligence Observables (RIOs), which the company contends move beyond traditional security indicators. A number of Flashpoint partners have already utilized v4.
GLEIF has announced the launch of its Legal Entity Identifier (LEI) Look-Up API which provides access to the organization’s complete LEI data pool in real time. The LEI is a 20-digit, alpha-numeric code that helps identify legal entities that participate in financial transactions.
Compliance.ai has launched a new developer portal that provides an API, documentation, code samples, and other tools developers can use to build applications integrated with financial regulation data. Sources of information include federal and state agencies, regulatory publications, and more.
As part of the series on getting the most ROI out of your API, this case study shows how Intercom grew its developer program by tracking key indicators across a range of business goals — platform reach, developer engagement, financial impact — that aligned with their API strategy and business plan.
Deciding what metrics matter depends on the overall strategy goals and business model that aligns with your APIs. This is why defining the business model was one of the first steps in your decision series. Now we need to make sure our evaluation framework matches back up to what we set out to do.
Our series on getting the most ROI out of your API has looked at the business and technical decisions to make when building your API strategy. We've also made decisions around how to engage with developers and build a developer community. A key aspect to this involves creating a developer portal.
Now that your API has been published and external developers are beginning to consume it, our focus shifts again towards a balance between business and technical issues. In this part of the series we take a look at how a business can leverage the technical API to grow a developer community?
Congratulations, your API is now production ready. Next you will need to provide documentation to consumers so they can integrate the data and services you have exposed via API quickly. This part covers API documentation including the role of API specs and a number of available tools.
At this point in your API journey, you have made a number of business decisions and a couple of technical ones. Now, several crucial decisions need to be made around security. Securing an API is an often neglected task, yet doing so is at the heart of an effective API strategy.
With business decisions in place for your API strategy, we've moved on to some more technical issues, such as the reference and API architectures, and the choice of API specification formats. Now in this part, let's take a look at the range of API lifecycle tooling available.
The first few decisions around building an API strategy centered on the business components. With those in place, building the API is now possible. The API strategy moves to becoming more of a technical concern for several steps as you resolve API design, security, and API Ops.
As you go through the decisions involved in setting up the business side of managing an API, it becomes clear that you will need to treat the API as a product in order for it to succeed. But what does that mean and how do you do that? This part takes you through the things you need to consider.
When defining your API strategy, a crucial decisions to make is what API business model will be used. A business model is a way to understand all of the system components that come together to allow you to create a project and add value. It helps you answer how you will make money from your API.
At this point in an organization's API journey, the groundwork has been laid and it is time to think about one of the first big decisions in creating our APIs: which data and services to open first as APIs. This article looks at how different API business models can affect this decision.
This is Part 3 of ProgrammableWeb's series on maximizing the ROI on your API. In this part we explore how to build a team that can build internal support by liaising with various business units. The article also looks at putting together the right team to drive your API strategy.
When a business starts its API journey, it has to make a number of key decisions. Not surprisingly, at each decision point, multiple options branch out it can become easy to become confused and cautious quickly. How do you make the decisions to embark on a successful API journey?
Nineteen APIs have been added to the ProgrammableWeb directory in categories such as Payments, Healthcare, and Charts. Highlights today include an API which can create charts out of financial stock market results and an API that provides blood glucose data for diabetes applications.
SugarCRM has launched an SDK for the mobile version of its popular CRM product. The mobile SDK offers a similar developer experience to the desktop SDK version. With the SDK, users can create custom experiences that integrate with existing apps, workflows, and business tools.
DropBuddies, the Postmates of Nigeria, launched an API that allows local businesses to include courier services directly within their apps. Without leaving the integrated business' app, users get a delivery quote, ETA, and book a delivery. Once booked, users can track shipments through delivery.
Dexcom, a continuous glucose monitoring solution provider, has launched an API that grants access to continuous glucose monitoring data. Use of such data is completely at the discretion of the user, on an app by app basis. The goal is to give users options to interact with glucose data.