ЕСОЗ - публічна документація
Update division
Purpose
This method must be used to update existing division in the system.
Note that different legal entity types can register specific division types and address types accordingly More details can be found here
Specification
Link | Посилання на Apiary або Swagger | |
Resource | /api/divisions/{{id}} | Посилання на ресурс, наприклад: /api/persons/create |
Scope | division:write | Scope для доступу |
Components | Divisions | Зазначається перелік бізнес компонентів, які використовують цей метод, наприклад: ePrescription |
Microservices | il/api | Перелік мікросервісів, які використовує метод API, наприклад: Auth, ABAC |
Protocol type | REST | Тип протоколу, який використовується запитом, наприклад: SOAP | REST |
Request type | PATCH | Тип запиту API, наприклад: GET, POST, PATCH… |
Sync/Async | Sync | Метод є синхронним чи асинхронним? |
Public/Private/Internal | Public | Потрібно зазначити тип методу за ступенем доступності |
Logic
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
Input parameters
Input parameter | Values | Type | Description | Example |
---|---|---|---|---|
id |
| String | Required | d290f1ee-6c54-4b01-90e6-d701748f0851 |
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 |
Dictionaries
Dictionary ADDRESS_TYPE
Dictionary PHONE_TYPE
Dictionary SETTLEMENT_TYPE
Dictionary STREET_TYPE
Dictionary DIVISION_TYPE
Dictionary COUNTRY
Request structure
Example:
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")
Headers
Content-Type:application/json
Authorization:Bearer {{access_token}}
API-key:{{secret}}
Request data validation
Validate location
Location is required for divisions related to legal entity with type PHARMACY
Check that location exists in request for legal entity with type PHARMACY
In case of error - generate 422 response
Validate addresses
Check that addresses.type exists in dictionaries.
In case error generate 422 "value is not allowed in enum"
Check that addresses.area exists in Uaddresses.areas
in case error generate 422 "invalid area value"
Check that addresses.settlement exists in Uaddresses.settlements
in case error generate 422 "invalid settlement value"
Check that addresses.settlement_type exists in dictionaries.
in case error generate 422 "value is not allowed in enum"
Check that addresses.settlement_id exists in Uaddresses.settlements
in case error generate 422 "settlement with id = <id> does not exist"
Check that addresses.street_type exists in dictionaries.
In case error generate 422 "value is not allowed in enum"
Check that addresses.zip in
"^[0-9]{5}$"
format.In case error generate 422 "string does not match pattern \"^[0-9]{5}$\""
Check mapping legal_entity_type, division_type and address_type and its obligation. See validation rules here: Validation rules on Divisions
in case error generate 422 response
Validate phone
Check that phone type exists in dictionaries. PHONE_TYPE required (MOBILE,LAND_LINE)
in case error generate 422 response
Check phone number is valid according to "^\\+38[0-9]{10}$"
in case error generate 422 response
Validate email
Check that email is valid according to "~r/^[\\w!#$%&'*+\\/=?`{|}~^-]+(?:\\.[\\w!#$%&'*+\\/=?`{|}~^-]+)*@(?:[A-Z0-9-]+\\.)+[A-Z]{2,6}$/i"
in case error generate 422 response
Validate type
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
Response structure
Example:
HTTP status codes
HTTP status code | Message | What caused the error |
---|---|---|
200 | Response |
|
401 |
| Authorization failed |
403 |
| Access denied |
422 |
| Validation failed |
ЕСОЗ - публічна документація