| IATA |
Enabler of an Airline Industry Open Data Ecosystem |
OpenAPI v3.0, OpenAPI Program |
Transport |
| Open Geospatial Consortium |
OGC Standards are internationally recognized specifications that let different systems exchange information seamlessly. They are organized by functional area (e.g., data discovery, organization). The functional capabilities of the Web Service Standards are now available as more modern web APIs. |
OpenAPI v3.0, OGC API - Common |
Geospatial |
| Transport Operator Mobility-as-a-service Provider (TOMP) |
The TOMP working group aims to develop and sustain an internationally governed interoperable open standard for technical communication between Transport Operators and MaaS Providers, by means of definition, improvement, alignment and dissemination. |
OpenAPI v3.0, TOMC WG API |
Transport |
| Open Banking UK |
The Open Banking Standard's Read/Write Data API Profile provides a description of the elements that are common across all the Read/Write Data APIs. |
OpenAPI v3.0, Read/Write API standard |
Banking/Finance |
| OpenEHR |
Open industry specifications, models and software for e-health |
OpenAPI v3.0, OpenAPI specifications |
Health |
| WIPO World Intellectual Property Organisation |
WIPO's API Standards include a standard for publishing an API specification but does not mention that this should be OpenAPI in particular, but encouarges OpenAPI version 3 with national IP offices and uses OpenAPI to automate their API catalog |
ST 90 API standards(https://www.wipo.int/export/sites/www/standards/en/pdf/03-90-01.pdf) |
Intellectual Property |
| DCSA - Digital Container Shipping Association |
The DCSA provides a range of API standards and documents each using OpenAPI. The standards note that Open API 3.0.x MUST be used to document APIs. |
OpenAPI v3.0.3, DCSA API Design Principles 1.1 |
Logistics |
| UK Government |
UK Government standards for people building Application Programming Interfaces (APIs) in government |
"The OpenAPI Specification is a standardised way of describing RESTful web APIs, and is recommended by the government Open Standards Board." No specific version is noted.API technical and data standards |
Government |
| Collision Industry Electronic Commerce Association (CIECA) |
CAPIS JSON Style Guide |
"CIECA Architecture Committee understands that everyone is looking forward to building OpenAPIs. Standards describe use of OpenAPIs and JSON Schema. |
{CAPIS JSON Style Guide](https://www.cieca.com/capis-guidelines) |
| papiNet is a global paper, forest products and bioproducts industry e-Business initiative, started in year 2000. |
papiNet API is a new initiative that aim to deliver a similar industry level standardization of a REST API that facilitates the flow of information among parties engaged in buying, selling, and distribution of paper, forest and bio related products. |
For this new flavour of the papiNet standard, we have decided to adopt an agile way of working, delivering the papiNet API definition iteratively based on specific use cases. |
Includes a yaml OpenAPI document describing the normative structure of a standardised API, https://github.com/papinet/papiNet-API |
| Government of The Netherlands |
Dutch Government standards for people building Application Programming Interfaces (APIs) in government |
OpenAPI Specification 3.0.x is a required standard by the Netherlands Standardisation Forum for Government APIs. |
Government |
| Open Logistics Foundation |
The Open Logistics Foundation has devoted itself to collaborative brainstorming on, as well as development and implementation of, open source solutions for logistics and supply chain management. |
TBD |
Logistics |