Public Keys

Description

This API endpoint retrieves a collection of public keys. These public keys are used to verify the digital signatures on JWTs (JSON Web Tokens) that are sent from the conneQt Toolbar to your widget. These JWTs serve as a way to ensure the authenticity and integrity of the data being exchanged between the conneQt Toolbar and your widget, providing a secure means of communication.

HTTP Definition

Method: GET Endpoint URL: /api/v1/public-keys

Headers

This request defines no mandatory headers.

URL Parameters

The request contains no URL parameters.

Request JSON Definition

This message does not include a request payload.

GET https://int.conneqt.health/api/v1/public-keys HTTP/1.1

Response JSON Definition

HTTP/1.1 200 OK

{
    "keys": [
        {
            "kty": "RSA",
            "x5t#S256": "kv45eQHo4MKiyqhcAPG9U5uSet4_gDJsVdPDM7664_U",
            "nbf": 1659433491,
            "e": "AQAB",
            "kid": "toolbar-jwt-signing-certificate",
            "x5c": [
                "MIIDSDCCAjCgAwIBAgIEYujyEzANBgkqhkiG9w0BAQsFADBmMRcwFQYDVQQKDA5RdWlja3NpbHZhIEx0ZDEhMB8GA1UECwwYUmVzZWFyY2ggYW5kIERldmVsb3BtZW50MSgwJgYDVQQDDB9Ub29sYmFyIEpXVCBTaWduaW5nIENlcnRpZmljYXRlMB4XDTIyMDgwMjA5NDQ1MVoXDTIzMDgwMjA5NDQ1MVowZjEXMBUGA1UECgwOUXVpY2tzaWx2YSBMdGQxITAfBgNVBAsMGFJlc2VhcmNoIGFuZCBEZXZlbG9wbWVudDEoMCYGA1UEAwwfVG9vbGJhciBKV1QgU2lnbmluZyBDZXJ0aWZpY2F0ZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKFepShaECkg1Msj/gx+lmY8v66OQ1IR+BT81nLgROKqT4gR02SPp2k/wyQEPXQyLziTA0gGdLiQj8OVMMIvlMvWveS6ETDeAX0NELK1uhJy9DjuUx12/HR0ErpntGalvc00bwsHtVykHBepQTyCfZ4D084GjQdAOndY0pLSPFT7HRSK0TMgM3J5YMR/T9IEwhaMWhjVguzKCmI6A45jP+jQceht8g8mffZuqV4sqNbKANJ2wKfuSlCtinATgsTibXIFedGsE8ze2y9dVcCWbXz+w1qKNyeAoOJwjNyq3BbSNYdv2dp8qyiATivNoXR6gwrRq4YjME7XmwSon1zXPTsCAwEAATANBgkqhkiG9w0BAQsFAAOCAQEAX5O1F55D1jVWYmOISS0qCr2lw7/6BUU05vG8NmEb3PDPQovXtAe8Pbgq4q3yUD2ow0+rT5YuBSwi5grKG9dpA85cqyry2yXolhLyWrRAR7JRXxg+9D9O+ByFBA+cmmMxKD/sAIc/b6Iz7vqZJtsSWvna/TpMoPyhHlLNdmP9Hbv3IgdJGeCklLnRY072r78Jv63YwzIIrHolpvjKiskqY+jttEoNtqeqLbxxiABQVAK+SEGhHrXTYyfx4d/MTuyTwkSfO7vav8v4PmhZ1Xt/WFwOy/4aIw9QijKDaNCnB+FVJcEdwgND26CrftDru9oFfw1vbDLUJ3XlZlfDqKBuyQ=="
            ],
            "exp": 1690969491,
            "n": "oV6lKFoQKSDUyyP-DH6WZjy_ro5DUhH4FPzWcuBE4qpPiBHTZI-naT_DJAQ9dDIvOJMDSAZ0uJCPw5Uwwi-Uy9a95LoRMN4BfQ0QsrW6EnL0OO5THXb8dHQSume0ZqW9zTRvCwe1XKQcF6lBPIJ9ngPTzgaNB0A6d1jSktI8VPsdFIrRMyAzcnlgxH9P0gTCFoxaGNWC7MoKYjoDjmM_6NBx6G3yDyZ99m6pXiyo1soA0nbAp-5KUK2KcBOCxOJtcgV50awTzN7bL11VwJZtfP7DWoo3J4Cg4nCM3KrcFtI1h2_Z2nyrKIBOK82hdHqDCtGrhiMwTtebBKifXNc9Ow"
        }
    ]
}

Error Responses

If there was an issue processing your request, a HTTP error response will be returned, containing details of the issue. Common problems include:

  • One or more invalid data items were found in the request.
  • The intended recipient organisation is not one that uses our system.

The system uses the definition of an IETF Problem, as described in RFC 7807, in error responses to provide machine-readable details of why a request was rejected. The content of the Problem returned depends on the nature of the issue.

HTTP Response Code HTTP Reason Code Description
500 Internal Server Error Internal Server Error - An Internal Server Error Prevented the Request from Being Processed.

See Also