Smile CDR v2023.05.PRE
On this page:
  • JSON Admin Endpoints
  • 33.0 JSON Admin API
  • 33.1 Audit Log Endpoint
  • 33.2 Batch Job Endpoint
  • 33.3 Bulk Import Endpoint
  • 33.4 CDA Exchange Endpoint
  • 33.5 Metrics Endpoint
  • 33.6 Module Config Endpoint
  • 33.7 OpenID Connect Clients Endpoint
  • 33.8 OpenID Connect Servers Endpoint
  • 33.9 OpenID Connect Sessions Endpoint
  • 33.10 Runtime Status Endpoint
  • 33.11 System Config Endpoint
  • 33.12 Transaction Log Endpoint
  • 33.13 User Management Endpoint
    • 33.1    Audit Log Endpoint   
       Table of Contents

    JSON Admin API

    33.0JSON Admin API

     

    Smile CDR includes an administration API based on (non-FHIR) RESTful JSON Web Services. This API uses simple JSON-based REST calls to check status information and configure the CDR.

    In a default installation of Smile CDR, this will be found on port 9000 so it will be accessible by a URL similar to http://localhost:9000/.

    This API makes use of Swagger, which is a RESTful web services description framework as well as a convenient testing tool for using these services. A screenshot of this tool is shown below.

    Swagger-UI

    33.0.1Security

     

    By default these services are secured using HTTP Basic Authentication, which means every request should include an Authorization header.

    When using Swagger-UI, you will be prompted by your browser for credentials when accessing any services where the default security is preserved.

    HTTP Basic Authentication

    If HTTP Basic Authentication is enabled, a typical GET request to the JSON Admin API will resemble the following:

    GET http://localhost:9000/runtime-status/node-statuses/complete
Authorization: Basic YWRtaW46cGFzc3dvcmQ=
Accept: application/json

    These services may also be configured to use a different security module, such as an OpenID Connect module.

    33.0.2Format

     

    Note that all dates and times in this API follow the same ISO-8601 format used by FHIR (e.g. 2017-01-01T00:00:00.0000-05:00).

    33.0.3Allowing Anonymous Access

     

    It is sometimes beneficial to allow specific types of requests to be performed without authentication. This is most commonly the case for monitoring tools. Note that this is recommended only in cases where the JSON Admin API is not accessible to the outside world (e.g. it is exposed only to a port on an internal management network). If you would like to enable anonymous access, use the following steps:

    • Enable Allow Anonymous Access on the JSON Admin API module. Enabling this setting means that requests to the JSON Admin API will receive the permissions associated with your anonymous user. By default the anonymous user has no meaningful permissions so this setting has no effect on its own.

    • Grant your anonymous user the ACCESS_ADMIN_JSON permission. This allows anonymous requests to access the endpoint, but does not grant any ability to invoke specific operations.

    • Grant your anonymous user appropriate permissions for the functions you want to enable anonymous access for. For example, if you want to enable anonymous metric access, grant the VIEW_METRICS permission. Be careful about which permissions you grant here, since anonymous access can be a significant security concern.

  • JSON Admin Endpoints
  • 33.0 JSON Admin API
  • 33.1 Audit Log Endpoint
  • 33.2 Batch Job Endpoint
  • 33.3 Bulk Import Endpoint
  • 33.4 CDA Exchange Endpoint
  • 33.5 Metrics Endpoint
  • 33.6 Module Config Endpoint
  • 33.7 OpenID Connect Clients Endpoint
  • 33.8 OpenID Connect Servers Endpoint
  • 33.9 OpenID Connect Sessions Endpoint
  • 33.10 Runtime Status Endpoint
  • 33.11 System Config Endpoint
  • 33.12 Transaction Log Endpoint
  • 33.13 User Management Endpoint
    • 33.1    Audit Log Endpoint