Info |
---|
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
...
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
Configured Public GET, POST, PATCH methods on GW
Successful response with correct authorization and appropriate scopes
401 error on invalid authorization
403 error on invalid scopes
Legal entity id is missing in request
Legal entity id is set as header by GW
Created divisions saved to DB
Mountain group calculated
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
Dictionary ADDRESS_TYPE
Dictionary PHONE_TYPE
Dictionary SETTLEMENT_TYPE
Dictionary STREET_TYPE
Dictionary DIVISION_TYPE
Dictionary COUNTRY
Input parameters
Description of input
Input parameters
Input parameter | Mandatory | Type | Description | Example | ||||||
---|---|---|---|---|---|---|---|---|---|---|
1 | composition_id | M | String ($uuid) (path) | Composition object ID | 89678f60-4cdc-4fe3-ae83-e8b3ebd35c59||||||
2 |
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
|
...
Key | Value | Mandatory | Description | Example | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json | 2 | Authorization | json | ||||
2 | Authorization | Bearer {{access_token}} | M | Перевірка користувача | Authorization:Bearer {{access_token}} | |||||||
3 | API-key | {{secret}} | API-key:{{secret}} | M | Перевірка користувача | Authorization:Bearer {{access_token}} | 3 | API-key | {{secret}} | API-key:{{secret}} |
...
Request data validation
Authorize
Verify the validity of access token
Check user scope (scope = 'division:write') in order to perform this action
in case error - generate 401 response
If BLOCK_UNVERIFIED_PARTY_USERS is true, then check party's data match following condition: verification_status != NOT_VERIFIED or (verification_status = NOT_VERIFIED and updated_at <= current_date - UNVERIFIED_PARTY_PERIOD_DAYS_ALLOWED):
in case not match - return 403 ("Access denied. Party is not verified")
Validate location
Location is required for divisions related to legal entity with type PHARMACY
...
Response structure examples
See on API-specification (посилання на сторінку з API-специфікацією)Description of the REST API response structure, example
Expand | ||
---|---|---|
| ||
|
...
Response code | HTTP Status code | Message | Internal name | Description | |||||
---|---|---|---|---|---|---|---|---|---|
1 | Базові | ||||||||
2 | 200 | Response |
| ||||||
3 | 401 | Authorization failed | |||||||
4 | 401 | Unauthorized | Помилка підтвердження | 5 | 403 | Invalid scopes | |||
65 | 403 | Access denied. Party is not verified | |||||||
7 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | ||||
86 | 422 | invalid area value | |||||||
97 | 422 | invalid settlement value | |||||||
108 | 422 | settlement with id = <id> does not exist | |||||||
119 | 422 | string does not match pattern \"^[0-9]{5}$\" | |||||||
1210 | 422 | Validation failed | |||||||
1311 | 422 | value is not allowed in enum | |||||||
1412 | Специфічні | ||||||||
15 | 422 | Only for active MPI record can be created medication request!13 |
Post-processing processes
Description of actions performed on data after processing
Technical modules where the method is used
List of pages describing technical modules where the method is used
Page Properties Report | ||||
---|---|---|---|---|
|
...