1 Purpose
2 Specification
3 Logic
4 Input parameters
5 Request structure
6 Authorize
7 Headers
8 Request data validation
- 8.1 Request validation
9 Processing
10 Response structure
11 Post-processing processes
12 HTTP status codes

Purpose

Only redirect uri can be updated using this method

Specification

Link	https://ehealthmisapi1.docs.apiary.io/#reference/public.-medical-service-provider-integration-layer/manage-client-configuration/update-client-connection	Посилання на Apiary або Swagger
Resource	/api/clients/{{id}}/connections/{{connection_id}}	Посилання на ресурс, наприклад: /api/persons/create
Scope	connection:write	Scope для доступу
Components	Manage client configuration	Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescription
Microservices	API paragraph not found	Перелік мікросервісів, які використовує метод API, наприклад: Auth, ABAC
Protocol type	REST	Тип протоколу, який використовується запитом, наприклад: SOAP \| REST
Request type	PATCH	Тип запиту API, наприклад: GET, POST, PATCH…
Sync/Async	Sync	Метод є синхронним чи асинхронним?
Public/Private/Internal	Public	Потрібно зазначити тип методу за ступенем доступності

Logic

Extract client_type from token
Validate specified Client ID according to context:
1. MSP, MIS, PHARMACY - receives only its own client
  1. in case of error generate 403 response ('forbidden')
Update mithril.connections for specified Connection ID and replace redirect_uri with the value from request
Hide secret from response

Input parameters

Input parameter	Values	Type	Description	Example

Input parameter	Values	Type	Description	Example
id		String	Required	1380df72-275a-11e7-93ae-92361f002671
connection_id		String	Required	e5372365-d47a-467f-81d0-f35117864352

Request structure

{
  "redirect_uri": "https://example3.com"
}

Authorize

Verify the validity of access token
1. in case of error return 401 ('Access denied')
Check user scope connection:write in order to perform this action
1. in case of error generate 403 response ('Invalid scopes')

Headers

Content-Type:application/json

Authorization:Bearer c2778f3064753ea70de870a53795f5c9

API-key:uXhEczJ56adsfh3Ri9SUkc4en

Request data validation

Request validation

Validate according JSON Schema
1. Return 422 with list of validation errors in case validation fails

Processing

API paragraph not found

Response structure

Example:

{
  "meta": {
    "code": 200,
    "url": "https://example.com/resource",
    "type": "object",
    "request_id": "6617aeec-15e2-4d6f-b9bd-53559c358f97#17810"
  },
  "data": {
    "id": "df9f70ee-4b12-4740-b0f5-bb5aea116863",
    "client_id": "c4a6d45f-2cf2-4e6d-909a-5962604ad63b",
    "consumer_id": "25c03af6-69bd-439e-b0dd-f1669b3dbbfd",
    "redirect_uri": "https://example2.com"
  }
}

Post-processing processes

API paragraph not found

HTTP status codes

HTTP status code	Message	What caused the error

HTTP status code	Message	What caused the error
200	Response
401	Access denied
403	Invalid scopes Forbidden
422		Validation failed

E-Health

Update client connection

Purpose

Specification

Logic

Input parameters

Request structure

Authorize

Headers

Request data validation

Request validation

Processing

Response structure

Post-processing processes

HTTP status codes