Cover Image
市場調查報告書

通訊、IoT的API:市場預測與預測

Application Programming Interfaces (API) in Telecommunications and Internet of Things (IoT): Market Outlook and Forecasts for Telecom and IoT APIs 2017 - 2022

出版商 Mind Commerce 商品編碼 547922
出版日期 內容資訊 英文 368 Pages
商品交期: 最快1-2個工作天內
價格
Back to Top
通訊、IoT的API:市場預測與預測 Application Programming Interfaces (API) in Telecommunications and Internet of Things (IoT): Market Outlook and Forecasts for Telecom and IoT APIs 2017 - 2022
出版日期: 2017年08月25日 內容資訊: 英文 368 Pages
簡介

本報告提供全球通訊API (應用編程介面) 市場相關調查分析,經營模式,價值鏈分析,業者策略,產業評估為焦點,市場預測,市場課題與機會,主要企業,解決方案,技術,使用案例等系統性資訊。

第1章 簡介

第2章 通訊API概要

  • 網路API定義
  • CSP的API有效利用的商務推動因素
  • 通訊API類別
  • 通訊API經營模式
  • 區分
  • 競爭問題
  • 使用API的應用
  • 通訊API收益的潛在性
  • 通訊API利用:各產業市場區隔
  • 通訊API價值鏈
  • API交易成本:各類型
  • API交易的數量

第3章 API聚合

  • API聚合商所扮演的角色
  • 由於API聚合商的整體營運成本
  • 聚合商的API利用:各類別

第4章 通訊API市場

  • DaaS
  • API市場廠商
  • 新的類型的應用市場

第5章 通訊API支援應用程式的使用案例

  • 通訊支援應用程式的收益化
  • 使用案例的課題

第6章 網路業者通訊API策略

  • 電信業者市場策略和定位
  • 全球網路業者API計劃
  • 電信業者、公司內部通訊API利用
  • 電信業者、OTT服務供應商
  • 電信業者、附加價值服務

第7章 API支援應用開發業者策略

第8章 通訊API供應商策略

第9章 市場分析與預測

  • 通訊API收益
  • 通訊API收益:各類別
  • 通訊API收益:各地區

第10章 未來的API市場成長的技術和市場的推動要素

  • SOA
  • SDN
  • 虛擬化
  • IoT
  • IoT WAN、通訊API

第11章 附錄

目錄

Overview:

The role of Application Programming Interfaces (API) is evolving within the Information and Communications Technology (ICT) space to support increasingly more than consumer oriented communications, applications, commerce, and digital content. This evolution extends beyond API support of B2C and B2B services for traditional ICT apps and services towards a larger role for network service providers in intelligent solutions for enterprise as well as Internet of Things (IoT) systems and networks.

There is a general flattening of the growth curve for traditional consumer centric and handset oriented services supported by Telecom APIs. Longer term, Telecom API growth will come from new networks such as those cellular and non-cellular WANs supporting IoT. Mind Commerce sees communication-enabled application revenue plateauing while IoT network-support revenue becoming a more substantial revenue component for Telecom APIs by 2025. This will begin to take shape as wireless carriers deploy 5G and leverage the associated capabilities for operational improvements within IoT networks.

This research provides an in-depth assessment of the global telecom APIs market, including business models, value chain analysis, operator strategies and a quantitative assessment of the industry from 2017 to 2022. It includes forecasts for major telecom API application support areas and segments. This research also 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 includes detailed forecasts for IoT API revenue globally, regionally, and by industry verticals for the period 2017 to 2022.

Key Findings:

  • Telecom API revenue is forecast to reach $207 billion globally by 2022
  • Unwanted Call blocking a developing area for carriers to leverage Telecom APIs
  • APIs will be a facilitator of data interchange in the emerging Data as a Service (IoTDaaS) marketplace
  • APIs will be a key infrastructure element for Identity Database (IDDB), Permissions Database, and Device Discovery Database
  • Communication service providers have not yet leveraged Telecom APIs for IoT authentication, but will do so with deployment of 5G IoT
  • Communication-enabled app revenue is plateauing while IoT network-support revenue becomes substantial revenue component by 2025

Target Audience:

  • API providers
  • IoT service providers
  • Application developers
  • Data services companies
  • Network service operators
  • ICT infrastructure suppliers
  • Wireless device manufacturers
  • Systems integration companies

Table of Contents

Telecom API Market Outlook and Forecasts 2017-2022

1. Introduction

  • 1.1. Executive Summary
  • 1.2. Topics Covered
  • 1.3. Key Findings
  • 1.4. Target Audience

2. Telecom API Overview

  • 2.1. Defining Network APIs
  • 2.2. Business Drivers for CSPs to Leverage APIs
    • 2.2.1. Need for New Revenue Sources
    • 2.2.2. B2B Services and Asymmetric Business Models
    • 2.2.3. Emerging Need for IoT Mediation
  • 2.3. Telecom API Categories
    • 2.3.1. WebRTC
    • 2.3.2. SMS and RCS-E
    • 2.3.3. Presence
    • 2.3.4. MMS
    • 2.3.5. Location
    • 2.3.6. Payments
    • 2.3.7. Voice/Speech
    • 2.3.8. Voice Control
    • 2.3.9. Multimedia Voice Control
    • 2.3.10. M2M
    • 2.3.11. SDM/Identity Management
    • 2.3.12. Subscriber Profile
    • 2.3.13. QoS
    • 2.3.14. ID/SSO
    • 2.3.15. Content Delivery
    • 2.3.16. Hosted UC
    • 2.3.17. Directory
    • 2.3.18. Number Provisioning
    • 2.3.19. USSD
    • 2.3.20. Billing of Non-Digital Goods
    • 2.3.21. Advertising
    • 2.3.22. Collaboration
    • 2.3.23. IVR/Voice Store
  • 2.4. Telecom API Business Models
    • 2.4.1. Three Business Model Types
      • 2.4.1.1. Model One
      • 2.4.1.2. Model Two
      • 2.4.1.3. Model Three
    • 2.4.2. The Asymmetric Business Model
    • 2.4.3. Exposing APIs to Developers
    • 2.4.4. Web Mash-ups
  • 2.5. Segmentation
    • 2.5.1. Users by Segment
    • 2.5.2. Workforce Management
  • 2.6. Competitive Issues
    • 2.6.1. Reduced TCO
    • 2.6.2. Open APIs
    • 2.6.3. Configurability
  • 2.7. Applications that use APIs
  • 2.8. Telecom API Revenue Potential
    • 2.8.1. Standalone API Revenue vs. API enabled Revenue
    • 2.8.2. Telecom API-enabled Mobile VAS Applications
    • 2.8.3. Carrier Focus on Telecom API's for the Enterprise
  • 2.9. Telecom API Usage by Industry Segment
  • 2.10. Telecom API Value Chain
    • 2.10.1. Telecom API Value Chain
    • 2.10.2. How the Value Chain Evolve
    • 2.10.3. API Transaction Value Split among Players
  • 2.11. API Transaction Cost by Type
  • 2.12. Volume of API Transactions

3. API Aggregation

  • 3.1. Role of API Aggregators
  • 3.2. Total Cost of Operation with API Aggregators
    • 3.2.1. Start-up Costs
    • 3.2.2. Transaction Costs
    • 3.2.3. Ongoing Maintenance/Support
    • 3.2.4. Professional Services by Intermediaries
  • 3.3. Aggregator API Usage by Category
    • 3.3.1. API Aggregator Case Study
    • 3.3.2. Aggregation: Intersection of Two Big Needs
    • 3.3.3. The Case for Other API Categories
    • 3.3.4. Moving Towards New Business Models

4. Telecom API Marketplace

  • 4.1. Data as a Service (DaaS)
    • 4.1.1. Carrier Structured and Unstructured Data
    • 4.1.2. Carrier Data Management in DaaS
    • 4.1.3. Data Federation in the DaaS Ecosystem
  • 4.2. API Market Makers
    • 4.2.1. mashape
    • 4.2.2. Mulesoft
  • 4.3. New Type of Application Marketplace
    • 4.3.1. Communications-enabled App Marketplace
    • 4.3.2. CAM Market Opportunities and Challenges

5. Telecom API Enabled App Use Cases

  • 5.1. Monetization of Communications-enabled Apps
    • 5.1.1. Direct API Revenue
    • 5.1.2. Data Monetization
    • 5.1.3. Cost Savings
    • 5.1.4. Higher Usage
    • 5.1.5. Churn Reduction
  • 5.2. Use Case Issues
    • 5.2.1. Security
    • 5.2.2. Interoperability

6. Network Operator Telecom API Strategies

  • 6.1. Carrier Market Strategy and Positioning
    • 6.1.1. API Investment Stabilization
    • 6.1.2. Carriers, APIs, and OTT
    • 6.1.3. Leveraging Subscriber Data and APIs
    • 6.1.4. Telecom API Standards
    • 6.1.5. Telecom APIs and Enterprise
  • 6.2. Global Network Operator API Programs
    • 6.2.1. AT&T Mobility
    • 6.2.2. Verizon Wireless
    • 6.2.3. Vodafone
    • 6.2.4. France Telecom
    • 6.2.5. Telefonica
  • 6.3. Carriers and Internal Telecom API Usage
    • 6.3.1. The Case for Internal Usage
    • 6.3.2. Internal Telecom API Use Cases
  • 6.4. Carriers and OTT Service Providers
    • 6.4.1. Allowing OTT Providers to Manage Applications
    • 6.4.2. Carriers Lack the Innovative Skills to Capitalize on APIs Alone
  • 6.5. Carriers and Value-added Services
    • 6.5.1. Role and Importance of VAS
    • 6.5.2. The Case for Carrier Communication-enabled VAS
    • 6.5.3. Challenges and Opportunities for Carriers in VAS

7. API Enabled Application Developer Strategies

  • 7.1. A Critical Asset to Developers
  • 7.2. Stimulating the Growth of API Releases
  • 7.3. Working alongside Carrier Programs
  • 7.4. Developer Preferences: Google vs Carriers

8. Telecom API Vendor Strategies

  • 8.1. Positioning as Enablers in the Value Chain
  • 8.2. Moving Away from a Box/Product Supplier Strategy

9. Market Analysis and Forecasts

  • 9.1. Telecom API Revenue 2017-2022
  • 9.2. Telecom API Revenue by Category 2017-2022
    • 9.2.1. Messaging API Revenues
    • 9.2.2. LBS API Revenues
    • 9.2.3. SDM API Revenues
    • 9.2.4. Payment API Revenues
    • 9.2.5. IoT API Revenues
    • 9.2.6. Other API Revenues
  • 9.3. Telecom API Revenue by Region 2017-2022
    • 9.3.1. Asia Pacific
    • 9.3.2. Eastern Europe
    • 9.3.3. Latin & Central America
    • 9.3.4. Middle East & Africa
    • 9.3.5. North America
    • 9.3.6. Western Europe

10. Technology and Market Drivers for Future API Market Growth

  • 10.1. Service Oriented Architecture
  • 10.2. Software Defined Networks
  • 10.3. Virtualization
    • 10.3.1. Network Function Virtualization
    • 10.3.2. Virtualization beyond Network Functions
  • 10.4. Internet of Things
    • 10.4.1. IoT Definition
    • 10.4.2. IoT Technologies
    • 10.4.3. IoT Applications
    • 10.4.4. IoT Solutions
    • 10.4.5. IoT, DaaS, and APIs
  • 10.5. IoT WANs and Telecom APIs
    • 10.5.1. Cellular IoT WAN
    • 10.5.2. Non-Cellular IoT WAN
    • 10.5.1. Cellular vs. Non-Cellular IoT WAN Telecom API Needs
    • 10.5.2. Telecom APIs for IoT a $20B Opportunity by 2025

11. Appendix

  • 11.1. Telecom API Definitions
  • 11.2. More on Telecom APIs and DaaS
    • 11.2.1. Tiered Data Focus
    • 11.2.2. Value-based Pricing
    • 11.2.3. Open Development Environment
    • 11.2.4. Specific Strategies
      • 11.2.4.1. Service Ecosystem and Platforms
      • 11.2.4.2. Bringing to Together Multiple Sources for Mash-ups
      • 11.2.4.3. Developing Value-added Services as Proof Points
      • 11.2.4.4. Open Access to all Entities including Competitors
      • 11.2.4.5. Prepare for Big Opportunities with the Internet of Things (IoT)
  • 11.3. Monetizing IoT APIs
    • 11.3.1. IoT API Business Models
    • 11.3.2. Peer Support of Platforms, Devices, and Gateways
    • 11.3.3. Supporting the API Developer Community
    • 11.3.4. Data and Database Transactions

Figures

  • Figure 1: Wireless Carrier Assets
  • Figure 2: Telecom API: Standalone vs. Finished Services
  • Figure 3: RCS and Telecom API Integration
  • Figure 4: RCS Revenue Forecast
  • Figure 5: Business vs. Consumer Telecom API Focus
  • Figure 6: Enterprise Dashboard
  • Figure 7: Enterprise Dashboard App Example
  • Figure 8: Telecom API Value Chain
  • Figure 9: API Transaction Value by Type
  • Figure 10: API Transaction Costs
  • Figure 11: Volume of API Transactions for a Tier 1 Carrier 2017-2022
  • Figure 12: Cloud Services and APIs
  • Figure 13: GSMA OneAPI: Benefits to Stakeholders
  • Figure 14: AT&T Wireless API Catalog
  • Figure 15: Verizon Wireless API Program
  • Figure 16: France Telecom (Orange) APIs
  • Figure 17: Telefonica APIs
  • Figure 18: Carrier Internal Use of Telecom APIs
  • Figure 19: Telecom API Revenue 2017-2022
  • Figure 20: Telecom API Revenue by Category 2017-2022
  • Figure 21: Messaging APIs Revenue 2017-2022
  • Figure 22: LBS APIs Revenue 2017-2022
  • Figure 23: SDM APIs Revenue 2017-2022
  • Figure 24: Payment APIs Revenue 2017-2022
  • Figure 25: IoT API Revenue 2017-2022
  • Figure 26: API Revenue for Other Categories 2017-2022
  • Figure 27: Telecom API Revenue by Region 2017-2022
  • Figure 28: Telecom API Revenue Asia Pacific 2017-2022
  • Figure 29: Telecom API Revenue Eastern Europe 2017-2022
  • Figure 30: Telecom API Revenue Latin & Central America 2017-2022
  • Figure 31: Telecom API Revenue Middle East and Africa 2017-2022
  • Figure 32: Telecom API Revenue North America 2017-2022
  • Figure 33: Telecom API Revenue Western Europe 2017-2022
  • Figure 34: Services Oriented Architecture
  • Figure 35: Growth of Connected Devices
  • Figure 36: IoT and Future Telecom API Topology
  • Figure 37: 3GPP IoT Proposals for LTE, Narrowband and 5G Network
  • Figure 38: LoRaWAN Network Architecture
  • Figure 39: Cellular vs. Non-Cellular IoT WAN Comparison
  • Figure 40: Different Data Types and Functions in DaaS
  • Figure 41: Ecosystem and Platform Model
  • Figure 42: Telecom API and Internet of Things Mediation
  • Figure 43: DaaS and IoT Mediation

Internet of Things API Marketplace: IoT API Use Cases, Solutions, Market Outlook and Forecasts 2017-2022

1. Executive Summary

  • 1.1. Importance of IoT APIs
  • 1.2. Market Outlook in Brief

2. API Management

  • 3.1. API Management Platform Components
    • 3.1.1. API Gateway
    • 3.1.2. API Developer Portal
    • 3.1.3. API Analytics
    • 3.1.4. API Monetization
  • 3.2. API Management Considerations
    • 3.2.1. Core Capabilities
    • 3.2.2. Quality of Service Attributes
    • 3.2.3. Vendor Assessment
    • 3.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-Lucent
  • 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
  • 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 (IoTDaaS)
    • 4.2.1. Data as a Service (DaaS)
    • 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

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.2.1.1. IoT Data Ownership
      • 5.2.1.2. IoT Data Care of Custody
      • 5.2.1.3. IoT APIs support Unstructured Data Challenges
  • 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 2017-2022

  • 6.1. Global IoT API Revenue 2017-2022
    • 6.1.1. IoT API Revenue
    • 6.1.2. IoT API Revenue by Types of IoT APIs
    • 6.1.3. IoT API Revenue by Application Sectors
    • 6.1.4. IoT API Revenue by API Category
    • 6.1.5. IoT API Revenue by Industry Vertical
      • 6.1.5.1. Automotive Services IoT API Revenue
      • 6.1.5.2. Smart City Services IoT API Revenue
      • 6.1.5.3. Healthcare Services IoT API Revenue
      • 6.1.5.4. Industrial Services IoT API Revenue
      • 6.1.5.5. Consumer Services IoT API Revenue
      • 6.1.5.6. Military and Aerospace Services IoT API Revenue
  • 6.2. Regional IoT API Revenue 2017-2022
    • 6.2.1. IoT API Revenue in Region
    • 6.2.2. North America Revenue: IoT API Type, App, Category, Industry Vertical, and Country
    • 6.2.3. APAC Revenue: IoT API Type, App, Category, Industry Vertical, and Country
    • 6.2.4. Europe Revenue: IoT API Type, App, Category, Industry Vertical, and Country
    • 6.2.5. Latin America Revenue: IoT API Type, App, Category, Industry Vertical, and Country
    • 6.2.6. MEA Revenue Forecast: IoT API Type, App, Category, Industry Vertical, and Country

7. Conclusions and Recommendations

8. Appendix

  • 8.1. IoT Protocols and Standards
    • 8.1.1. Infrastructure
      • 8.1.1.1. IPv6
      • 8.1.1.2. 6LoWPAN
      • 8.1.1.3. 6TiSCH
      • 8.1.1.4. 6Lo
      • 8.1.1.5. IPv6 over G.9959
      • 8.1.1.6. IPv6 over Bluetooth Low Energy
      • 8.1.1.7. UDP
      • 8.1.1.8. QUIC
      • 8.1.1.9. Aeron
      • 8.1.1.10. uIP (Micro-IP)
      • 8.1.1.11. DTLS
    • 6.1.1. RPL
      • 8.1.1.12. NanoIP
      • 8.1.1.13. Content-Centric Networking
      • 8.1.1.14. TSMP
    • 8.1.2. Discovery
      • 8.1.2.1. mDNS
      • 8.1.2.2. HyperCat
      • 8.1.2.3. UPnP
    • 8.1.3. Data Protocols
      • 8.1.3.1. MQTT
      • 8.1.3.2. MQTT-SN
      • 8.1.3.3. CoAP
      • 8.1.3.4. SMCP 117
      • 8.1.3.5. STOMP
      • 8.1.3.6. XMPP
      • 8.1.3.7. Mihini/M3DA
      • 8.1.3.8. AMQP
      • 8.1.3.9. DDS
      • 8.1.3.10. JMS
      • 8.1.3.11. LLAP
      • 8.1.3.12. LWM2M
      • 8.1.3.13. Reactive Streams
      • 8.1.3.14. SSI
      • 8.1.3.15. REST
      • 8.1.3.16. HTTP/2
      • 8.1.3.17. SOAP
      • 8.1.3.18. JSON
      • 8.1.3.19. WebHooks
      • 8.1.3.20. Jelastic
      • 8.1.3.21. MongoDB
      • 8.1.3.22. Websocket
      • 8.1.3.23. OPC
    • 8.1.4. Communication / Transport Layer
      • 8.1.4.1. Ethernet
      • 8.1.4.2. DigiMesh
      • 8.1.4.3. ISA100.11a
      • 8.1.4.4. IEEE 802.15.4
      • 8.1.4.5. WirelessHART
      • 8.1.4.6. NFC
      • 8.1.4.7. ANT
      • 8.1.4.8. Bluetooth
      • 8.1.4.9. Bluetooth Low Energy
      • 8.1.4.10. Eddystone
      • 8.1.4.11. ZigBee
      • 8.1.4.12. Zigbee Smart Energy
      • 8.1.4.13. DASH7
      • 8.1.4.14. Z-Wave
      • 8.1.4.15. HomePlug
      • 8.1.4.16. G.9959
      • 8.1.4.17. LTE-A
      • 8.1.4.18. EnOcean
      • 8.1.4.19. WiFi
      • 8.1.4.20. IEEE 802.11 AH
      • 8.1.4.21. WiMAX
      • 8.1.4.22. Non-Cellular LPWAN
      • 8.1.4.23. NB-IoT
    • 6.1.2. LTE-MTC
      • 8.1.4.24. EC-GSM-IoT
      • 8.1.4.25. DECT/ULE
      • 8.1.4.26. RPMA
    • 8.1.5. Semantic
      • 8.1.5.1. IOTDB
      • 8.1.5.2. SensorML
      • 8.1.5.3. Semantic Sensor Net Ontology-W3C
      • 8.1.5.4. Wolfram Language-Connected Devices
      • 8.1.5.5. RAML
      • 8.1.5.6. SENML
      • 8.1.5.7. LsDL
    • 8.1.6. Multi-layer Frameworks
    • 6.1.3. Alljoyn
      • 8.1.6.1. IoTivity
      • 8.1.6.2. IEEE P2413
      • 8.1.6.3. Thread
      • 8.1.6.4. IPSO Application Framework
      • 8.1.6.5. Weave
      • 8.1.6.6. OMA LightweightM2M v1.0
      • 8.1.6.7. Telehash
    • 8.1.7. Security
      • 8.1.7.1. Open Trust Protocol
      • 8.1.7.2. X.509
      • 8.1.7.3. MAC 802.15.4
      • 8.1.7.4. RPL
      • 8.1.7.5. Application Layer
    • 8.1.8. Vertical Specific Standards
      • 8.1.8.1. IEEE 1451
      • 8.1.8.2. IEEE 1888.3-2013
      • 8.1.8.3. IEEE 1905.1-2013
      • 8.1.8.4. IEEE 802.16p-2012
      • 8.1.8.5. IEEE P1828
      • 8.1.8.6. IEEE P1856
    • 8.1.9. IoT Management
      • 8.1.9.1. IEEE 1905.1
      • 8.1.9.2. Smart Transducer Interface
  • 8.2. IoT API Solutions
    • 8.2.1. AT&T M2X Keys API
    • 8.2.2. Interpair API
    • 8.2.3. Kaa Admin API
    • 8.2.4. Meshblu API
    • 8.2.5. Particle API
    • 8.2.6. SenseIoT API
    • 8.2.7. Weaver API
    • 8.2.8. Sensorberg API
    • 8.2.9. IOStash IoT PaaS API
    • 8.2.10. Mnubo API
    • 8.2.11. DeviceHub API
    • 8.2.12. Predix Time Series API
    • 8.2.13. Wia API
    • 8.2.14. Meeti API
    • 8.2.15. Omega Ricochet API
    • 8.2.16. Paraimpu API
    • 8.2.17. Temboo API
    • 8.2.18. Netbeast API
    • 8.2.19. Google Weave API
    • 8.2.20. URX App Search API
    • 8.2.21. Amazon Alexa Voice Service API
    • 8.2.22. Bt.tn API
    • 8.2.23. thingk.me API
    • 8.2.24. Mojio API
    • 8.2.25. PSA Group Connected Car API
    • 8.2.26. Muzzley API
    • 8.2.27. Amazon Alexa Smart Home Skills API
    • 8.2.28. Telematic REST API
    • 8.2.29. Beebotte API
    • 8.2.30. scriptr.io API
    • 8.2.31. The Beacon Registry API
    • 8.2.32. Predix Traffic Planning API
    • 8.2.33. theThings.IO REST API
    • 8.2.34. littleBits Cloud API
    • 8.2.35. Konekt API
    • 8.2.36. CloudRail API
    • 8.2.37. Predix Asset Data API
    • 8.2.38. ClearBlade API
    • 8.2.39. Samsung ARTIK Cloud API
    • 8.2.40. Beagle Sense API
    • 8.2.41. CubeSensors API
    • 8.2.42. GardenKit API
    • 8.2.43. Thinking Things API
    • 8.2.44. Arrow Intelligent Services API
    • 8.2.45. Pinoccio API
    • 8.2.46. VIMOC Technologies API
    • 8.2.47. Scio API
    • 8.2.48. Nest API
    • 8.2.49. Neura API
    • 8.2.50. Space Bunny API
    • 8.2.51. Netatmo API
    • 8.2.52. Angus.ai API
    • 8.2.53. Sense Tecnic WoTkit API
    • 8.2.54. OGC SensorThings API
    • 8.2.55. OpenSensors API
    • 8.2.56. Brivo Labs SAM API
    • 8.2.57. Carvoyant API
    • 8.2.58. Illiri API
    • 8.2.59. ThingPark API
  • 8.3. IoT APIs in Industry Verticals and Functional Areas
    • 8.3.1. 3D
    • 6.1.4. Body Labs BodyKit Instant API
    • 8.3.2. Advertising
      • 8.3.2.1. Roq.ad Cross-Device User Identification API
    • 8.3.3. Analytics
      • 8.3.3.1. MoBagel API
    • 8.3.4. API Management
      • 8.3.4.1. APIBond API
    • 8.3.5. Application Development
      • 8.3.5.1. Zatar API
      • 8.3.5.2. Telepat API
      • 8.3.5.3. Relayr API
      • 8.3.5.4. AT&T M2X Distribution API
      • 8.3.5.5. AT&T M2X MQTT API
    • 8.3.6. Audio
      • 8.3.6.1. W3C Web MIDI API
    • 8.3.7. Augmented Reality
      • 8.3.7.1. Thalmic Myo API
    • 8.3.8. Auto
      • 8.3.8.1. Caruma API
      • 8.3.8.2. Automile API
      • 8.3.8.3. Autodata Motorcycle API
      • 8.3.8.4. Dash Chassis API
      • 8.3.8.5. Unofficial Tesla Model S API
      • 8.3.8.6. Dash Mobile API
      • 8.3.8.7. Vinli API
    • 8.3.9. Automation
      • 8.3.9.1. SNAP PAC REST API
      • 8.3.9.2. IJENKO IoE2 IoT API
      • 8.3.9.3. SmartThings API
      • 8.3.9.4. Ubidots API
    • 8.3.10. Backend
      • 8.3.10.1. Kuzzle API
      • 8.3.10.2. Sidecar Event API
      • 8.3.10.3. Xively API
      • 8.3.10.4. THIL API
    • 8.3.11. Unstructured Data
      • 8.3.11.1. Orange Datavenue API
    • 8.3.12. Business
      • 8.3.12.1. xMatters API
    • 8.3.13. Cameras
      • 8.3.13.1. Google Open Spherical Camera API
    • 8.3.14. Classification
      • 8.3.14.1. MyTagList API
    • 8.3.15. Cloud
      • 8.3.15.1. MODE API
      • 8.3.15.2. SIGFOX API
    • 8.3.16. Data
      • 8.3.16.1. Chain API
      • 8.3.16.2. HPE Haven OnDem and Retrieve Config API
      • 8.3.16.3. Sierra Wireless AirVantage API
    • 8.3.17. Data-as-a-Service
      • 8.3.17.1. Fencer API
      • 8.3.17.2. myCloudData API
    • 8.3.18. Demographics
      • 8.3.18.1. Cara API
    • 8.3.19. eCommerce
      • 8.3.19.1. Estimote API
    • 8.3.20. Energy
      • 8.3.20.1. Know Watt API
    • 8.3.21. Enterprise
      • 8.3.21.1. GroveStreams API
      • 8.3.21.2. Scout API
      • 8.3.21.3. Smart Citizen API
    • 8.3.22. Environment
      • 8.3.22.1. Safecast API
    • 8.3.23. Fax
      • 8.3.23.1. Telecoms Cloud API
    • 8.3.24. Home Automation
      • 8.3.24.1. MicroBees API
      • 8.3.24.2. Lelylan API
      • 8.3.24.3. Myfox API
      • 8.3.24.4. Sensorist API
      • 8.3.24.5. Dog Gateway API
      • 8.3.24.6. Insteon API
      • 8.3.24.7. Istabai API
      • 8.3.24.8. Loggamera Heatpump API
      • 8.3.24.9. Pimatic REST API
      • 8.3.24.10. Wink App API
      • 8.3.24.11. Indigo Domotics API
      • 8.3.24.12. Apple HomeKit API
      • 8.3.24.13. Lockitron API
      • 8.3.24.14. Okidokeys API
    • 8.3.25. Lists
      • 8.3.25.1. Amazon List Skills API
    • 8.3.26. Location
      • 8.3.26.1. Garmin Communicator Plugin API
      • 8.3.26.2. LotaData API
      • 8.3.26.3. Kontakt.io API
      • 8.3.26.4. BeaconsInSpace API
    • 8.3.27. Machine-to-Machine
      • 8.3.27.1. DeviceHive API
      • 8.3.27.2. CoSwitched API
    • 8.3.28. Management
      • 8.3.28.1. InstaUnite API
    • 8.3.29. Marketing
      • 8.3.29.1. Poken API
    • 8.3.30. Marketplace
      • 8.3.30.1. OpenChannel Marketplace API
    • 8.3.31. Medical
      • 8.3.31.1. Withings API
    • 8.3.32. Messaging
      • 8.3.32.1. UnificationEngine API
    • 8.3.33. Messaging
      • 8.3.33.1. Matrix API
    • 8.3.34. Monitoring
      • 8.3.34.1. Pulseway REST API
      • 8.3.34.2. energyhive API
    • 8.3.35. Motion
      • 8.3.35.1. Motion Shadow API
      • 8.3.35.2. Sense360 API
    • 8.3.36. Music
    • 6.1.5. ickStream API
      • 8.3.36.1. Livio Connect API
    • 6.1.6. Sonos Music API
    • 8.3.37. NoSQL
      • 8.3.37.1. Couchbase API
    • 8.3.38. Notifications
      • 8.3.38.1. Mojio Push API
    • 8.3.39. Optimization
      • 8.3.39.1. Minme API
    • 8.3.40. Other
      • 8.3.40.1. Pebble API
      • 8.3.40.2. yetu API
      • 8.3.40.3. TalkBack API
      • 8.3.40.4. BITalino API
      • 8.3.40.5. electric imp API
      • 8.3.40.6. ThingSpeak API
      • 8.3.40.7. Pachube API
    • 8.3.41. Pets
      • 8.3.41.1. FitBark API
    • 8.3.42. Robots
      • 8.3.42.1. NAOqi Sensors API
    • 8.3.43. Science
      • 8.3.43.1. ThinkEco API
    • 8.3.44. Search
      • 8.3.44.1. Reposify API
      • 8.3.44.2. Shodan API
    • 8.3.45. Security
      • 8.3.45.1. ncryptify API
      • 8.3.45.2. SecureDB accounts API
      • 8.3.45.3. Miracl API
      • 8.3.45.4. Codeproof MDM API
      • 8.3.45.5. Nymi API
    • 8.3.46. Storage
      • 8.3.46.1. Verizon Personal Cloud Storage API
    • 8.3.47. Telephony
      • 8.3.47.1. DeviceIdentifier API
      • 8.3.47.2. Tweakker API
      • 8.3.47.3. PushBug API
    • 8.3.48. Tools
      • 8.3.48.1. Craft.ai API
      • 8.3.48.2. Solutecia API
      • 8.3.48.3. METAQRCODE API
      • 8.3.48.4. Instacount API
      • 8.3.48.5. ecobee API
      • 8.3.48.6. ioBridge API
      • 8.3.48.7. Spark Devices API
      • 8.3.48.8. Miri Device Description API
      • 8.3.48.9. SwiftKey API
      • 8.3.48.10. Arrayent API
      • 8.3.48.11. W3C Generic Sensor API
    • 8.3.49. Transportation
      • 8.3.49.1. PlugShare Station API
      • 8.3.49.2. CarmaLink GPS API
    • 8.3.50. Voice
      • 8.3.50.1. Houndify API
    • 8.3.51. Wearable
      • 8.3.51.1. Myle API
      • 8.3.51.2. Garmin Connect API
      • 8.3.51.3. Misfit API
      • 8.3.51.4. Sony Lifelog API
    • 8.3.52. Weather
      • 8.3.52.1. PressureNet.io API
      • 8.3.52.2. Planet OS API
      • 8.3.52.3. BloomSky API
  • 8.4. IoT API Standardization Efforts
    • 8.4.1. GSMA
    • 8.4.2. Open alliance for IoT Standard
    • 8.4.3. oneM2M
    • 8.4.4. Others
    • 8.4.5. Important Considerations

Figures

  • Figure 1: The IoT Stack
  • Figure 2: Distributed Computing in IoT
  • Figure 3: Artificial Intelligence in IoT Edge Computing
  • Figure 4: APIs Enable Data Access and Exchange
  • Figure 5: IoT Data Exchange Marketplace
  • Figure 6: IoT Platform Functionality
  • Figure 7: IoT Device Management Platforms
  • Figure 8: Global IoT Data as a Service (IoTDaaS) Revenue
  • Figure 9: IoTDaaS Topology
  • Figure 10: IoTDaaS Data Flow
  • Figure 11: Data as a Service Functions
  • Figure 12: Mediation between Cloud and Telephony
  • Figure 13: Mediation of Location Information
  • Figure 14: Mediation between Telecom and Enterprise
  • Figure 15: Leveraging APIs for IoT Mediation
  • Figure 16: IoT APIs and Mediation with Smart Grid
  • Figure 17: IoT API support of Platform to Platform
  • Figure 18: IoT API support of Platform to Device
  • Figure 20: Phase One: Limited IoT Data Sharing without Formalized Mediation
  • Figure 21: Phase Two: IoT Data Sharing between Limited Industries
  • Figure 22: Phase Three: Broadly shared IoT Data across Industries and between
  • Figure 23: Direct and Indirect IoT API Monetization
  • Figure 24: APIs support Physical to Cyber World Communications
  • Figure 25: IoT API supports Data Care of Custody
  • Figure 26: IoT API supports BDaaS/IoTDaaS
  • Figure 27: Need for Authority Data and Mediation in IoT
  • Figure 28: IoT API support of Identity Management
  • Figure 29: IoT API support of Permission Mediation
  • Figure 30: IoT APIs facilitates Permissions Hierarchy
  • Figure 31: IoT APIs facilitate Device Discovery
  • Figure 32: Global IoT API Revenue 2017-2022

Tables

  • Table 1: Global IoT API Revenue by Types of APIs 2017-2022
  • Table 2: Global IoT API Revenue by Application Sector 2017-2022
  • Table 3: Global IoT API Revenue by API Category 2017-2022
  • Table 4: Global IoT API Revenue by Industry Vertical 2017-2022
  • Table 5: Global IoT API Revenue by Automotive Services 2017-2022
  • Table 6: Global IoT API Revenue by Smart City Services 2017-2022
  • Table 7: Global IoT API Revenue by Healthcare Services 2017-2022
  • Table 8: Global IoT API Revenue by Industrial Services 2017-2022
  • Table 9: Global IoT API Revenue by Consumer Services 2017-2022
  • Table 10: Global IoT API Revenue by Military & Aerospace Services 2017-2022
  • Table 11: IoT API Revenue in Region 2017-2022
  • Table 12: North America IoT API Revenue by Types of APIs 2017-2022
  • Table 13: North America IoT API Revenue by Application Sector 2017-2022
  • Table 14: North America IoT API Revenue by API Category 2017-2022
  • Table 15: North America IoT API Revenue by Industry Vertical 2017-2022
  • Table 16: North America IoT API Revenue by Automotive Services 2017-2022
  • Table 17: North America IoT API Revenue by Smart City Services 2017-2022
  • Table 18: North America IoT API Revenue by Healthcare Services 2017-2022
  • Table 19: North America IoT API Revenue by Industrial Services 2017-2022
  • Table 20: North America IoT API Revenue by Consumer Services 2017-2022
  • Table 21: North America IoT API Revenue by Military & Aerospace Services 2017-2022
  • Table 22: North America IoT API Revenue by Country 2017-2022
  • Table 23: APAC IoT API Revenue by Types of APIs 2017-2022
  • Table 24: APAC IoT API Revenue by Application Sector 2017-2022
  • Table 25: APAC IoT API Revenue by API Category 2017-2022
  • Table 26: APAC IoT API Revenue by Industry Vertical 2017-2022
  • Table 27: APAC IoT API Revenue by Automotive Services 2017-2022
  • Table 28: APAC IoT API Revenue by Smart City Services 2017-2022
  • Table 29: APAC IoT API Revenue by Healthcare Services 2017-2022
  • Table 30: APAC IoT API Revenue by Industrial Services 2017-2022
  • Table 31: APAC IoT API Revenue by Consumer Services 2017-2022
  • Table 32: APAC IoT API Revenue by Military & Aerospace Services 2017-2022
  • Table 33: APAC IoT API Revenue by Country 2017-2022
  • Table 34: Europe IoT API Revenue by Types of APIs 2017-2022
  • Table 35: Europe IoT API Revenue by Application Sector 2017-2022
  • Table 36: Europe IoT API Revenue by API Category 2017-2022
  • Table 37: Europe IoT API Revenue by Industry Vertical 2017-2022
  • Table 38: Europe IoT API Revenue by Automotive Services 2017-2022
  • Table 39: Europe IoT API Revenue by Smart City Services 2017-2022
  • Table 40: Europe IoT API Revenue by Healthcare Services 2017-2022
  • Table 41: Europe IoT API Revenue by Industrial Services 2017-2022
  • Table 42: Europe IoT API Revenue by Consumer Services 2017-2022
  • Table 43: Europe IoT API Revenue by Military & Aerospace Services 2017-2022
  • Table 44: Europe IoT API Revenue by Country 2017-2022
  • Table 45: Latin America IoT API Revenue by Types of APIs 2017-2022
  • Table 46: Latin America IoT API Revenue by Application Sector 2017-2022
  • Table 47: Latin America IoT API Revenue by API Category 2017-2022
  • Table 48: Latin America IoT API Revenue by Industry Vertical 2017-2022
  • Table 49: Latin America IoT API Revenue by Automotive Services 2017-2022
  • Table 50: Latin America IoT API Revenue by Smart City Services 2017-2022
  • Table 51: Latin America IoT API Revenue by Healthcare Services 2017-2022
  • Table 52: Latin America IoT API Revenue by Industrial Services 2017-2022
  • Table 53: Latin America IoT API Revenue by Consumer Services 2017-2022
  • Table 54: Latin America IoT API Revenue by Military & Aerospace Services 2017-2022
  • Table 55: Latin America IoT API Revenue by Country 2017-2022
  • Table 56: MEA IoT API Revenue by Types of APIs 2017-2022
  • Table 57: MEA IoT API Revenue by Application Sector 2017-2022
  • Table 58: MEA IoT API Revenue by API Category 2017-2022
  • Table 59: MEA IoT API Revenue by Industry Vertical 2017-2022
  • Table 60: MEA IoT API Revenue by Automotive Services 2017-2022
  • Table 61: MEA IoT API Revenue by Smart City Services 2017-2022
  • Table 62: MEA IoT API Revenue by Healthcare Services 2017-2022
  • Table 63: MEA IoT API Revenue by Industrial Services 2017-2022
  • Table 64: MEA IoT API Revenue by Consumer Services 2017-2022
  • Table 65: MEA IoT API Revenue by Military & Aerospace Services 2017-2022
  • Table 66: MEA IoT API Revenue by Country 2017-2022
Back to Top