Overview:
This research assesses the market challenges and opportunities associated with development and support of IoT APIs. The report evaluates leading companies, solutions, technologies, and use cases.
The report also analyzes the role of IoT APIs in support of key functional components of the IoT Ecosystem including Identity Management, Mediation, and other operational support functions. The report includes detailed forecasts for IoT API revenue globally, regionally, and by industry verticals for the period 2023 to 2028.
Select Report Findings
- The overall IoT API market will reach $289.4 billion by 2028, led by North America at $103.4 billion.
- One of the best market drivers for IoT APIs is their ability to facilitate the exposure of APIs to attract IoT companies, application companies, and individual IoT app/service developers.
- Over the long-term, we see developers using APIs to both establish/support IoT aps and services as well as a means of employing virtual control of Smart Objects in the Real World.
- While many companies offer their own APIs, there are some that do not provide open APIs. There is an opportunity for API management companies to take over the task of managing the IoT API program on behalf of a given company.
- Major IoT Data source segments include Smart Systems (systems interacting with other systems via automation), Ambient Systems (data from the business and/or consumer environment), Personal Assistants (intelligent agents that act on behalf of users), and Quantified Self (self-improving products) to name a few.
Application Programming Interfaces (API) represent a set of requirements that describes how applications should communicate in a systematic manner. APIs are important in the IoT world for the same reason that they are important in general - they provide a means of decoupling functionality from platforms. In other words, one is not married to an IoT platform with APIs.
The Internet of Things (IoT) is anticipated by many to have great potential to deliver business value. Billions of devices generate data associated with various enterprise and consumer lifestyle events such as shopping activity, utility usage and other smart grid data, advertisement response, status of goods in transport, weather forecasts, traffic conditions, vehicle maintenance, public transport, downloads and usage of applications, and much more.
IoT APIs are the cornerstone of signaling, communications, and data exchange. This is arguably critically important in the case of database access for various transactions. The prudent use of APIs provides operational flexibility, scalability, and enhanced opportunities for new application and service deployment. APIs will become table stakes for IoT interoperability between platforms, devices, and gateways. Moreover, IoT APIs will become a critical part of major IoT application and service developer programs.
We see an especially important role for IoT APIs in the support of signaling, communications, and information exchange between certain key authoritative databases including Identity Database (IDDB), Permissions Database, and Device Discovery Database. Each of these databases will be accessed via IoT APIs in support of the IoT Mediation function necessary for the long-term scalability of IoT networks and systems. Furthermore, IoT APIs will be at the foundation of data interchange in the emerging IoT Data as a Service (IoTDaaS) marketplace.
Select Companies in Report:
- 3Scale
- Akana
- Alcatel
- Amazon
- Angus.ai
- API Axle
- Apiary
- Apify
- Apigee
- APIphany
- Arrow Intelligent Services
- AT&T
- Atmosphere
- Axway
- Beagle Sense
- Beebotte
- Brivo Labs SAM
- Bt.tn
- CA API Management
- Carvoyant
- ClearBlade
- Cloud Elements
- CloudRail
- CubeSensors
- Cumula
- Deployd
- DeviceHub
- DreamFactory
- Emergent One
- GardenKit
- Google
- HERE Fleet
- Illiri
- Interpair
- IOStash
- Kaa Admin
- Kasabi
- Konekt
- Kong
- Layer 7 Technologies (CA)
- littleBits
- Mashape
- Mashery
- Meeti
|
- Meshblu
- Mnubo
- Mojio
- Muzzley
- Nest
- Netatmo
- Netbeast
- Neura
- Nevatech Sentinet
- OGC SensorThings
- OpenSensors
- Paraimpu
- Particle
- Pinoccio
- Predix
- PSA Group
- RacoWireless
- REST United
- Restlet
- Samsung
- Scio
- scriptr.io
- Sense Tecnic
- SenseIoT
- Sensorberg
- Socrata
- Space Bunny
- StrongLoop
- Swagger
- Temboo
- The Beacon Registry
- theThings.IO
- thingk.me
- ThingPark
- Thinking Things
- Tyk
- URX
- VIMOC Technologies
- Vordel
- Weaver
- WebServius
- Wia
- WSO2
|
Table of Contents
1. Executive Summary
2. API Management
- 2.1. API Management Platform Components
- 2.1.1. API Gateway
- 2.1.2. API Developer Portal
- 2.1.3. API Analytics
- 2.1.4. API Monetization
- 2.2. API Management Considerations
- 2.2.1. Core Capabilities
- 2.2.2. Quality of Service Attributes
- 2.2.3. Vendor Assessment
- 2.2.4. People Criteria
- 2.2. IoT API Management Challenges
- 2.2.1. Wide Range of Protocols
- 2.2.2. Security Risks
- 2.2.3. Mobility Issues
- 2.2.4. Reliability Requirements
- 2.2.5. Scalability Needs
- 2.2.6. Interoperability Needs
3. API Management Tool Providers and Solutions
- 3.1. 3Scale
- 3.2. Akana
- 3.3. Alcatel
- 3.4. API Axle
- 3.5. Apiary
- 3.6. Apify
- 3.7. Apigee
- 3.8. APIphany
- 3.9. Atmosphere
- 3.10. Axway
- 3.11. CA API Management
- 3.12. Cloud Elements
- 3.13. Cumula
- 3.14. Deployd
- 3.15. DreamFactory
- 3.16. Emergent One
- 3.17. Kasabi
- 3.18. Kong
- 3.19. Layer 7 Technologies (CA)
- 3.20. Mashape
- 3.21. Mashery
- 3.22. Nevatech Sentinet
- 3.23. REST United
- 3.24. Restlet
- 3.25. Socrata
- 3.26. StrongLoop
- 3.27. Swagger
- 3.28. Tyk
- 3.29. Vordel
- 3.30. WebServius
- 3.31. WSO2
4. IoT API Market Drivers
- 4.1. Access to IoT Platforms, Devices, Gateways, and More
- 4.2. IoT and Data as a Service
- 4.2.1. Data as a Service
- 4.2.2. DaaS Federation
- 4.2.3. DaaS and IoT
- 4.3. IoT Mediation
- 4.3.1. IoT Platform to Platform Mediation
- 4.3.2. IoT Platform to Device Mediation
- 4.3.3. IoT Device to Device Mediation
- 4.3.4. IoT Mediation Roadmap
5. Monetizing IoT APIs
- 5.1. IoT API Business Models
- 5.1.1. Peer Support of Platforms, Devices, and Gateways
- 5.1.2. Supporting the API Developer Community
- 5.1.3. Data and Database Transactions
- 5.2. IoT APIs and Data
- 5.2.1. IoT API support in Data Management
- 5.3. IoT APIs Monetized through IoT Mediation
- 5.3.1. IoT APIs support Identity
- 5.3.2. IoT APIs support Permission
- 5.3.3. IoT APIs support Device Discovery
6. IoT API Forecasts 2023-2028
- 6.1. Global IoT API Revenue 2023-2028
- 6.1.1. IoT API Revenue
- 6.1.2. IoT API Revenue by Region
- 6.1.3. IoT API Revenue by Application, Device, Platform, and Deployment
- 6.1.4. IoT API Revenue by Market Sector
- 6.1.5. IoT API Revenue by API Category
- 6.1.6. IoT API Revenue by Industry Vertical
7. North America IoT API Revenue 2023-2028
- 7.1.1. North America IoT API Revenue
- 7.1.2. North America IoT API Revenue by Region
- 7.1.3. North America IoT API Market by Application, Device, Platform, and Deployment
- 7.1.4. North America IoT API Revenue by Market Sector
- 7.1.5. North America IoT API Revenue by API Category
- 7.1.6. North America IoT API Revenue by Industry Vertical
8. Asia Pacific IoT API Revenue 2023-2028
- 8.1.1. APAC IoT API Revenue
- 8.1.2. APAC IoT API Revenue by Region
- 8.1.3. APAC IoT API Market by Application, Device, Platform, and Deployment
- 8.1.4. APAC IoT API Revenue by Market Sector
- 8.1.5. APAC IoT API Revenue by API Category
- 8.1.6. APAC IoT API Revenue by Industry Vertical
9. Europe IoT API Revenue 2023-2028
- 9.1.1. Europe IoT API Revenue
- 9.1.2. Europe IoT API Revenue by Country
- 9.1.3. Europe IoT API Market by Application, Device, Platform, and Deployment
- 9.1.4. Europe IoT API Revenue by Market Sector
- 9.1.5. Europe IoT API Revenue by API Category
- 9.1.6. Europe IoT API Revenue by Industry Vertical
10. Latin America IoT API Revenue 2023-2028
- 10.1.1. Latin America IoT API Revenue
- 10.1.2. Latin America IoT API Revenue by Country
- 10.1.3. Latin America IoT API Market by Application, Device, Platform, and Deployment
- 10.1.4. Latin America IoT API Revenue by Market Sector
- 10.1.5. Latin America IoT API Revenue by API Category
- 10.1.6. Latin America IoT API Revenue by Industry Vertical
11. Middle East and Africa IoT API Revenue 2023-2028
- 11.1.1. MEA IoT API Revenue
- 11.1.2. MEA IoT API Revenue by Country
- 11.1.3. MEA IoT API Market by Application, Device, Platform, and Deployment
- 11.1.4. MEA IoT API Revenue by Market Sector
- 11.1.5. MEA IoT API Revenue by API Category
- 11.1.6. MEA IoT API Revenue by Industry Vertical
12. Conclusions and Recommendations
13. Appendix
- 13.1. IoT Protocols and Standards
- 13.1.1. Infrastructure
- 13.1.2. Discovery
- 13.1.3. Data Protocols
- 13.1.4. Communication / Transport Layer
- 13.1.5. Semantic
- 13.1.6. Multi-layer Frameworks
- 13.1.7. Security
- 13.1.8. Vertical Specific Standards
- 13.1.9. IoT Management
- 13.2. IoT API Solutions
- 13.2.1. AT&T M2X Keys API
- 13.2.2. Interpair API
- 13.2.3. Kaa Admin API
- 13.2.4. Meshblu API
- 13.2.5. Particle API
- 13.2.6. SenseIoT API
- 13.2.7. Weaver API
- 13.2.8. Sensorberg API
- 13.2.9. IOStash IoT PaaS API
- 13.2.10. Mnubo API
- 13.2.11. DeviceHub API
- 13.2.12. Predix Time Series API
- 13.2.13. Wia API
- 13.2.14. Meeti API
- 13.2.15. Omega Ricochet API
- 13.2.16. Paraimpu API
- 13.2.17. Temboo API
- 13.2.18. Netbeast API
- 13.2.19. Google Weave API
- 13.2.20. URX App Search API
- 13.2.21. Amazon Alexa Voice Service API
- 13.2.22. Bt.tn API
- 13.2.23. thingk.me API
- 13.2.24. Mojio API
- 13.2.25. PSA Group Connected Car API
- 13.2.26. Muzzley API
- 13.2.27. Amazon Alexa Smart Home Skills API
- 13.2.28. Telematic REST API
- 13.2.29. Beebotte API
- 13.2.30. scriptr.io API
- 13.2.31. The Beacon Registry API
- 13.2.32. Predix Traffic Planning API
- 13.2.33. theThings.IO REST API
- 13.2.34. littleBits Cloud API
- 13.2.35. Konekt API
- 13.2.36. CloudRail API
- 13.2.37. Predix Asset Data API
- 13.2.38. ClearBlade API
- 13.2.39. Samsung ARTIK Cloud API
- 13.2.40. Beagle Sense API
- 13.2.41. CubeSensors API
- 13.2.42. GardenKit API
- 13.2.43. Thinking Things API
- 13.2.44. Arrow Intelligent Services API
- 13.2.45. Pinoccio API
- 13.2.46. VIMOC Technologies API
- 13.2.47. Scio API
- 13.2.48. Nest API
- 13.2.49. Neura API
- 13.2.50. Space Bunny API
- 13.2.51. Netatmo API
- 13.2.52. Angus.ai API
- 13.2.53. Sense Tecnic WoTkit API
- 13.2.54. OGC SensorThings API
- 13.2.55. OpenSensors API
- 13.2.56. Brivo Labs SAM API
- 13.2.57. Carvoyant API
- 13.2.58. Illiri API
- 13.2.59. ThingPark API
- 13.3. IoT APIs in Industry Verticals and Functional Areas
- 13.3.1. 3D
- 13.3.2. Advertising
- 13.3.3. Analytics
- 13.3.4. API Management
- 13.3.5. Application Development
- 13.3.6. Audio
- 13.3.7. Augmented Reality
- 13.3.8. Auto
- 13.3.9. Automation
- 13.3.10. Backend
- 13.3.11. Unstructured Data
- 13.3.12. Business
- 13.3.13. Cameras
- 13.3.14. Classification
- 13.3.15. Cloud
- 13.3.16. Data
- 13.3.17. Data-as-a-Service
- 13.3.18. Demographics
- 13.3.19. eCommerce
- 13.3.20. Energy
- 13.3.21. Enterprise
- 13.3.22. Environment
- 13.3.23. Fax
- 13.3.24. Home Automation
- 13.3.25. Lists
- 13.3.26. Location
- 13.3.27. Machine-to-Machine
- 13.3.28. Management
- 13.3.29. Marketing
- 13.3.30. Marketplace
- 13.3.31. Medical
- 13.3.32. Messaging
- 13.3.33. Messaging
- 13.3.34. Monitoring
- 13.3.35. Motion
- 13.3.36. Music
- 13.3.37. NoSQL
- 13.3.38. Notifications
- 13.3.39. Optimization
- 13.3.40. Other
- 13.3.41. Pets
- 13.3.42. Robots
- 13.3.43. Science
- 13.3.44. Search
- 13.3.45. Security
- 13.3.46. Storage
- 13.3.47. Telephony
- 13.3.48. Tools
- 13.3.49. Transportation
- 13.3.50. Voice
- 13.3.51. Wearable
- 13.3.52. Weather
- 13.4. IoT API Standardization Efforts
- 13.4.1. GSMA
- 13.4.2. Open Alliance for IoT Standard
- 13.4.3. oneM2M
- 13.4.4. Others
- 13.4.5. Important Considerations