The hype surrounding the API economy is not exaggerated. Like almost all eruptions on the IT market, application development interfaces caused an uproar in 2015, and no less is expected for 2016. It’s not a new thing; since 2012, APIs have been growing as the real glue between software creation equipment, data management and the business infrastructure. Without them, it’s difficult to compete now and in the future.
APIs are the real key for creating products and services and for generating revenue and brand commitment. Nowadays, no one in the market doubts the importance of APIs in the B2B business (business to business), either through public interfaces or the development of internal APIs. According to the study ‘Global API Market Forecast to 2017’, the API business generated 113 billion dollars in 2012, and it is expected to grow by 8% per year until 2017.
In another recently published report, ‘2016 Connectivity Benchmark Report’, the company Mulesoft provides some very interesting information about this API economy. One of the most impacting conclusions is that 91% of companies have a strategy that is currently being implemented based around these application development interfaces, or they are thinking of starting it up this year. In most cases, it is focused on three fields of business: software integration with existing platforms or applications; the creation of revenue from IT and business, and increasing speed and providing business with IT resources.
This chart perfectly shows the distribution of effort:
Another piece of really interesting information from the report is what companies expect to earn with the development of these types of API related strategies: 33% of organizations with more than 100,000 employees in the study expect to earn more than 10 million dollars using these app development interfaces. Furthermore, 26% of those surveyed plan on generating between one and five million dollars. Here is a chart with all the results from the report drawn up by Mulesoft.
These are our predictions within the world of the APIs:
APIs: a resource for all
2016 will be the year in which no company in the world can think that their future will not depend on one or several APIs, either internal or third party. Without a doubt, the digital products and services economy has become the APIs economy. And that’s a reality there’s no escaping from. This will speed up the integration process of many company’s departments beyond technical equipment. The universalization of APIs will enable four aspects:
● Accelerating the digitalization of processes.
● The adoption of applications and platforms by third parties.
● Business analysis.
● The monetization of these digital channels’ products and services.
APIs could become the huge differentiating element of banking in the future. Banks who understand that application development interfaces are the perfect instrument to make money with third parties and that changing from traditional banking to becoming Platforms as a Service (PaaS) will win in the future with their relationships with account information services (AIS) and the new Payment Initiation Services (PIS), which are taking business away from financial institutions.
To regulate this context, in October 2015, the EU updated the Payment Services Directive (PSD2), which gives banks the opportunity to do business with open service platforms by using APIs The legislation forces banks to give third parties access, with permission from their customers, to account and payment related information. Banks such as BBVA and JP Morgan Chase have understood this new scenario and are willing to convert an obligation into an opportunity: take advantage of this revenue asset. This is what’s known as the ‘platformification’ of banking.
There are two interesting reports about this transformation of banking into service platforms: ‘2016 Retail Banking Trends and Predictions’ is a good summary of the radical change in banking institutions, analyzing a large number of the agents who have implemented this change; and a second report, ‘The disruption of banking’, which is an analysis by the magazine The Economist from the end of 2015. The second report gives many keys about the new scenario in which banking products will compete with their new and powerful rivals, fintech.
APIs for the architecture of applications based on microservices
The architecture of microservices is the new paradigm of DevOps equipment. What does it involve? In the development of applications as a group of microservices that are executed independently, and which normally communicate with the different APIs via HTTP requests.
This has several advantages:
● If some of the microservices in an application, whether it be the user interface (front-end) or back-end services , have an error, the development equipment can resolve bugs separately without having to send the entire application to production with the development improvements.
● Something similar occurs with scalability processes, either up (growth) or down (decrease). In an application based on microservices development, capacity growth is simpler and more rational because each one is an independent service.
● The business logic is separated and each part is independent.
● Integration mechanisms such as ESB (Enterprise Service Bus, a component of the Service Oriented Architecture or SOA) have been rejected in favor of lightweight mechanisms such as applications based on the queuing systems.
This article by Martin Fowler and James Lewis is often brought up to explain what microservices are for and what they are used for in the development of applications. The report explains how APIs are key to the flexibility and agility of microservices.
Fowler’s speech is also interesting for understanding microservices:
Use of APIs: measure, measure, measure
Here at BBVAOpen4U, we already analyzed the best API monitoring tools, without which it is difficult to know what the actual performance of these interfaces is. With APIs, development equipment can analyze performance and correct bugs or errors that interfere in its performance in a timely manner. Mashape Analytics, Akana Envision and CA App Synthetic Monitor are three examples.
API security is a priority
The growth of APIs as application development and integration instruments, especially in the field of mobile device development, attracts those who work on finding weaknesses. Nowadays most APIs base their security on a protocol framework creation, such as OAuth2.
By using application development interface capital for their business, large IT companies such as Google, Facebook, and Twitter use this authorization and security system for third parties. The system is based on the creation of access tokens so that third party developers can use the API without over committing the tool. A credentials system based on a username and password is more delicate, because an irregular breakdown of this protocol would result in having to change the access for all that API’s customers.
Taking a customer through the entire buying process until it is formalized is an arduous journey and one that faces the constant possibility of the customer leaving. However, there are ways to make the buying decision happen if you are given facilities such as agile, secure financing.
In a connected world, APIs are the glue that keeps all the parts that form our day-to-day lives in place. The same way the power of glue depends on the material it is used on and the knowledge of its properties, APIs are only as useful as their documentation allows for.
There are different solutions to monitor the performance of an API, in terms of traffic, quality and speed of the answers it provides. Detecting faults in the code or quantifying the generated revenues are also some of the options offered by these useful tools.
Please, if you can't find it, check your spam folder
×
The email message with your ebook is on the way
We have sent you two messages. One with the requested ebook and one to confirm your email address and start receiving the newsletter and/or other commercial communications from BBVA API_Market
×
PROCESSING OF PERSONAL DATA
Who is the Data Controller of your personal data?
Banco Bilbao Vizcaya Argentaria, S.A. (“BBVA“) with registered address at Plaza de San Nicolás 4, 48005, Bilbao, España and Tax ID number A-48265169 . Email address: contact.bbvaapimarket@bbva.com
What for and why does BBVA use your personal data for?
For those activities among the following for which you give your consent by checking the corresponding box:
to receive newsletter from BBVA API_Market through electronic means;
to send you commercial communications, events and surveys relating to BBVA API_Market to the e-mail address you have provided.
For how long we will keep your data?
We will keep your data until you unsubscribe from receiving our newsletter or, if applicable, the commercial communications, events and surveys to which you have subscribed. Whether you unsubscribe or whether BBVA decides to end the service, your details will be deleted.
How can I unsubscribe to stop receiving newsletters and/or communications from BBVA API_Market?
You can unsubscribe at any time and without need to indicate any justification, by sending an email to the following address: contact.bbvaapimarket@bbva.com
To whom will we communicate your data?
We will not transfer your personal data to third parties, unless it is mandatory by a law or if you have previously agreed to do so.
What are your rights when you provide us with your information?
You will be able to consult your personal data included in BBVA files (access right)
You can modify your personal data when they are inaccurate (correction right)
You may request that your personal data not be processed (opposition right)
You may request your personal data be deleted (suppression right)
You can request a limitation on the processing of your data in the allowed cases (right of limitation of processing)
You will be able to receive, in electronic format, the personal data you have provided to us, as well as to transmit them to another entity (portability right)
You are responsible for the accuracy of the personal data you provide to BBVA and to keep them duly updated. If you believe that we have not processed your personal data in accordance with regulations, you can contact the Data Protection Officer of BBVA at the following address dpogrupobbva@bbva.com.
You can find more information in the “Personal Data Protection Policy” document on this website.
×
PROCESSING OF PERSONAL DATA
Who is the Data Controller of your personal data? Banco Bilbao Vizcaya Argentaria, S.A (“BBVA“), with registered address at Plaza de San Nicolás 4, 48005, Bilbao, España, and Tax ID No. A-48265169. Email address:contact.bbvaapimarket@bbva.com
What for and why does BBVA use your personal data for?
For the execution and management of your request, specifically, download the requested e-book/s.
BBVA informs you that, unless you indicate your opposition by sending an email to the following address: contact.bbvaapimarket@bbva.com, BBVA may send you commercial communications, surveys and events related to products and/or services of BBVA API Market through electronic means.
For how long we will keep your data?
We will keep your data as long as necessary for the management of your request, and to receive commercial communications, events and surveys. BBVA will keep your data until you unsubscribe to stop receiving our newsletters or, where appropriate, until the end of the service. Afterwards, we will destroy your data.
How can I unsubscribe to stop receiving newsletters and/or communications from BBVA API Market?
You can unsubscribe at any time and without need to indicate any justification, by sending an email to the following address: contact.bbvaapimarket@bbva.com
To whom will we communicate your data?
We will not transfer your personal data to third parties, unless it is mandatory by a law or if you have previously agreed to do so.
What are your rights when you provide us with your information?
You will be able to consult your personal data included in BBVA files (access right)
You can modify your personal data when they are inaccurate (correction right)
You may request that your personal data not be processed (opposition right)
You may request your personal data be deleted (suppression right)
You can request a limitation on the processing of your data in the allowed cases (right of limitation of processing)
You will be able to receive, in electronic format, the personal data you have provided to us, as well as to transmit them to another entity (portability right)
You can exercise before BBVA the aforementioned rights through the following address: contact.bbvaapimarket@bbva.com
You are responsible for the accuracy of the personal data you provide to BBVA and to keep them duly updated.
If you believe that we have not processed your personal data in accordance with the regulations, you can contact the Data Protection Officer at the following address: dpogrupobbva@bbva.com
You can find more information in the “Personal Data Protection Policy” document on this website.
Banco Bilbao Vizcaya Argentaria, S.A. owner of this portal uses cookies and/or similar technologies of its own and third parties for the purposes of personalization, analytics, behavioral advertising or advertising related to your preferences based on a profile prepared from your browsing habits (e.g. pages visited). If you wish to obtain more detailed information, consult our Cookies Policy.
Cookie settings panel
These are the advanced settings for first-party and third-party cookies. Here you can change the parameters that will affect your browsing experience on this website.
Technical Cookies (required)
These cookies are used to give you secure access to areas with personal information and to identify you when you log in.
Name
Owner
Duration
Description
gobp.lang
BBVA
1 month
Language preference
aceptarCookies
BBVA
1 year
Configuration Accepted Cookies
_abck
BBVA
1 year
Helps protect against malicious website attacks
bm_sz
BBVA
4 hours
Helps protect against malicious website attacks
ADRUM_BTs
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BT1
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BTa
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BT
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
xt_0d95e
Salesforce Marketing Cloud
Session
Remember user preferences (if any)
__s9744cdb192d044faa1bf201d29fafd1e
Salesforce Marketing Cloud
Session
Remember user preferences (if any)
wpml_browser_redirect_test
WPML
Session
Text translation in the portal
wp-wpml_current_language
WPML
24 hours
Text translation in the portal
They are used to track the activity or number of visits anonymously. Thanks to them we can constantly improve your browsing experience
Your browsing experience is constantly improving.
With your selection, we cannot offer you a continuously improved browsing experience.
Name
Owner
Duration
Description
AMCV_***
Adobe Analytics
Session
Unique Visitor IDs used in Cloud Marketing solutions
AMCVS_***
Adobe Analytics
2 years
Unique Visitor IDs used in Cloud Marketing solutions
demdex (safari)
Adobe Analytics
180 days
Create and store unique and persistent identifiers
sessionID
Adobe Analytics
Session
Launch's internal cookie used to identify the user
gpv_URL
Adobe Analytics
Session
Adobe Analytics plugin: getPreviousValue Capture the value of a certain variable in the following page view, in this case the prop1
gpv_level1
Adobe Analytics
Session
Cookie used to store the DataLayer levl1 of the previous page.
gpv_pageIntent
Adobe Analytics
Session
Cookie used to store the pageIntent of the previous page.
gpv_pageName
Adobe Analytics
Session
Cookie used to store the pagename of the previous page.
aocs
Adobe Analytics
Session
Cookie that stores the first values collected at the beginning of a process.
TTC
Adobe Analytics
Session
Cookie used to store the time between the App Page Visit event and the App Completed event.
TTCL
Adobe Analytics
Session
Cookie used to store the time between the LogIn event and App Completed.
s_cc
Adobe Analytics
Session
Determine if cookies are active
s_hc
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_ht
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_nr
Adobe Analytics
2 years
Determine the number of user visits
s_ppv
Adobe Analytics
Permanent
Adobe Analytics plugin: getPercentPageViewed Determine what percentage of the page a user views
s_sq
Adobe Analytics
Session
ClickMap/ActivityMap features
s_tp
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_visit
Adobe Analytics
2 years
Cookie used by Adobe to know when a session has been started.
They allow the advertising shown to you to be customized and relevant to you. Thanks to these cookies, you will not see ads that you are not interested in.
The advertising is customized to you and your preferences.
Your choice means you will not see customized ads, only generic ones.
Name
Owner
Duration
Description
OT2
VersaTag
90 days
VersaTag Cookie used to store a user id and the number of user visits.
u2
VersaTag
90 days
VersaTag Cookie where the user ID is stored
TargetingInfo 2
MediaMind
1 year
Cookie that serves to assign a unique random number that generates MediaMind.
These cookies are related to general features such as the browser you use.
Your experience and content have been customized.
With your selection, we cannot offer you a continuously improved browsing experience.
Name
Owner
Duration
Description
mbox
Adobe Target
9 days
Cookie used by Adobe Target to test user experience customization.
×
Looks like you’re browsing from Mexico, so let’s show you the custom content for your
location. Change
Looks like you’re browsing from Spain, so let’s show you the custom content for your
location. Change
Select a country
In order to access the private area and corresponding sandbox, select the country of the APIs you want to use.