Update SEPA TIS Specs authored by Konrad Botor's avatar Konrad Botor
...@@ -3,22 +3,18 @@ ...@@ -3,22 +3,18 @@
Note: All endpoints will be on the same path, only `method` parameter will change Note: All endpoints will be on the same path, only `method` parameter will change
```yaml ```yaml
swagger: '2.0' openapi: 3.0.0
info: info:
description: API for TIS connection to DIS in SEPA connector project description: API for TIS connection to DIS in SEPA connector project
version: 1.0.0 version: 1.0.0
title: SEPA-TIS title: SEPA-TIS
# put the contact info for your development or API team
contact: contact:
email: kbotor@syncad.com email: kbotor@syncad.com
# tags are used for organizing operations
tags: tags:
- name: input - name: input
description: Endpoints for mesages incoming from bank description: Endpoints for mesages incoming from bank
- name: output - name: output
description: Endpoints for messages outgoing to bank description: Endpoints for messages outgoing to bank
paths: paths:
/payment-request: /payment-request:
post: post:
...@@ -27,21 +23,19 @@ paths: ...@@ -27,21 +23,19 @@ paths:
summary: Sends payment request to bank summary: Sends payment request to bank
operationId: paymentRequest operationId: paymentRequest
description: Sends payment request to bank description: Sends payment request to bank
consumes:
- application/json
produces:
- application/json
parameters:
- in: body
name: paymentRequest
description: Payment request to send
schema:
$ref: '#/definitions/PaymentRequest'
responses: responses:
200: '200':
description: ALways HTTP code 200 description: ALways HTTP code 200
schema: content:
$ref: '#/definitions/Response' application/json:
schema:
$ref: '#/components/schemas/Response'
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentRequest'
description: Payment request to send
/payment-return-request: /payment-return-request:
post: post:
tags: tags:
...@@ -49,21 +43,19 @@ paths: ...@@ -49,21 +43,19 @@ paths:
summary: Sends payment return request to bank summary: Sends payment return request to bank
operationId: paymentReturnRequest operationId: paymentReturnRequest
description: Sends payment return request to bank description: Sends payment return request to bank
consumes:
- application/json
produces:
- application/json
parameters:
- in: body
name: paymentReturnRequest
description: Payment return request to send
schema:
$ref: '#/definitions/PaymentReturnRequest'
responses: responses:
200: '200':
description: ALways HTTP code 200 description: ALways HTTP code 200
schema: content:
$ref: '#/definitions/Response' application/json:
schema:
$ref: '#/components/schemas/Response'
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentReturnRequest'
description: Payment return request to send
/payment-return: /payment-return:
post: post:
tags: tags:
...@@ -71,468 +63,769 @@ paths: ...@@ -71,468 +63,769 @@ paths:
summary: Sends payment return to bank summary: Sends payment return to bank
operationId: paymentReturn operationId: paymentReturn
description: Sends payment return to bank description: Sends payment return to bank
consumes:
- application/json
produces:
- application/json
parameters:
- in: body
name: paymentReturn
description: Payment return to send
schema:
$ref: '#/definitions/PaymentReturn'
responses: responses:
200: '200':
description: ALways HTTP code 200
content:
application/json:
schema:
$ref: '#/components/schemas/Response'
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/PaymentReturn'
description: Payment return to send
/resolution-of-investigation:
post:
tags:
- output
summary: Sends resolution of investigation to bank
operationId: resloutionOfInvestigation
description: Sends resolution of investigation to bank
responses:
'200':
description: ALways HTTP code 200
content:
application/json:
schema:
$ref: '#/components/schemas/Response'
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/ResolutionOfInvestigation'
description: Resolution of investigation to send
/next-message:
post:
tags:
- input
summary: Checks for new mesages from bank
operationId: nextMessage
description: Checks for new mesages from bank
responses:
'200':
description: ALways HTTP code 200 description: ALways HTTP code 200
schema: content:
$ref: '#/definitions/Response' application/json:
definitions: schema:
PaymentRequest: $ref: '#/components/schemas/NextMessageResponse'
type: object requestBody:
required: content:
- jsonrpc application/json:
- id schema:
- method $ref: '#/components/schemas/NextMessageRequest'
- params description: Next message request
properties: servers:
jsonrpc: - url: 'https://localhost:8080/'
type: number components:
format: double schemas:
enum: PaymentRequest:
- 1.0 type: object
- 2.0 required:
description: JSON-RPC standard version number - jsonrpc
example: 1.0 - id
id: - method
type: integer - params
description: Request ID properties:
example: 1 jsonrpc:
method: type: number
type: string format: double
enum: enum:
- ffcctrns - 1
description: Method name - 2
example: ffcctrns description: JSON-RPC standard version number
params: example: 1
type: array id:
description: Request parameters type: integer
items: description: Request ID
$ref: '#/definitions/PaymentRequestParams' example: 1
PaymentReturnRequest: method:
type: object type: string
required: enum:
- jsonrpc - ffcctrns
- id description: Method name
- method example: ffcctrns
- params params:
properties: type: array
jsonrpc: description: Request parameters
type: number items:
format: double $ref: '#/components/schemas/PaymentRequestParams'
enum: minItems: 1
- 1.0 maxItems: 1
- 2.0 PaymentReturnRequest:
description: JSON-RPC standard version number type: object
example: 1.0 required:
id: - jsonrpc
type: integer - id
description: Request ID - method
example: 1 - params
method: properties:
type: string jsonrpc:
enum: type: number
- ffpcqrst format: double
description: Method name enum:
example: ffpcqrst - 1
params: - 2
type: array description: JSON-RPC standard version number
description: Request parameters example: 1
items: id:
$ref: '#/definitions/PaymentReturnRequestParams' type: integer
PaymentReturn: description: Request ID
type: object example: 1
required: method:
- jsonrpc type: string
- id enum:
- method - ffpcqrst
- params description: Method name
properties: example: ffpcqrst
jsonrpc: params:
type: number type: array
format: double description: Request parameters
enum: items:
- 1.0 $ref: '#/components/schemas/PaymentReturnRequestParams'
- 2.0 minItems: 1
description: JSON-RPC standard version number maxItems: 1
example: 1.0 PaymentReturn:
id: type: object
type: integer required:
description: Request ID - jsonrpc
example: 1 - id
method: - method
type: string - params
enum: properties:
- prtrn jsonrpc:
description: Method name type: number
example: prtrn format: double
params: enum:
type: array - 1
description: Request parameters - 2
items: description: JSON-RPC standard version number
$ref: '#/definitions/PaymentReturnParams' example: 1
PaymentRequestParams: id:
type: object type: integer
description: Payment request data description: Request ID
required: example: 1
- header method:
- payment_data type: string
- chrg_br enum:
properties: - prtrn
header: description: Method name
$ref: '#/definitions/DocumentHeader' example: prtrn
payment_data: params:
$ref: '#/definitions/PaymentData' type: array
chrg_br: description: Request parameters
type: string items:
enum: $ref: '#/components/schemas/PaymentReturnParams'
- SLEV minItems: 1
description: Charge Bearer maxItems: 1
example: SLEV ResolutionOfInvestigation:
PaymentReturnRequestParams: type: object
type: object required:
description: Payment return request data - jsonrpc
required: - id
- header - method
- assigner_bic - params
- assignee_bic properties:
- cancellation_id jsonrpc:
- cancelling_party type: number
- cancellation_reason format: double
- payment_data enum:
properties: - 1
header: - 2
$ref: '#/definitions/DocumentHeader' description: JSON-RPC standard version number
assigner_bic: example: 1
type: string id:
description: Assigner BIC type: integer
example: PCTULT21XXX description: Request ID
assignee_bic: example: 1
type: string method:
description: Assignee (BoL) BIC type: string
example: LIABLT2XMSD enum:
cancellation_id: - roinvstg
type: string description: Method name
description: Cancellation transaction identifier. Unique, as required in Chapter IX of the document SEPA-MMS User Detailed Functional Specifications for Credit Transfer Processing (SCT). Uniqueness is checked. example: roinvstg
example: D118100301085772 params:
cancelling_party: type: array
$ref: '#/definitions/CancellingParty' description: Request parameters
cancellation_reason: items:
$ref: '#/definitions/CancellationReason' $ref: '#/components/schemas/ResolutionOfInvestigationParams'
payment_data: minItems: 1
$ref: '#/definitions/PaymentData' maxItems: 1
PaymentReturnParams: NextMessageRequest:
type: object type: object
description: Payment return data required:
required: - jsonrpc
- header - id
- return_id - method
- return_reason - params
- returning_party properties:
- return_amount jsonrpc:
- return_currency type: number
- chrg_br format: double
- settlment_date enum:
- payment_data - 1
properties: - 2
header: description: JSON-RPC standard version number
$ref: '#/definitions/DocumentHeader' example: 1
return_id: id:
type: string type: integer
description: Return identification. Unique, as required in Chapter IX of the document SEPA-MMS User Detailed Functional Specifications for Credit Transfer Processing (SCT). Uniqueness is checked. description: Request ID
example: D118100301086072 example: 1
return_amount: method:
type: number type: string
format: double enum:
description: Returned amount, calculated according to return reason - nextmsg
example: 13.31 description: Method name
return_currency: example: nextmsg
type: string params:
enum: type: array
- EUR description: RequestParameters
description: Returned amount currency items:
example: EUR $ref: '#/components/schemas/NextMessageRequestParams'
chrg_br: minItems: 1
type: string maxItems: 1
enum: PaymentRequestParams:
- SLEV type: object
description: Charge Bearer description: Payment request data
example: SLEV required:
settlment_date: - header
type: string - payment_data
description: Current or next TARGET2 business day - chrg_br
format: date properties:
additional_info: header:
type: string $ref: '#/components/schemas/DocumentHeader'
description: Cancellation transaction identifier from FFPCRQST, only filled if return_reason/iso_code is FOCR payment_data:
example: D118100301085772 $ref: '#/components/schemas/PaymentData'
returning_party: chrg_br:
$ref: '#/definitions/ReturningParty' type: string
return_reason: enum:
$ref: '#/definitions/ReturnReason' - SLEV
payment_data: description: Charge Bearer
$ref: '#/definitions/PaymentData' example: SLEV
DocumentHeader: PaymentReturnRequestParams:
type: object type: object
description: Document header description: Payment return request data
required: required:
- doc_id - header
- type - assigner_bic
- date_time - assignee_bic
- priority - cancellation_id
- business_area - cancelling_party
properties: - cancellation_reason
doc_id: - payment_data
type: string properties:
description: Document ID - the structure is established in Section IX of the document LITAS-Pranesimu formatai.docx. header:
example: D118091001045732 $ref: '#/components/schemas/DocumentHeader'
type: assigner_bic:
type: string type: string
enum: description: Assigner BIC
- FFCCTRNS example: PCTULT21XXX
- FFPCRQST assignee_bic:
- PRTRN type: string
- ROINVSTG description: Assignee (BoL) BIC
description: Document type. Allowed values are FFCCTRNS/FFPCRQST/PRTRN/ROINVSTG example: LIABLT2XMSD
example: FFCCTRNS cancellation_id:
date_time: type: string
type: string description: >-
format: date-time Cancellation transaction identifier. Unique, as required in Chapter
description: Document creation timestamp IX of the document SEPA-MMS User Detailed Functional Specifications
example: 2018-10-03T08:48:09 for Credit Transfer Processing (SCT). Uniqueness is checked.
priority: example: D118100301085772
type: integer cancelling_party:
description: Document priority $ref: '#/components/schemas/CancellingParty'
example: 51 cancellation_reason:
business_area: $ref: '#/components/schemas/CancellationReason'
type: string payment_data:
description: Document business area $ref: '#/components/schemas/PaymentData'
example: SEPASCT PaymentReturnParams:
PaymentData: type: object
type: object description: Payment return data
description: Payment data required:
required: - header
- instr_id - return_id
- end_to_end_id - return_reason
- tx_id - returning_party
- amount - return_amount
- currency - return_currency
- date - chrg_br
- mtd - settlment_date
- prty - payment_data
- cd properties:
- debtor header:
- creditor $ref: '#/components/schemas/DocumentHeader'
properties: return_id:
instr_id: type: string
type: string description: >-
description: Instruction identification Return identification. Unique, as required in Chapter IX of the
example: D118091001048175 document SEPA-MMS User Detailed Functional Specifications for Credit
end_to_end_id: Transfer Processing (SCT). Uniqueness is checked.
type: string example: D118100301086072
description: A sending customer reference that must be passed to a receiveing customer. In the event that no reference was given, the value NOTPROVIDED must be used. return_amount:
example: NOTPROVIDED type: number
tx_id: format: double
type: string description: 'Returned amount, calculated according to return reason'
description: Unique Id of a transaction, as required in Chapter IX of the document SEPA-MMS User Detailed Functional Specifications for Credit Transfer Processing (SCT). Uniqueness is checked. example: 13.31
example: 8e7070743da24402a7fc290bc62fbcd0 return_currency:
amount: type: string
type: number enum:
format: double - EUR
description: Payment amount description: Returned amount currency
example: 13.31 example: EUR
currency: chrg_br:
type: string type: string
enum: enum:
- EUR - SLEV
description: Payment currency description: Charge Bearer
example: EUR example: SLEV
date: settlment_date:
type: string type: string
description: Payment date. In payment request must be current or next TARGET2 business day. format: date
format: date description: Current or next TARGET2 business day
mtd: example: '2018-10-03T00:00:00.000Z'
type: string additional_info:
enum: type: string
- CLRG description: >-
description: Settlment method Cancellation transaction identifier from FFPCRQST, only filled if
example: CLRG return_reason/iso_code is FOCR
prtry: example: D118100301085772
type: string returning_party:
description: Clearing system $ref: '#/components/schemas/ReturningParty'
example: LITAS-MIG return_reason:
cd: $ref: '#/components/schemas/ReturnReason'
type: string payment_data:
enum: $ref: '#/components/schemas/PaymentData'
- SEPA ResolutionOfInvestigationParams:
description: Service level code type: object
example: SEPA description: Resoultion of investigation data
debtor: required:
$ref: '#/definitions/Participant' - header
creditor: - assigner_bic
$ref: '#/definitions/Participant' - assignee_bic
CancellingParty: - status
type: object - resolution_id
description: Cancelling party data. Only one of available properties can be filled. - rejecting_party
properties: - rejection_reason
customer_name: - payment_data
type: string properties:
description: Customer name or BIC header:
example: Dan Notestein or PCTULT21XXX $ref: '#/components/schemas/DocumentHeader'
bank_bic: assigner_bic:
type: string type: string
description: Bank BIC description: Assigner BIC
example: PCTULT21XXX example: PCTULT21XXX
CancellationReason: assignee_bic:
type: object type: string
description: Cancellation reason. Only one of available properties can be filled description: Assignee (BoL) BIC
properties: example: LIABLT2XMSD
iso_code: status:
type: string type: string
enum: enum:
- DUPL - RJCR
description: ISO code of cancellation reason description: Confirmation of resolution of investigation
example: DUPL example: RJCR
code: resolution_id:
type: string type: string
enum: description: >-
- FRAD Identification of the cancellation request transaction status.
- TECH Unique, as required in Chapter IX of the document SEPA-MMS User
description: Custom code of cancellation reason Detailed Functional Specifications for Credit Transfer Processing
example: FRAD (SCT). Uniqueness is checked.
ReturningParty: example: D118100301086192
type: object rejecting_party:
description: Data of party returning payment. Only one of available properties can be filled $ref: '#/components/schemas/RejectingParty'
properties: rejection_reason:
customer_name: $ref: '#/components/schemas/RejectionReason'
type: string additional_info:
description: Customer's name or BIC type: array
example: Dan Notestein or PCTULT21XXX items:
bank_bic: type: string
type: string minItems: 1
description: Bank BIC maxItems: 2
example: PCTULT21XXX description: To be used only when code is ‘LEGL’ in order to precise the reason.
ReturnReason: example:
type: object - AT51Description
description: Reason for payment return, Only one of available properties can be filled - AT57Description
properties: payment_data:
iso_code: $ref: '#/components/schemas/PaymentData'
type: string NextMessageRequestParams:
enum: type: object
- AC01 description: Next message request parameters
- AC04 required:
- AC06 - tis_code
- AG01 properties:
- AG02 tis_code:
- AM05 type: string
- BE04 description: Two character TIS code - all generated IDs start with this
- FOCR example: D1
- MD07 DocumentHeader:
- MS02 type: object
- MS03 description: Document header
- RC01 required:
- RR01 - doc_id
- RR02 - type
- RR03 - date_time
- RR04 - priority
description: ISO code of payment return reason. Allowed values are AC01, AC04, AC06, AG01, AG02, AM05, BE04, FOCR, MD07, MS02, MS03, RC01, RR01, RR02, RR03, RR04 - business_area
example: FOCR properties:
code: doc_id:
type: string type: string
description: Custom code of payment return reason description: >-
Participant: Document ID - the structure is established in Section IX of the
type: object document LITAS-Pranesimu formatai.docx.
required: example: D118091001045732
- bic type:
- iban type: string
- name enum:
properties: - FFCCTRNS
bic: - FFPCRQST
type: string - PRTRN
description: Participant;s BIC - ROINVSTG
example: LIABLT20XXX description: Document type. Allowed values are FFCCTRNS/FFPCRQST/PRTRN/ROINVSTG
iban: example: FFCCTRNS
type: string date_time:
description: Participant's IBAN type: string
example: LT261010000002132402 format: date-time
name: description: Document creation timestamp
type: string example: '2018-10-03T08:48:09.000Z'
description: Participant's name priority:
example: Dan Notestein type: integer
country: description: Document priority
type: string example: 51
description: Participant's country ISO 3166-1 alpha-2 code business_area:
example: US type: string
address_line1: description: Document business area
type: string example: SEPASCT
description: Participant's address PaymentData:
example: PO Box 10608 type: object
address_line2: description: Payment data
type: string required:
description: Participant's address - instr_id
example: Blacksburg, VA 24062-0608 - end_to_end_id
Response: - tx_id
type: object - amount
description: API response type for 'output' type endpoints - currency
required: - date
- id - mtd
- result - prty
properties: - cd
id: - debtor
type: integer - creditor
example: 1 properties:
result: instr_id:
$ref: '#/definitions/Result' type: string
error: description: Instruction identification
$ref: '#/definitions/Error' example: D118091001048175
Result: end_to_end_id:
type: object type: string
description: Operation result description: >-
required: A sending customer reference that must be passed to a receiveing
- doc_id customer. In the event that no reference was given, the value
- status NOTPROVIDED must be used.
properties: example: NOTPROVIDED
doc_id: tx_id:
type: string type: string
description: Document ID description: >-
example: D118091001045732 Unique Id of a transaction, as required in Chapter IX of the
status: document SEPA-MMS User Detailed Functional Specifications for Credit
type: string Transfer Processing (SCT). Uniqueness is checked.
enum: example: 8e7070743da24402a7fc290bc62fbcd0
- Accepted amount:
- Error type: number
description: Request status. Available values are Accepted, Error format: double
example: Accepted description: Payment amount
Error: example: 13.31
type: object currency:
description: Error object. Only sent if result.status is 'Error' type: string
required: enum:
- code - EUR
- message description: Payment currency
properties: example: EUR
code: date:
type: string type: string
enum: description: >-
- DIS-0001 Payment date. In payment request must be current or next TARGET2
- DIS-0002 business day.
- DIS-0003 format: date
description: Error code (1 - document with given ID already exists, 2 - missing required data, 3 - technical error) example: '2018-10-03T00:00:00.000Z'
example: DIS-0001 mtd:
message: type: string
type: string enum:
description: Error message - CLRG
example: Document with given ID already exists description: Settlment method
host: localhost example: CLRG
basePath: / prtry:
schemes: type: string
- https description: Clearing system
example: LITAS-MIG
cd:
type: string
enum:
- SEPA
description: Service level code
example: SEPA
debtor:
$ref: '#/components/schemas/Participant'
creditor:
$ref: '#/components/schemas/Participant'
CancellingParty:
type: object
description: Cancelling party data. Only one of available properties can be filled.
properties:
customer_name:
type: string
description: Customer name or BIC
example: Dan Notestein or PCTULT21XXX
bank_bic:
type: string
description: Bank BIC
example: PCTULT21XXX
CancellationReason:
type: object
description: Cancellation reason. Only one of available properties can be filled
properties:
iso_code:
type: string
enum:
- DUPL
description: ISO code of cancellation reason
example: DUPL
code:
type: string
enum:
- FRAD
- TECH
description: Custom code of cancellation reason
example: FRAD
ReturningParty:
type: object
description: >-
Data of party returning payment. Only one of available properties can be
filled
properties:
customer_name:
type: string
description: Customer's name or BIC
example: Dan Notestein or PCTULT21XXX
bank_bic:
type: string
description: Bank BIC
example: PCTULT21XXX
ReturnReason:
type: object
description: >-
Reason for payment return, Only one of available properties can be
filled
properties:
iso_code:
type: string
enum:
- AC01
- AC04
- AC06
- AG01
- AG02
- AM05
- BE04
- FOCR
- MD07
- MS02
- MS03
- RC01
- RR01
- RR02
- RR03
- RR04
description: >-
ISO code of payment return reason. Allowed values are AC01, AC04,
AC06, AG01, AG02, AM05, BE04, FOCR, MD07, MS02, MS03, RC01, RR01,
RR02, RR03, RR04
example: FOCR
code:
type: string
description: Custom code of payment return reason
RejectingParty:
type: object
description: >-
Data of party rejecting payment return. Only one of available properties
can be filled
properties:
customer_name:
type: string
description: Customer's name or BIC
example: Dan Notestein or PCTULT21XXX
bank_bic:
type: string
description: Bank BIC
example: PCTULT21XXX
RejectionReason:
type: object
description: >-
Reason for payment return rejection, Only one of available properties
can be filled
properties:
iso_code:
type: string
enum:
- LEGL
- CUST
description: >-
ISO code of payment return rejection reason. Allowed values are
LEGL, CUST
example: LEGL
code:
type: string
enum:
- ARDT
- AC04
- AM04
- NOAS
- NOOR
description: >-
Custom code of payment return reason. Allowed values are ARDT, AC04,
AM04, NOAS, NOOR
Participant:
type: object
required:
- bic
- iban
- name
properties:
bic:
type: string
description: Participant;s BIC
example: LIABLT20XXX
iban:
type: string
description: Participant's IBAN
example: LT261010000002132402
name:
type: string
description: Participant's name
example: Dan Notestein
country:
type: string
description: Participant's country ISO 3166-1 alpha-2 code
example: US
address_line1:
type: string
description: Participant's address
example: PO Box 10608
address_line2:
type: string
description: Participant's address
example: 'Blacksburg, VA 24062-0608'
Response:
type: object
description: API response type for 'output' type endpoints
required:
- id
- result
properties:
id:
type: integer
description: Request ID
example: 1
result:
$ref: '#/components/schemas/Result'
error:
$ref: '#/components/schemas/Error'
NextMessageResponse:
type: object
description: API response type for NextMessage endpoint
required:
- id
- result
properties:
id:
type: integer
description: Request ID
example: 1
result:
oneOf:
- $ref: '#/components/schemas/ErrorDocument'
- $ref: '#/components/schemas/Document'
error:
$ref: '#/components/schemas/Error'
Result:
type: object
description: Operation result
required:
- doc_id
- status
properties:
doc_id:
type: string
description: Document ID
example: D118091001045732
status:
type: string
enum:
- Accepted
- Error
description: 'Request status. Available values are Accepted, Error'
example: Accepted
ErrorDocument:
type: object
description: >-
Document describing an error received from PAS (AUTHRES, SYNRES, RETURN)
or processing error in CPR subsystem
required:
- doc_id
- doc_ref_id
- timestamp
- error_code
- error_message
properties:
doc_id:
type: string
description: >-
ID of this document - generated either by PAS or CDR - the same
format as any other document ID
example: PS18091010000007
doc_ref_id:
type: string
description: Reference to the document that caused the error
example: D118091001045732
timestamp:
type: string
format: date-time
description: Timestamp of this document's creation
example: '2018-09-10T11:41:54.000Z'
error_code:
type: string
description: Error code as provided by PAS or CPR
example: PAS-81500000
error_message:
type: string
description: Error message as provided by PAS or CPR
example: >-
Priimami tik pasirašyti LITAS-INST ir PROXY sistemų pranešimai. Only
LITAS-INST and PROXY signed messages are accepted.
Document:
type: object
description: >-
One of possible incoming document types - data will be deserialized from
XML to Java class and then serialized to JSON
Error:
type: object
description: Error object. Only sent if result.status is 'Error'
required:
- code
- message
properties:
code:
type: string
enum:
- DIS-0001
- DIS-0002
- DIS-0003
description: >-
Error code (1 - document with given ID already exists, 2 - missing
required data, 3 - technical error)
example: DIS-0001
message:
type: string
description: Error message
example: Document with given ID already exists
``` ```
\ No newline at end of file