Info |
---|
Note |
Сторінка знаходиться в процесі розробки. Інформація на ній може бути застарілою. |
Info |
---|
/wiki/spaces/EN/pages/17591304241 (remove the link block before publishing the document) |
Table of Contents |
---|
Properties of a REST API method document
Page Properties | ||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||
|
Purpose
Describe the purpose of the API method, add Key points (if necessary)This method is designed to verify that provided in the declaration request phone number is valid and is in service. Final stage
Logic
Description of the working algorithm of the API method and the interaction of services with each other add Service logic (if necessary)
Configuration parameters
Description of the configuration parameters that are used when processing a request in the system
Dictionaries
Provides a list of links to dictionaries that are available in Confluence
Input
...
parameters
Input parameter | Mandatory | Type | Description | Example | |
---|---|---|---|---|---|
1 | compositionphone_idnumber | M | String ($uuid) (path)Composition object ID | Required | 89678f60-4cdc-4fe3-ae83-e8b3ebd35c59 |
2 |
Attributes
Attribute | Values | Type | Description | Example |
---|---|---|---|---|
code |
| Number |
| 3782 |
Request structure
See on API-specification (посилання на сторінку з API-специфікацією)Description of the REST API request structure, example
Expand | ||
---|---|---|
| ||
|
Headers
Key | Value | Mandatory | Description | Example | ||
---|---|---|---|---|---|---|
1 | Content-Type | application/json | M | Тип контенту | Content-Type:application/json | |
2 | Authorization | Bearer c2778f3064753ea70de870a53795f5c9M{token} | Перевірка користувача | Authorization:Bearer c2778f3064753ea70de870a53795f5c9 | 3{token} | |
3 | api-key | {secret} | Секретний ключ | api-key: {secret} |
Request data validation
Describe the process of checking the input data transmitted in the request for compliance with the given rules and restrictions set in the API
Processing
...
A list of processes related to receiving, changing or transmitting data according to the logic defined in the REST API
Response structure examples
...
To confirm the verification, you must enter the phone number and OTP (one-time code) in the system
If the code entered by the user is correct, the system will send a reply: |
---|
|
Where:
id
- request idcode_expired_at
= the time until which the code is valid in the systemActive
- code activity status in the system"TRUE" -
if verification is possible:when creating a default query,
if there were less than 4 attempts to use
if the code has not expired (up to 300 seconds after creation)
"FALSE" - if verification is impossible:
if code has been already used
if more then 3 repayment attemptes has been made
if the verification deadline has expired, including successful verification
Status
- displays the verification status
|
|
|
|
|
---|---|---|---|---|
when creating a query, by default | upon successful completion | upon unsuccessful verification (more than 3 attempts) | the code has expired коду | installed by the provider, in case the SMS cannot be delivered |
If the code entered by the user is incorrect, then:
If this is one of the first three incorrect attempts, the system will respond: |
---|
|
If this is the fourth (or more) failed attempt to enter the code, the system will respond: |
---|
|
If the correct code is entered after the expiration of the code (OTP_LIFETIME = 300 seconds) : |
---|
|
If an incorrect code is entered after the expiration of the code : |
---|
If an incorrect code is entered after the expiration of the code : |
---|
{ |
Verify code
Search active code for phone number
Check code expiration period
Compare codes
Matched
Deactivate code
Add phone number to verified_phones
Not matched
Deactivate code
Invoke Send verification code
Return error
Response structure examples
See on API-specification
Expand | ||
---|---|---|
| ||
|
HTTP status codes
Response code | HTTP Status code | Message | Internal name | Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Базові | |||||||||||||
2 | 1000 | 404 | Composition not found | COMPOSITION_NOT_FOUND_404 | Не знайдено медичний висновок | 3 | 401 | Unauthorized | Помилка підтвердження | 200 | Response | |||
3 | 403 | Error | ||||||||||||
4 | Специфічні | |||||||||||||
5 | 422 | Only for active MPI record can be created medication request!
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 | ||||
---|---|---|---|---|
|
...