Purpose
Returns declaration requests that were created through V2 and V3
Key features
Fields person_id
and data_to_be_signed
will be empty if declaration request is created by V2.
Only authenticated and authorized user can use declaration request
The service returns only a declaration request that was created in the same legal entity as the user
Specification
Link | |
Resource | /api/v3/declaration_requests/{{id}} |
Scope | declaration_request:read |
Components | Declarations |
Using Microservices | il/api ops/api |
Protocol type | REST |
Request type | GET |
Sync/Async | API paragraph not found |
Public/Private/Internal | Public |
Logic
API paragraph not found
Input parameters
Filter | Values | Type | Description | Example |
---|---|---|---|---|
id |
| String | request identifier |
|
Authorize
Verify the validity of access token
Return 401 in case validation fails
Check scopes in order to perform this action (scope = 'declaration_request:read')
Return 403 in case invalid scope(s)
Request to process the request using a token in the headers.
Headers
Content-Type:application/json
Authorization:Bearer c2778f3064753ea70de870a53795f5c9
Response structure
Print form is generated after approve declaration request, so in response on Get declaration request by id show fields context
and data_to_be_signed
if DR approved.
HTTP status codes
HTTP status code | Message | What caused the error |
---|---|---|
200 | Response |
|
401 | Access token validation failed | |
403 | Invalid scope |
Backward compatibility
This endpoint shows the declaration requests which are created by V2 and V3. Due to the fact that structure of declaration request V2 is different from the structure of decl request V3 , so not all fields od decl request v2 can be displayed.