Info |
---|
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
Table of Contents |
---|
Properties of a REST API method document
Page Properties | ||
---|---|---|
| ||
Document type | Метод REST API | |
Document title | [Document status] REST API [Назва методу] [ID методу] | |
Guideline ID | GUI-0011 | |
Author | @ | |
Document version | 1 | |
Document status | DRAFT | |
Date of creation | ХХ.ХХ.ХХХХ (дата фінальної версії документа – RC або PROD) | |
Date of update | ХХ.ХХ.ХХХХ (дата зміни версії) | |
Method API ID | API-005-006-001-0088 | |
Microservices (namespace) | IL | |
Component | Divisions | |
Component ID | COM-005-006 | |
Link на API-специфікацію | ||
Resource | {{host}}/api/divisions/{{id}} | Scope | Protocol type |
Info | ||
REST API method / Метод REST API (настанова) (remove the link block before publishing the document) |
Table of Contents |
---|
Properties of a REST API method document
Page Properties | ||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||
|
...
Only authenticated and authorized user of this legal entity with appropriate scope can update division.
Division can be updated for RESIDENCE, REGISTRATION addresses types.
Division can be updated for legal entities in ACTIVE or SUSPENDED statuses.
Editable information on division:
name
addresses
phones
email
add the gps-coordinates attributed to the division (location)
working hours
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 parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | id |
| String | Required | d290f1ee-6c54-4b01-90e6-d701748f0851 |
2 |
...
Parameter | Source |
---|---|
action | `PATCH` |
id |
|
external_id | $.external_id |
name | $.name |
type | $.type |
addresses | $.addresses |
phones | $.type, $.number |
inserted_at | :timestamp |
updated_at | :timestamp |
legal_entity_id | take from token |
location | $.latitude, $.longitude |
status | ACTIVE |
is_active | true |
working_hours | $.working_hours |
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
|
Headers
...
Key
...
Value
...
Mandatory
...
Description
...
Example
...
Content-Type
...
application/json
...
M
...
Тип контенту
...
Content-Type:application/json
...
Authorization
...
Bearer {{access_token}}
...
M
...
Перевірка користувача
...
Authorization:Bearer {{access_token}}
...
API-key
...
{{secret}}
...
API-key:{{secret}}
...
|
Headers
Key | Value | Mandatory | Description | Example | |
---|---|---|---|---|---|
1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json |
2 | Authorization | Bearer {{access_token}} | 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
...
Check that type exists in dictionaries. Type required (DRUGSTORE,DRUGSTORE2,CLINIC,AMBULANT_CLINIC,FAP)
in case error generate 422 response
Check mapping of legal_entity_type and division type.
in case error generate 422 response
Processing
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API
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 | Помилка підтвердження | 5Authorization failed | |||
4 | 403 | Access denied | ||||||||
65 | 403 | Access denied. Party is not verified | ||||||||
7 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | |||||
8 | 6 | 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 | ||||
---|---|---|---|---|
|
...