Page Comparison

openapi: 3.0.1

info:
  title: Ozone Connect - Health Check APIs
  contact:
    name: Ozone Financial Technology Limited
  description: |
    This document provides the OAS3 specification for Health Check APIs for Ozone Connect.

    These APIs should be implemented by an financial institution so that Ozone
    can ensure that the institution's Ozone Connect implementation is up and running.

    #### Document Structure
 Please refer to the API Hub documentation for details of test cases that are 
 The documentation contains aavailable numberfor ofthis referencesAPI of the form `XXX-999-999`. These are references
    to test case numbers in the Ozone Connect Test Harness that financial institutions may use to test their Ozone Connect implementationsusing the Ozone Connect test suite.

    ### Changes in Version 2025.06.0

    * Added Security Requirements as Ozone Connect API design guidelines.

    * Added `default` response to all API operations as per Ozone Connect API design 
      guidelines. This prescribes an error response structure that should be used but 
      does not mandate the HTTP status code to be used, leaving this at the discretion 
      of the implementer.

    * Removed test case guidance and references from the API description as now 
      maintained on a API Hub documentation page.

  version: Version 2024.342025.06.0

servers:
  - url: https://<your-ozone-connect-server>

tags:
  - name: health-check
    description: |
      APIs that should be implemented by Financial InstituationsInstitutions to expose health check end-points 
      operations

security:
  - {}

paths:
  /hello:
    get:
      operationId: hello
      summary: check connectivity without a mutual tls check
      tags:
        - health-check
      description:
        Check connectivity without a mutual tls CheckDetails.

        This health check is used to check that the end-to-end network connectivity is working as expected. This is a simple health check that does not require mutual TLS.
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HealthCheck200Response'
        default:
          $ref: '#/components/responses/DefaultErrorResponse'

  /hello-mtls:
    get:
      operationId: helloMtls
      summary: check connectivity including mtls
      tags:
        - health-check
      description:
        Check connectivity including mutual TLS CheckDetails.

        This health check is used to check that the end-to-end network connectivity is working as expected including mutual tls.
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HealthCheck200Response'

        '401':
          description: Returned when mtls connection could not be established
          content:
            application/json:$ref: '#/components/responses/UnauthorizedResponse'
              schema:
     default:
          $ref: '#/components/schemasresponses/HealthCheck4xxResponseDefaultErrorResponse'

  /echo-cert:
    get:
      operationId: echoCert
      tags:
        - health-check
      summary: Provides information about the client cert that the server received
      description:
        This health check endpoint assists in debugging mutual tls client issues.

        The health check returns information about the client certificate and the issuer of the client certificate that the server received.

        Where mtls cannot be established, the server will return a 401 response.
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HealthCheckCertResponse'
         '401':
          $ref: '#/components/responses/UnauthorizedResponse'
        description: Returned when mtls connection could not be establisheddefault:
          $ref: '#/components/responses/DefaultErrorResponse'

components:
  responses:
    UnauthorizedResponse:
      contentdescription: Unauthorized response
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/HealthCheck4xxResponse'
    DefaultErrorResponse:
      description: Default error response
      content:
        schemaapplication/json:
          schema:
            $ref: '#/components/schemas/HealthCheck4xxResponse'

components:
  schemas:
    HealthCheck200Response:
      type: object
      description:
        Succesful response on a health check
      properties:
        connectionEstablished:
          type: boolean

        mtlsStatus:
          type: string
          enum:
            - established
            - not-established
            - not-checked

        hostName:
          type: string

      required:
        - connectionEstablished
        - mtlsStatus
        - hostName

    HealthCheck4xxResponse:
      type: object
      description:
        Response when connection could not be established
      properties:
        errorMessage:
          type: string

      required:
        - errorMessage

    HealthCheckCertResponse:
      properties:
        connectionEstablished:
          type: boolean

        mtlsStatus:
          type: string
          enum:
            - established
            - not-established

        hostName:
          type: string

        clientCertificate:
          type: object
          properties:
            subject:
              type: string

            issuer:
              type: string
          required:
            - subject
            - issuer

      required:
        - connectionEstablished
        - mtlsStatus
        - hostName
        - clientCertificate