1 of 100

API cookbooks

Welcome

Authentication

About authentication

To use Tuum's API, you must first authenticate. Once you have completed the authentication process, you will receive a . This token allows you to make authorised API calls within the Tuum system.

Tuum has two different API endpoints for authentication:

You must choose the authentication endpoint applicable to the context in which you will make API requests.

When making API requests for your employees, select the authentication endpoint for employees.
When making API requests for your customers, select the authentication endpoint for customers.

In this part of the API cookbook, you will find:

Authenticate employee

Here, you can learn how to make an API call to authenticate an employee. Once you execute the call successfully, you will receive a JSON web token that permits you to make authorised API calls to other Tuum API endpoints.

Sample API call

To authenticate an employee, make the following API call.

https://auth-api.sandbox.tuumplatform.com/api/v1/employees/authorise

Learn more about the endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the API call for authentication of an employee.

Please make sure to input the username and password of the particular employee when submitting your request.

Sample response

Below you find an example response body to the API call above.

Response

Result

An employee is authenticated, and a JSON Web Token is returned in the response.

In order to make authorised API calls, the JSON Web Token that was received must be used as a parameter value for the x-auth-token header parameter.

Create customer credentials

Here, you can learn how to make an API call to create customer credentials. Once the call is successful, your customers can authenticate themselves using the created credentials.

Sample API call

To create customer credentials, make the following API call.

https://auth-api.sandbox.tuumplatform.com/api/v1/credentials

Learn more about the create customer credentials endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the API call to create customer credentials.

{
"personId": "ID-1038",
"username": "customer_username",
"password": "customer_password"
}

curl 'https://auth-api.sandbox.tuumplatform.com/api/v1/credentials' \
-H 'x-auth-token: eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJuYW1lIjoiYWF0b21payIsInBlcnNvbklkIjoiSUQtMTAzOCIsInRlbmFudENvZGUiOiJNQiIsImV4cGlyeURUaW1lIjoiMjAyMy0wNy0yOFQxMjoyMDoyMSIsImV4cCI6MTY5MDU0NjgyMX0.wpNOfTan73vnqQNZo5cI99B2NWuVZ6wurW9JiO7z0x0' \
-H 'Content-Type: application/json' \
-d '{
"personId": "ID-1038",
"username": "customer_username",
"password": "customer_password"
}'

Please make sure to input the username and password of the particular customer when submitting your request.

To make a successful API call, you must include the JSON Web Token of the authenticated employee with specific user rights as a header parameter with the value of x-auth-token. Kindly adhere to the instructions given in the explanations for header parameters.

Sample response

Below you find an example response body to the API call above.

Response

{
    "errors": null,
    "validationErrors": null,
    "data": {
        "credentialId": "ID-1005",
        "personId": "ID-1038",
        "username": "customer_username",
        "tenantId": "ID-1000"
    }
}

Result

After making the API call, customer credentials will be created so that they can authenticate themselves.

Authenticate customer

Here, you can learn how to make an API call to authenticate a customer. Once you execute the call successfully, you will receive a JSON web token that permits you to make authorised API calls to other Tuum API endpoints.

Sample API call

To authenticate a customer, make the following API call.

https://auth-api.sandbox.tuumplatform.com/api/v1/authorise

Learn more about the authenticate customer endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the API call for authentication of a customer.

{
"username": "customer_username",
"password": "customer_password"
}

curl 'https://auth-api.sandbox.tuumplatform.com/api/v1/authorise' \
-H 'Content-Type: application/json' \
-d '{
"username": "customer_username",
"password": "customer_password"
}'

Please make sure to input the username and password of the particular customer when submitting your request.

If your customer doesn't have login details, you can create them following the instructions provided in the Create customer credentials example.

Sample response

Below you find an example response body to the API call above.

Response

{
    "errors": null,
    "validationErrors": null,
    "data": {
        "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJuYW1lIjoiYWF0b21payIsInBlcnNvbklkIjoiSUQtMTAzOCIsInRlbmFudENvZGUiOiJNQiIsImV4cGlyeURUaW1lIjoiMjAyMy0wNy0yOFQxMjoyMDoyMSIsImV4cCI6MTY5MDU0NjgyMX0.wpNOfTan73vnqQNZo5cI99B2NWuVZ6wurW9JiO7z0x0"
    }
}

Result

An customer is authenticated, and a JSON Web Token is returned in the response.

In order to make authorised API calls, the JSON Web Token that was received must be used as a parameter value for the x-auth-token header parameter.

Refresh JSON Web Token

Here, you can learn how to make an API call to refresh a valid JSON Web Token. Once you execute the call successfully, you will receive a JSON Web Token with new expiration time.

You can use the refresh JSON Web Token endpoint to renew a valid token of an employee or customer. For renewal, provide the respective token as the value for the x-auth-token header parameter.

Sample API call

To refresh a valid JSON Web Token, make the following API call.

https://auth-api.sandbox.tuumplatform.com/api/v1/authorise/refresh

Learn more about the endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the API call to refresh a valid JSON Web Token.

This POST request does not have a body.

Sample response

Below you find an example response body to the API call above.

Response

Result

The response will contain a fresh JSON Web Token with an updated expiration time.

You can keep making API calls using the renewed JSON Web Token.

Invalidate customer credentials

Here, you can learn how to make an API call to invalidate customer credentials. Once the call succeeds, your customer cannot authenticate using the invalidated credentials.

Sample API call

To create customer credentials, make the following API call.

https://auth-api.sandbox.tuumplatform.com/api/v1/credentials/invalidate

Learn more about the in the Tuum developer portal.

Invalidate customer credentials

POST https://auth-api.sandbox.tuumplatform.com/api/v1/credentials/invalidate

Learn more about the in the Tuum developer portal.

Sample request

Below is an example request body of the API call to invalidate customer credentials.

Please make sure to input the username and password of the particular customer when submitting your request.

Sample response

Below you find an example response body to the API call above.

Response

Result

After making the API call, the customer's credentials become invalid, making it impossible to authenticate themselves.

Export-import roles

Here, you can learn how to use APIs to export roles and their privileges from one Tuum environment and import them into another. This functionality aims to facilitate smooth replication for testing across different environments.

Tuum offers three API endpoints for exporting and importing roles and their associated privileges.

Export roles endpoint enables you to retrieve all roles or specific roles and their privileges from the source Tuum environment.
Partial import endpoint allows you to add a selected set of roles and their privileges to the target Tuum environment. Any existing roles and privileges in the target environment not included in the import will remain unchanged.
Complete import endpoint lets you delete all existing roles and their privileges in the target environment and replace them with new roles and privileges specified in the payload.

The export and import functionality is restricted to users with the EXPORT_IMPORT_ROLE_PRIVILEGES privilege. Learn here how to assign privileges.

Export selected roles

In this example, you can learn how to retrieve specific roles and their privileges from the source Tuum environment.

To export all roles and privileges, make the same API call with an empty request body.

Use case

In this example, we will export specific roles and privileges.

Use case data

API parameters with values

The system will export only roles and associated privileges with a valid validity range.

Sample API call

To export specific roles and privileges, make the following API call.

https://auth-api.sandbox.tuumplatform.com/api/v1/roles/privileges/export

Learn more about the in the Tuum developer portal.

Sample request

Below is an example request body of the API call for export roles.

Sample response

Below you find an example response body to the API call above.

Response

Result

The selected valid roles ACCOUNTANT and TEST_LT with related privileges have been exported.

Use the response content to import roles and privileges into the target environment.

Import all roles

In this example, you can learn how to replace all roles and their privileges in the target Tuum environment.

This endpoint is disabled for the Prod (Live) environment and is available only for non-Prod environments like DEV, TEST, or similar ones.

As a precondition to import, first export all roles and associated privileges by making the API call, as shown in the example of exporting selected roles with an empty request body.

Use case

In this example, we showcase the steps to replace all roles and associated privileges in the target environment using the data retrieved in your export roles request.

Use case data

API parameters with values

We want to import all roles to the target environment and thus we have to use the roles and privileges from the response of the export done before.

The system will import only roles and privileges with a valid validity range.

Sample API calls

To import all roles and privileges, make the following API call with the roles and associated privileges (exported before) in the request body.

https://auth-api.{another-environment}.tuumplatform.com/api/v1/roles/privileges/import

Learn more about the endpoint in the Tuum developer portal.

Result

All valid roles and their privileges in the target environment have been replaced with roles and associated privileges exported from the source environment.

Header parameters

Mandatory parameters

To make an authorised API call, you must include the x-auth-token header parameter.

x-auth-token

For the HTTP header parameter x-auth-token, use the JWT token you received in response to the authentication call as a parameter value.

Example cURL with employee token

-H 'x-auth-token: eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJleHBpcnlEVGltZSI6IjIwMjMtMDMtMDhUMDg6NDg6NDkiLCJyb2xlcyI6WyJBRE1JTiJdLCJuYW1lIjoiSm9obiBPZmZpY2VyIiwiZW1wbG95ZWVJZCI6IjEiLCJ0ZW5hbnRDb2RlIjoiTUIiLCJleHAiOjE2NzgyNjUzMjl9.G7rqNTJbeyMdMy1ZGwu1G7JRSvwAg084IiBYhOEz4I8'

Optional parameters

To protect your POST requests against duplicating, you can use the optional header parameter x-request-id - request ID.

The request ID value must be in the format of a Universally Unique IDentifier (UUID), RFC 4122.

Below we will provide examples to show the difference in the API call outcomes with and without the request ID header parameter.

Use case

We will review several examples that illustrate the difference in the API outcomes when the request ID is used and when the request ID is not applied.

The initial request data:

Use case data

API parameters with values

Person's Tuum id is ID-3419.

The name of the account holder is Eleanor Rigby.

Eleanor is a resident of Great Britain.

The standard price list is assigned to the account.

Eleanor is assigned to the GROUP_A customer group.

Currency account type.

The account currency code is GBP.

Explanatory examples

To view the examples, go to the following pages:

Summary

From the illustrated examples we can see that when the x-request-id parameter is applied, it prevents the system from creating new objects. And when the x-request-id is not used or is used with unique value as per each call, all the POST calls are treated as unique and new objects are created:

POST call / Request ID

Same request ID

No or unique request ID

Initial POST call

Unique response

Duplicated POST call

Same as in the initial response

Unique response

Duplicated POST with updated data

Same as in the initial response

Unique response

Usage recommendations

If you use the x-request-id header parameter, it is recommended to avoid reusing the same parameter value, even if the requests are made to different Tuum APIs.

Employee

Create employee

Use case

In this use case, we will create a new employee with the following data set:

Use case data

API parameters with values

Sample API call

To create a new employee, make the following API call.

https://auth-api.sandbox.tuumplatform.com/api/v1/employees

Learn more about the endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the API call for creating an employee.

Sample response

Below you find an example response body to the API call above.

Response

Result

As a result, a new employee with the employeeId: ID-1183 was created.

Find employee by ID

Use case

In this example, we will find an existing employee by employeeId.

Use case data

API parameters with values

We will search an employee ID-1183 whose .

...api/v1/employees/ID-1183

Sample API call

To find an employee by username, make the following API call.

https://auth-api.sandbox.tuumplatform.com/api/v1/employees/username

Learn more about the find employee endpoint in the Tuum developer portal.

Sample request

Below is an example request of the API call to retrieve customer data.

No request body.

curl --location 'https://auth-api.sandbox.tuumplatform.com/api/v1/employees/ID-1183' \
--header 'x-channel-code: BACKOFFICE' \
--header 'x-auth-token: eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJuYW1lIjoiT2ZmaWNlciBUZXN0IiwiZW1wbG95ZWVJZCI6IklELTEwMDAiLCJ0ZW5hbnRDb2RlIjoiTUIiLCJleHBpcnlEVGltZSI6IjIwMjQtMTItMTZUMjI6Mzk6MTUiLCJleHAiOjE3MzQzODg3NTUsInJvbGVzIjpbIkFETUlOIl19.ftJgnhviaIP-qTsXh19FIG6wpZntGXezBIXHVK0-63U' \
--data ''

Sample response

Below you find an example response body to the API call above.

Response

{
    "errors": null,
    "validationErrors": null,
    "data": {
        "employeeId": "ID-1183",
        "firstName": "Test",
        "lastName": "Employee",
        "username": "[email protected]",
        "email": "[email protected]",
        "authenticationMethod": "PASSWORD",
        "defaultTenantCode": "MB",
        "roles": [
            "CUSTOMER_SERVICE"
        ],
        "tenants": [
            {
                "tenantEmployeeId": "ID-1213",
                "defaultTenant": true,
                "tenantId": "ID-1000",
                "tenantCode": "MB",
                "roles": [
                    "CUSTOMER_SERVICE"
                ]
            }
        ],
        "externalId": null,
        "lastLogin": "2024-11-25T12:28:04.635156Z",
        "blockedUntil": null,
        "failedAttempts": 0
    }
}

Result

The result of the API call is the dataset of a particular employee.

Find employee by username

Use case

In this example, we will review how to find an employee by username.

Use case data

API parameters with values

Sample API call

To find an employee by username, make the following API call.

https://auth-api.sandbox.tuumplatform.com/api/v1/employees/{employeeId}

Learn more about the endpoint in the Tuum developer portal.

Sample request

Below is an example request of the API call to retrieve customer data.

No request body.

Sample response

Below you find an example response body to the API call above.

Response

Result

The result of the API call is the dataset of a particular employee.

Person

Find person

This guide will help you find details about an individual or a legal entity.

The endpoint provides a detailed overview of the person from various APIs.

The endpoint provides person's address details.

You can use use other endpoints to find person details such as , , , , , , , , , , and . Select the appropriate endpoint based on the specific requirements to retrieve the necessary person data.

Based on your use case, use either of the endpoints to retrieve person data:

Find person addresses

Use case

Learn how to find a particular person's addresses in Tuum. In this example, we will demonstrate it on a private person using the following data.

Use case data

API parameters with values

To retrieve the record of a legal entity, use the same API endpoint.

Sample API call

To retrieve customer data, make the following API call.

https://person-api.sandbox.tuumplatform.com/api/v1/persons/ID-3392/addresses

Learn more about the endpoint in the Tuum developer portal.

Sample request

Below is an example request of the API call to retrieve person addresses.

No request body.

Sample response

Below you find an example response body to the API call above.

Response

Result

The result of the API call is the overview of the addresses linked to the person.

Create person document

Use case

In this example, we will review how to add a document record for a person.

Use case data

API parameters with values

You can add different types of personal documents: ID cards, passports, driving licences and residence permits. See more in the .

Sample API call

To create a person document, make the following API call.

https://person-api.sandbox.tuumplatform.com/api/v1/persons/ID-3392/documents

See more about the endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the API call for creating a person document.

Sample response

Below you will find an example response to the API call from above.

Response

Result

A new passport record ID-1024 was added for a private person.

Update person address

Use case

Here we will review how to update the person address.

Use case data

API parameters with values

The addressId parameter is generated when a . You can fetch the current address data by calling the endpoint.

Sample API call

To update person address, make the following call.

https://person-api.sandbox.tuumplatform.com/api/v2/persons/ID-3397/addresses/ID-3088

See more information about the endpoint in the Tuum developer portal.

Sample request

Below is an example body request of the API call for updating the person address.

Sample response

Below you find an example response body to the API call above.

Response

Result

The person address information is updated.

Create customer group

Use case

Here we will review how to create customer groups that are used to make different price decisions based on the group. We will create a new customer group using the following data:

Use case data

API parameters with values

Sample API call

To create a new customer group, make the following API call.

https://person-api.sandbox.tuumplatform.com/api/v1/person-group-types

See more information about the endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the API call for creating a new customer group.

Sample response

Here you find an example response body to the API call above.

Response

Result

A new BUSINESS customer group is created.

Assign person to group

Use case

Here we will review how to assign a person to the customer group. Let us assign a private person, Trevor Tuum, to a business customer group.

Use case data

API parameters with values

Sample API cal

To assign a person to the customer group, make the following API call.

https://person-api.sandbox.tuumplatform.com/api/v2/persons/ID-3392/person-groups

To learn more about the endpoint, check the Tuum developer portal.

Sample request

Below is the example body request of the API call for assigning a person to the group.

Sample response

Here you find an example response body to the API call above.

Response

Result

The user ID-3392 is assigned to the BUSINESS customer group.

Create person financial data

Use case

In this example, we will show how to set up legal person financial data. We will modify New company Ltd and add assets as a currency worth 10000000 EUR.

Use case data

API parameters with values

Learn more about the endpoint details in the Tuum developer portal.

Sample API call

To create financial data, call the following endpoint.

https://person-api.sandbox.tuumplatform.com/api/v1/persons/ID-3394/financial-data

Sample request

Below is an example request body of the API call for creating person representation.

Sample response

Below you will find an example response to the API call from above.

Response

Result

Assets as a currency worth 10000000 EUR are added to the legal person.

Reactivate person

Use case

Here, you can learn how to reactivate a person who is in INACTIVE status. We will reactivate a private person, Rhys Davey, who was inactivated previously, but has now returned as a client.

Use case data

API parameters with values

The personId of Rhys Davey who we want to reactivate isID-3204.

Since the person returned as a client, the reason can be set as OTHER.

The reactivation is effective from June 15th 2023. The date format: YYYY-MM-DD.

You can use different values for the processReason parameter, which can be defined from Lookups.

The by default processReason-s for private and legal persons:

ERROR,
OTHER.

Sample API call

To reactivate a person, make the following API call.

https://person-api.sandbox.tuumplatform.com/api/v1/persons/ID-3204/reactivate/start

Learn more about the reactivate person endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the API call to inactivate a person.

{
  "processReason": "OTHER",
  "processDate": "2023-06-15"
}

curl --location 'https://person-api.sandbox.tuumplatform.com/api/v1/persons/ID-3204/reactivate/start' \
--header 'x-auth-token: eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJuYW1lIjoiTGF1cmEgVCIsImVtcGxveWVlSWQiOiJJRC0xMDU0IiwidGVuYW50Q29kZSI6Ik1CIiwiZXhwaXJ5RFRpbWUiOiIyMDI1LTAzLTA1VDE1OjEwOjE4IiwiZXhwIjoxNzQxMTg3NDE4LCJyb2xlcyI6WyJBRE1JTiJdfQ.gnVRav5NmpZapS3uGMLt69xADsYdEPiGGOjXnt1jqyY' \
--header 'x-channel-code: SYSTEM' \
--header 'Accept-Language: en' \
--header 'Content-Type: application/json' \
--data '{
  "processReason": "OTHER",
  "processDate": "2023-06-15"
}'

Sample response

Below you find an example response body to the API call above.

Response

{
    "errors": null,
    "validationErrors": null,
    "data": null
}

Result

The person's status is changed to PENDING. The person can be activated with Activate person endpoint.

Forget person

Use case

In this use case, we will review a situation when a person - Rhys Davey with personId ID-3204, who has the account inactivated, requested the bank to remove the personal data. To complete this request, you can initiate the forget person process.

Sample API call

To initiate the forget person process, make the following API call.

https://person-api.sandbox.tuumplatform.com/api/v1/persons/ID-3204/forget/start

Learn more about the endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the forget person API call.

Sample response

The forget person generates the following response.

Response

Result

As an outcome, the personal data of Rhys Davey ID-3204 is forgotten.

Remove person restoration key

Use case

In this example, we will review how to forget a person record forever and make it unrecoverable.

Use case data

API parameters with values

Sample API call

To remove the restoration key, make the following call.

https://person-api.sandbox.tuumplatform.com/api/v1/persons/ID-3415/forget/key

See more about the endpoint in the Tuum developer portal.

Sample request

Below is an example request to remove the restoration key call.

No request body.

Sample response

The remove restoration key endpoint generates the following response.

Response

Result

The restoration key of a forgotten person ID-3415 is removed. The personal data that belong to the person is non-recoverable.

ACCOUNTS

Savings accounts

A savings account is a type of account designed to help customers save money for specific goals while earning a higher interest rate. To open a savings account, you must have an existing currency account (called the servicing account) and provide an initial deposit.

These API call examples demonstrate how to create a new savings account, retrieve its unique savings ID, and set up a savings order to automate recurring deposits.

See the sections below for details:

Create account limit code

Use case

In this example, we will review how to set up an account limit code. This parameter gives a name and description of the account limit that will be configured in the further articles.

Use case data

API parameters with values

Sample API call

To create a new account limit code, make the following call.

Create account limit code

https://account-api.sandbox.tuumplatform.com/api/v1/limits/codes

See more information about this in the Tuum developer portal.

Sample request

Below is an example body request of the API call for creating an account limit code.

Sample response

Below you find an example response body to the API call above.

Response

Result

A new limit code NEW_ACCOUNT_LIMIT is created and enabled. This parameter will be used for setting up an account limit type.

Create account limit type

Use case

Here, we will create a single currency account limit type with the account scope.

Use case data

API parameters with values

You can find more information about the in the dev portal.

Sample API call

To create an account limit type, make the following call.

https://account-api.sandbox.tuumplatform.com/api/v1/limits/types

See more about the create

in the Tuum developer portal.

Sample request

Below is an example request body of the API call for creating an account and setting access rights.

Sample response

Below you find an example response body to the API call above.

Response

Result

A new single currency account limit type is created - ID-1002. In the , we will assign this limit type to an existing account and define the limit amount.

Create account class code

Use case

In this example, we will show how to create an account class code.

Use case data

API parameters

Sample API call

To create a new account class code, make the following API call.

https://account-api.sandbox.tuumplatform.com/api/v1/account-class-codes

See more information about the endpoint in the Tuum developer portal.

Create account class code

POST https://account-api.sandbox.tuumplatform.com/api/v1/account-class-codes

See more information about this in the Tuum developer portal.

Sample request

Below is an example request body of the API call for creating an account class code.

Sample response

Below you find an example response body to the API call above.

Response

Result

A new account class code is created.

Reports

About reports

To generate and download a report, follow these steps as part of the standard report flow:

Request to generate a report.
Check the report generation status.
Download the requested report.

For more detailed information about specific report workflows, refer to the available report guides.

Account transactions report

You can generate an accounts transactions report in CSV or JSON format by following these steps:

Check account transactions report generation status

Here, you will learn how to check the generation status of account transactions report in Tuum.

Use case

In this example, we will review how to check the status of a requested report file.

Use case data

API parameters with values

Sample API call

To find the status of the requested report, make the following API call.

reports-api.sandbox.tuumplatform.com/ api/v2/generations/{generationId}

Learn more about the endpoint in the Tuum developer portal.

Sample request

Below is an example request of the API call to find report status.

No request body.

Sample response

Below you find an example response body to the API call above.

Response

Result

This endpoint returns the status of the account transactions report. When the statusCode has a value DONE, the report is ready for . In this example, the generationFileId of the report file is ID-2864.

Download requested account transactions report

Here, you will learn how to download the requested account transactions report as a JSON or CSV file in Tuum.

Use case

In this use case, we will review how to download an account transactions report.

Use case data

API parameters with values

The generationFileId value is ID-2864. This parameter is generated when .

...generations/files/ID-2864

Sample API call

To find the status of the requested report, make the following API call. reports-api.sandbox.tuumplatform.com/ /api/v1/generations/files/{generationFileId}

Learn more about the get the report file endpoint in the Tuum developer portal.

Sample request

Below is an example request of the API call to get the report file.

No body request.

curl --location 'https://reports-api.sandbox.tuumplatform.com/api/v1/generations/files/ID-2864' \
--header 'x-channel-code: system' \
--header 'x-auth-token: eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJuYW1lIjoiT2ZmaWNlciBUZXN0IiwiZW1wbG95ZWVJZCI6IklELTEyMzgiLCJ0ZW5hbnRDb2RlIjoiTUIuRVUiLCJleHBpcnlEVGltZSI6IjIwMjUtMDMtMDdUMjM6MTQ6NTkiLCJleHAiOjE3NDEzODkyOTksInJvbGVzIjpbIkFDQ09VTlRBTlQiLCJBRE1JTiJdfQ.M_9PeWkEX4izXTAhYPNzj68FrMxB7gFJ7Zum9VPECKE' \
--data ''

Sample response

Below you find an example response body to the API call above.

Response

[{"transactionId":"ID-275388","groupId":"290379","postingDate":"2029-04-01","valueDate":"2029-04-01","accountId":"ID-12333","transactionTypeCode":"ACC_ADM_FEE","transactionSubtypeCode":null,"transactionGroupCode":"FEE","directionCode":"OUT","transactionAmount":{"amount":5.00,"currencyCode":"EUR"},"initialBalanceAmount":{"amount":-5.00,"currencyCode":"EUR"},"filingCode":"2029040100275388","source":{"sourceName":"ACCOUNT.ACCOUNT_PERIODIC_FEE","sourceRef":"ID-78253"},"contractSource":null,"counterparty":null,"details":"Account maintenance fee","referenceNumber":null,"metaInfo":null,"merchantInfo":null,"transactionDTime":"2025-02-28T11:23:58.16Z","reversedTransactionId":null,"endToEndId":null,"paymentServiceProviderCode":null,"virtualAccountId":null,"labels":[],"uniqueIdentifier":"1f78c038-96a6-4882-925e-ce8cd2668220","reportDateType":"POSTING_DATE","domainCode":"ACMT","familyCode":"MDOP","subfamilyCode":"FEES","reversed":false}, {"transactionId":"ID-1005","groupId":"1005","postingDate":"2024-06-11","valueDate":"2024-06-11","accountId":"ID-1006","transactionTypeCode":"ACC2SEPA_PAY","transactionSubtypeCode":null,"transactionGroupCode":"PAYMENT","directionCode":"OUT","transactionAmount":{"amount":1.00,"currencyCode":"EUR"},"initialBalanceAmount":{"amount":20000.00,"currencyCode":"EUR"},"filingCode":"2024061100001005","source":{"sourceName":"PAYMENT","sourceRef":"PAYM-1000"},"contractSource":null,"counterparty":{"name":"Simon Parker","accountNumber":{"value":"EE871275295834652820","type":"IBAN"},"accountNumberSubtype":null,"accountNumberCountryCode":"EE","financialInstitutionId":{"value":"PARXEE22XXX","type":"BIC"}},"details":"test","referenceNumber":null,"metaInfo":"{\"paymentResidencyCountryCode\":\"LV\",\"intrabankPaymentSource\":null,\"paymentMetaInfo\":\"[{\\\"typeCode\\\":\\\"SELECTED_SCHEME\\\",\\\"value\\\":\\\"SEPA_REGULAR\\\"}]\"}","merchantInfo":null,"transactionDTime":"2024-06-11T07:13:38.232717Z","reversedTransactionId":null,"endToEndId":null,"paymentServiceProviderCode":"SEPA","virtualAccountId":null,"labels":["COUNTERPARTY_EE","SEPA_REGULAR"],"uniqueIdentifier":"294ecf20-0e7f-46f8-9abe-3f4e040313bc","reportDateType":"POSTING_DATE","domainCode":"PMNT","familyCode":"ICDT","subfamilyCode":"OTHR","reversed":false}]

Result

As a result, the generated account transactions report was downloaded.

Sample account transaction export file

Below, you will find a sample of account transaction export file.

2KB

account_transaction_export.json

Open

1KB

account_transaction_export.csv

Open

QMR - Quarterly Mastercard report

You can generate a quarterly Mastercard report in PDF format by following these steps:

Check QMR generation status

Here, you will learn how to check the generation status of QMR in Tuum.

Use case

In this use case, we will demonstrate how to check the generation status of a requested QMR.

Use case data

API parameters with values

Sample API call

To find the status of the requested report, make the following API call.

reports-api.sandbox.tuumplatform.com/ api/v2/generations/{generationId}

Learn more about the endpoint in the Tuum developer portal.

Sample request

The sample request body is as follows:

No request body.

Sample response

Below you will find the response to the API request:

Response

Result

This endpoint returns the status of the QMR. When the statusCode value is DONE, the report is . In this example, the sourceRef for exporting the PDF file is ID-4359.

DEPOSITS

Deposit product management

Instructions in this section will help you to manage deposit products throughout their lifecycle.

Below you will find the following chapters:

Create deposit class code

Use case

Here we will review how to create deposit class codes that can be used to define separate general ledger accounts for different deposit products. We will create a new deposit class code for the premium customers.

Use case data

API parameters with values

Sample API call

To create a new deposit class code, make the following API call.

deposit-api.sandbox.tuumplatform.com/api/v1/deposit-class-codes

See more about the endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the API call for creating a deposit class code.

Sample response

Below you find an example response body to the API call above.

Response

Result

As an outcome, a new deposit class code for premium customers was created.

Activate deposit product

Use case

In this use case we will activate a new deposit product that was created as a previous step.

Use case data

API parameters with values

The path parameter is depositTypeCode. We will use the PREMIUM deposit product.

.../product/PREMIUM/activate

Sample API call

To activate a deposit product, make the following API call.

deposit-api.sandbox.tuumplatform.com/api/v1/deposits/product/{depositTypeCode}/activate

See more information about the activate deposit product endpoint in the Tuum developer portal.

Sample response

Below you find an example response body to the API call above.

Response

{
    "errors": null,
    "validationErrors": null,
    "data": null
}

Result

As a result, the PREMIUM deposit product was activated.

Find deposit product

Use case

In this example, we will find the .

Use case data

API parameters with values

Sample API call

deposit-api.sandbox.tuumplatform.com/api/v1/deposits/product/{depositTypeCode}

See more about the endpoint in the Tuum developer portal.

Sample response

Below you find an example response body to the API call above.

Response

Result

As a result, a complete set of product details about the PREMIUM deposit product was returned.

Inactivate deposit product

Use case

In this example, we will review how to deactivate a deposit product.

Use case data

API parameters with values

Sample API call

To deactivate a deposit product, make the following API call.

deposit-api.sandbox.tuumplatform.com/api/v1/deposits/product/{depositTypeCode}/deactivate

See more information about the endpoint in the Tuum developer portal.

Sample response

Below, you find an example response body to the API call above.

Response

Result

As a result, the PREMIUM deposit product was deactivated.

Once a deposit product is deactivated, the existing active contracts created under this product will remain active until they reach their maturity date.
Opening new contracts for a deactivated deposit product is not possible.

Deposit flow

In this block, you will learn how to open a deposit contract flow. There are two flows available:

Deposit flow - from application

The first deposit flow starts from a deposit application and includes the following steps:

- once the deposit application is created, the Tuum system automatically creates a related deposit offer.
- once the deposit offer is accepted, the Tuum system automatically creates a related deposit contract. Or - reject the offer and terminate the flow.

Deposit flow - from offer

You can use this flow if your organisation processes deposit applications outside the Tuum system.

When using the deposit offer flow, you can set or change the interest rate within the deposit product min/max range. On the contrary, the deposit application flow always uses the default interest rate with no option to change it.

This deposit contract flow starts from a deposit offer and includes the following steps:

- to enter the required deposit information into the Tuum system.
- once the deposit offer is accepted, the Tuum system will automatically create a deposit contract based on the deposit offer. Or - to reject the deposit offer and terminate the flow.

Below, you will find the following chapters:

Find deposit application

Use case

In this case, we will review how to find the ID of a created deposit application using person ID.

Use case data

API parameters with values

We will find an existing that was created for the test person with ID-2660.

...v2/persons/ID-2660/applications

This API call requires mandatory query parameters pageSize and pageNumber.

...?pageSize=1&pageNumber=1

Sample API call

To find a deposit application, make the following API call.

deposit-api.sandbox.tuumplatform.com/api/v3/persons/{personId}/applications

See more about the find deposit application endpoint in the Tuum developer portal.

Sample response

Below you find an example response body to the API call above.

Response

{
    "errors": null,
    "validationErrors": null,
    "data": {
        "values": [
            {
                "applicationId": "ID-1696407202",
                "personId": "ID-2660",
                "depositGroupCode": "TIME_DEPOSIT",
                "depositTypeCode": "PREMIUM_TEST",
                "statusCode": "ACCEPTED",
                "accountId": "ID-5334",
                "period": 3,
                "periodTypeCode": "MONTH",
                "endDate": null,
                "initialMoney": {
                    "amount": 5000.00,
                    "currencyCode": "EUR"
                },
                "interestPaymentFreqCode": "END",
                "prolongationCode": null,
                "countryCode": "EE",
                "interestRate": 0.25,
                "postingDate": "2024-11-14",
                "channelCode": "SYSTEM",
                "tenantCode": "MB",
                "offerId": null,
                "depositClassCode": "PREMIUM_CUSTOMER",
                "payoutDetails": null,
                "personTypeCode": "P",
                "taxResidencyCountryCode": "EE",
                "taxExempt": false
            }
        ],
        "pageNumber": 1,
        "pageSize": 1,
        "endReached": true,
        "sort": null
    }
}

Result

As a result we found the deposit application with the ID-1696407202 and fetched other information related to the deposit application.

Find deposit offer

Use case

In this example, we will review how to find a deposit offer using the application ID.

Use case data

API parameters with values

Searching the deposit offer that was created for the with ID-1696407202.

...applications/ID-1696407202/offers

Sample API call

To find a deposit offer that was automatically created by the deposit application, make the following API call.

deposit-api.sandbox.tuumplatform.com/api/v2/applications/{applicationId}/offers

See more about the find offer endpoint in the Tuum developer portal.

Sample response

Below you find an example response body to the API call above.

Response

{
    "errors": null,
    "validationErrors": null,
    "data": {
        "offerId": "ID-1696407305",
        "personId": "ID-2660",
        "applicationId": "ID-1696407202",
        "depositGroupCode": "TIME_DEPOSIT",
        "depositTypeCode": "PREMIUM_TEST",
        "terminationType": "WITHOUT_INTEREST",
        "statusCode": "PRESENTED",
        "reasonCode": null,
        "accountId": "ID-1012",
        "interestRate": 0.25,
        "period": 3,
        "periodTypeCode": "MONTH",
        "endDate": null,
        "initialMoney": {
            "amount": 5000.00,
            "currencyCode": "EUR"
        },
        "interestPaymentFreqCode": "END",
        "prolongationCode": null,
        "countryCode": "EE",
        "maturityDate": "2025-02-15",
        "returnAmount": {
            "amount": 5003.13,
            "currencyCode": "EUR"
        },
        "postingDate": "2024-11-15",
        "lastValidDate": "2024-11-16",
        "channelCode": "SYSTEM",
        "tenantCode": "MB",
        "contractHeaderId": null,
        "contractNumber": null,
        "depositClassCode": "PREMIUM_CUSTOMER",
        "payoutDetails": null,
        "personTypeCode": "P",
        "taxResidencyCountryCode": "EE",
        "taxExempt": false
    }
}

Result

As an outcome, we found the deposit offer ID ID-1696407305 and fetched related details.

Accept deposit offer

Use case

In this example, we will review how to accept a deposit offer.

Use case data

API parameters with values

We will accept the deposit offer ID-1696407305.

...v1/offers/ID-1696407305/accept

Sample API call

To accept a deposit offer, make the following API call.

deposit-api.sandbox.tuumplatform.com/api/v2/offers/{offerId}/accept

See more about the accept deposit offer endpoint in the Tuum developer portal.

Sample response

Below you find an example response body to the API call above.

Response

{
    "errors": null,
    "validationErrors": null,
    "data": {
        "offerId": "ID-1696407305",
        "personId": "ID-2660",
        "applicationId": "ID-1696407202",
        "depositGroupCode": "TIME_DEPOSIT",
        "depositTypeCode": "PREMIUM_TEST",
        "terminationType": "WITHOUT_INTEREST",
        "statusCode": "ACCEPTED",
        "reasonCode": null,
        "accountId": "ID-5334",
        "interestRate": 0.25,
        "period": 3,
        "periodTypeCode": "MONTH",
        "endDate": null,
        "initialMoney": {
            "amount": 5000.00,
            "currencyCode": "EUR"
        },
        "interestPaymentFreqCode": "END",
        "prolongationCode": null,
        "countryCode": "EE",
        "maturityDate": "2025-02-15",
        "returnAmount": {
            "amount": 5003.13,
            "currencyCode": "EUR"
        },
        "postingDate": "2024-11-15",
        "lastValidDate": "2024-11-16",
        "channelCode": "SYSTEM",
        "tenantCode": "MB",
        "contractHeaderId": null,
        "contractNumber": null,
        "depositClassCode": "PREMIUM_CUSTOMER",
        "payoutDetails": null,
        "personTypeCode": "P",
        "taxResidencyCountryCode": "EE",
        "taxExempt": false
    }
}

Result

As a result the deposit offer ID-1696407305 was accepted.

Once the deposit offer is accepted, the Tuum system automatically creates a deposit contract based on the related deposit offer.

Decline deposit offer

Use case

In this example, we will review how to decline a deposit offer.

Use case data

API parameters with values

Sample API call

deposit-api.sandbox.tuumplatform.com/api/v3/offers/{offerId}/decline

See more information about the endpoint in the Tuum developer portal.

Sample request

Below is an example request body of the API call for declining a deposit offer.

Sample response

Below you find an example response body to the API call above.

Response

Result

As a result, a deposit offer ID-1718023943 was declined.

Deposit contract management

In this block, you will find the most common use cases that explain how to manage an active deposit contract.

Below you will find the following sections:

Payments

Create outgoing payments

In this section, you will find instructions on how to create the following types of outgoing payments:

Account transactions report parameters

On this page, you will find a list of parameters included in the account transactions report. The report is available in both CSV and JSON formats, with a similar parameter structure. The key difference is that in the JSON format, the following parameters are represented as nested objects:

transactionAmount:
- amount,
- currencyCode
initialBalanceAmount:
- amount,
- currencyCode
source:
- sourceName,
- sourceRef
counterparty:
- name,
- accountNumber,
- accountNumberSubtype,
- accountNumberCountryCode,
- financialInstitutionId

Parmeter name

Type

Description

transactionId

Number, Text

Transaction ID number.

Example: ID-275388

groupId

Number

Transaction group ID.

Example: 290379

postingDate

Date

Posting date is the current Tuum banking date when the account transaction was posted to the Account API.

Date format: YYYY-MM-DD.

Example: 2029-04-01

accountId

Number, Text

The account number from where the account transactions are extracted.

Example: ID-12333

transactionTypeCode

Text, Number

The transaction type code.

Example: ACC_ADM_FE

transactionSubtypeCode

Text

Transaction subtype.

directionCode

Text

Transaction direction.

Example: OUT

initialBalanceAmount

Number

Initial balance amount.

Example: 3989.97

transactionAmount

Number

Transaction amount.

Example: 12.4

currencyCode

Text

Transaction currency.

Example: EUR

counterpartyName

Text

Transaction counterparty name.

Example: Simon Parker

counterpartyAccountNumber

Number, Text

Counterparty account number.

Example: EE871275295834652820

counterpartyAccountNumberTypeCode

Text

Counterparty account number type.

Example: IBAN

counterpartyAccountNumberSubtype

Text

Counterparty account number subtype.

counterpartyAccountNumberCountryCode

Text

Counterparty account number country code.

Example: EE

counterpartyFinancialInstitutionId

Number, Text

Counterparty financial institution ID.

Example: PARXEE22XXX

counterpartyFinancialInstitutionIdTypeCode

Text

Counterparty financial institution type.

Example: BIC

details

Text, Number

Transaction details.

Example: Account maintenance fee

metaInfo

Text, Number

Transaction meta info.

Example: {"paymentResidencyCountryCode":"LV","intrabankPaymentSource":null,"paymentMetaInfo":"[{"typeCode":"SELECTED_SCHEME","value":"SEPA_REGULAR"}]"}

merchantInfo

Text, Number

Merchant information.

endToEndId

Number

End-to-end ID.

Example: 2222223

transactionDTime

Date, Time

Transaction date and time.

Format: YYYY-MM-DDThh:mm:ss.sssZ

Example: 2025-02-28T11:23:58.16Z

paymentServiceProviderCode

Text

Payment service provider code.

Example: SEPA

labels

Text

Transaction labels.

Example: SEPA_REGULAR

referenceNumber

Number, Text

Transaction reference number.

contractSourceName

Text

Contract source name.

Example: LOAN.CONTRACT_HEADER

contractSourceRef

Number, Text

Contract source reference.

Example: ID-1718026338

contractRef

Number, Text

Contract reference.

valueDate

Date

Value date is the date on which operation actually carries out or is supposed to carry out in the account. Must be the same or earlier than the posting date.

Date format: YYYY-MM-DD.

Example: 2029-04-01

isReversed

Text

Defines if the transaction is reversed.

Example: false

reversedTransactionId

Number, Text

ID number of the reversed transaction.

filingCode

Number

Technical code assigned to the transaction record.

Example: 2029040100275388

reportDateType

Text

Account transaction report date type.

Example: POSTING_DATE

domainCode

Text

Domain code.

Example: PMNT

familyCode

Text

Transaction family code.

Example: RCDT

subfamilyCode

Text

Transaction subfamily code.

Example: FEES

sourceName

Text, Number

Transaction source name.

Example: ACCOUNT.ACCOUNT_PERIODIC_FEE

sourceRef

Text, Number

Transaction source reference.

Example: ID-78253

transactionGroupCode

Text

Transaction group code.

Example: FEE

virtualAccountId

Number, Text

Virtual account ID.

uniqueIdentifier

Number, Text

Transaction unique identifier.

Example: 1f78c038-96a6-4882-925e-ce8cd2668220

Export requested QMR as PDF

Here, you will learn how to export the requested QMR as a PDF file in Tuum.

Use case

In this use case, we will demonstrate how to download a QMR.

Use case data

API parameters with values

The fileId parameter corresponds to the sourceRef used when .

...reports/files/ID-4359

Sample API call

To export the requested report as a PDF file, use the following endpoint: storage-api.sandbox.tuumplatform.com/api/v1/reports/files/{fileId}

Learn more about the find reports file by file ID endpoint in the Tuum developer portal.

Sample request

The sample request body is as follows:

No body request.

curl -L 'https://storage-api.sandbox.tuumplatform.com/api/v1/reports/files/ID-4359' \
-H 'x-tenant-code: MB' \
-H 'Accept-Language: en' \
-H 'x-auth-token: eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJuYW1lIjoidGVzdGkgdGVzdCIsImVtcGxveWVlSWQiOiJJRC0xNDE3IiwidGVuYW50Q29kZSI6Ik1CIiwiZXhwaXJ5RFRpbWUiOiIyMDI1LTEwLTIyVDA5OjQ3OjQ2IiwiZXhwIjoxNzYxMTI2NDY2LCJyb2xlcyI6WyJBRE1JTiIsIlNZU1RFTSJdfQ.IMr4SfkQJcqPVEnmfjXcXfdvQAhOrfVFepOaiWa9Lm8'

Sample response

Below you will find the response to the API request:

Response

%PDF-1.4
%����
1 0 obj
<<
/Creator (Apache FOP Version 2.11)
/Producer (Apache FOP Version 2.11)
/CreationDate (D:20251022080154Z)
>>
endobj
2 0 obj
<<
  /N 3
  /Length 3 0 R
  /Filter /FlateDecode
>>
stream
x��gPTY��{�
�M���I��$�$9�
t7��*���""IDp��!�(*�T�idP��QDEei�1�5?��jk�l��}u�w�}u��W��!&�S`}��<_g;FpH(�`	�#X)I�~N�`5��o�~@��}�z�9RL��c3.��N4o�{�����e�V9��Ia��U�a'��Yg�&�{�2��:�*���3����j�}�W�Xb��O8r�)�f����_�Wa%�V�/-��m�����rx�6��l�?��JY}�����>����Z��	�^�Wn[9�� J�ʩ����޿r�'�*@�+���-�\��Ѐ��@�C`
,�
pn�����@H<���ݠ�RpT�:��A8��p\��=0
&L�W`��a D�� H҆!&d9B�/�C�J��C{�"����f�'�<t�	
C��Ih��#`"L��`5Xf¶�;�o���d8·�Õp|���Q���A@��a��B�"�<�ND!�рhC� �|�<�#��"H���d!��;���j�)d'�y9�\@~E�P�(m�9���Fe�
P�&T�j5�z�F��hu�)���C砋�G�����a�z��Ha�1�/L&S���\`�1����
�r�y�
l�;���.�Dq�8s�����q=���i�2^����������6�5��[��D0#�b	���3��I�G"��E�'�ӈ��'�����oI$�ɆJJ%�'5�����>�PEtE\E�"�"5"�"#"��8�*ٖ���M� �#�%ϋ�D�D�E#Dw�ֈ�]���y�%�������`(jG
��O9N�J��"��T{*����H�F���i�4WZ���#m�� N7���(Χ#�jtWz��~�>F�$!'a+���'�&1"�$)#i#ɑ,�l���$Őr���: �%�T)�%�#�!}T����M�B�%S(sV�,,�%�+�#{\vPvQN^�Y.I�J�ܼ<]�F>N�\�W~N��`��P�pI�%C�a�H`T2����.�i���C��J�JJyJ�JO���L�(�r�>�O��*�*�Uq�L��ê�Kj�jAj{պ�f�%�]ճ�[՟h�4�5�54h�5���G4�i�Z�Z1Z5Zw�am�X�#���P���q�5��!�����L��u=t�t�t_�������o���ߨ?a@1p3�3�1��PːeXc�`=i��������iq��=4�{�5�3�bbj�3i3�3U1
7�5gҘ��b�
3���Y�����&��g���б��h��ݠ����qÔ��e�e�%ߊanůo�ha�`��Fنm�d3c�ig{�����Ϯ�n���~��e���C�Ð#�1���񙓒S�S�ӂ��s��e�����qW9W�k�낛���~w���{��s-�G�'���y���FՍ܍]^�����Sou�d�_|�>�>5>/|
|���Q���������/��H�$�6.9����w���
�ń�6�.nr�th�t�qXA��f�͙�on�ޒ���V�ֈ���Q�A�-�#�""#]#k#X��ìWlv9{�c�)��DYF�E�F[F�������������}�W��2~%!(�=��x�K��s���o��6���T��O6O>���s�5�@)�S�Si���4����&ӭ�k�?df����ffie�˚�v�>���a��mWܾ{����;���;�r�s�s�w9�:��;~��<����w{�������ʟ������^��^��u�#���~h��}U���o�U}.f������V�G�*1)9Z�.喎�>p�L�,�l����rFya��C[ݬ0��;�?�v�_�Q�]�RUZ��:�z�Ʈ��V�v_������6G�����>�=��޹��A���8�x�����'�'�����������=��l���"�R�
���Ν;}�G���t�����Eg���3/
�i��پs�sm?��\�A�(�:�:�b���!�������X�t������j.�_,������\ʾ�x9�����+S}[�&�_}���?t��ڍ�Nׯ�\�ay��M��o1ou�6��9h<�q��Nǐ�P�]ӻ�����o���r�����n�n{86��~8�(�ћ�鏗'v=A=)|*���쳆_5m��/N:L>�{>1Śz�[�o���_�^T�(�4��^�s���r���WI���~���������cp!xa�
��ʟ�o�ޞ|g��o�{������K��>����8�)���r�g���/�_z��}����"t�]@�B����. t�]@�B�����]`�?�j ������q��jԢ ��r2S��mֶ�,^ltL�:FZ
���p�k�5&
endstream
endobj
3 0 obj
2472
endobj
4 0 obj
[/ICCBased 2 0 R]
endobj
5 0 obj
<<
  /Type /Metadata
  /Subtype /XML
  /Length 6 0 R
>>
stream
<?xpacket begin="" id="W5M0MpCehiHzreSzNTczkc9d"?><x:xmpmeta xmlns:x="adobe:ns:meta/">
    <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:Description xmlns:dc="http://purl.org/dc/elements/1.1/" rdf:about="">
            <dc:format>application/pdf</dc:format>
            <dc:language>x-unknown</dc:language>
            <dc:date>2025-10-22T08:01:54Z</dc:date>
        </rdf:Description>
        <rdf:Description xmlns:pdf="http://ns.adobe.com/pdf/1.3/" rdf:about="">
            <pdf:Producer>Apache FOP Version 2.11</pdf:Producer>
            <pdf:PDFVersion>1.4</pdf:PDFVersion>
        </rdf:Description>
        <rdf:Description xmlns:xmp="http://ns.adobe.com/xap/1.0/" rdf:about="">
            <xmp:CreatorTool>Apache FOP Version 2.11</xmp:CreatorTool>
            <xmp:MetadataDate>2025-10-22T08:01:54Z</xmp:MetadataDate>
            <xmp:CreateDate>2025-10-22T08:01:54Z</xmp:CreateDate>
        </rdf:Description>
    </rdf:RDF>
</x:xmpmeta><?xpacket end="r"?>

endstream
endobj
6 0 obj
1004
endobj
7 0 obj
<< /S /D >>
endobj
8 0 obj
<< /Length 9 0 R /Filter /FlateDecode >>
stream
x���w�D���+�q�x�f&�$�m[W���Z�A}`K��\�z��!�vvfځ1��۞���{?½�qDI,~�rQ�4*���܍>��S(I9�x�Kֽ)?�G1�J��67�߈Ż���Q�4�yAƭ���x��1�,�h��$M���YT��YNƌ���X���FY�����#��(-�Dܑ��h�yT$9�4OII�(fO�<���'�x���K�&,�%+˄rq㧟p1��~-�QGy���b};��w����7��q�F)�]\�^}�����1�c��H"�ߑ__��RFID���_���+q��x{\�m�~o^�N�������h^G�r�w���LL�}x*_��ޛw�_��v��%U��j�9a"x�8���Wh,��{����I)����.�K���{_�?'T��Y���}M"��=�p,WƑ��ݚ;y���B@£<�˒+������Z���x����J��M�N�˵ێ|�[��V�����9Z��iv���YT��@灟|V�x�x�q+��'w��r3�]ڽ>����ǣ@ć�x�fųCt��a�v\珸��O��4�=�_G�r���V�i�&����������Q;�eT�Ԃ���$�Y3Śx�iY>�����Tek���l=�
�>aK�)�~^Q��$� �(�+SӮ��}jz��;eJE��'�!񈢤2d�B	S\K�מrLǭ>h��7�I���r�:��j%qǽ��T�im�'yI<2�L��pH�Q�O�W��E���F����f6�T���Ba������d����Z�Y:�XK�~^-��*�'�):{����3%yx�8��������bx��ݙ�/Vw�f;�!�/�?��L*��@���~�U!���������8mAy�=߂Xۂ��jM.ě��yE�[-�W�ͶZ�������l��֓�<��y�p����r�$3@�$%NA{R����I�����I_/���&�[�y���C)��>��D�B�Y��!3B�!%PA����g�!����QmAˉl�,�/��l�$�[q]kE졪yD���An�,�)y
[�z��E�\�բ�}��̧Y}�R#3(l1��֨Anjd&j��)l5J�n
5����\��B�~��h�|FĂՋ�^��"���ޒ�(��yDk��s5�\?X�`��$*lO�А
O�f��|�/�S�]W��$-�:�4d�%�c �8Zm=���	��-0�)�
[�r�^C��	猓����yD��>DA ��C43A0!%Oa���of�	����i} Q�<b8��q%��\�L\I�SЮ�b�bÕ�����С�y�p�Y�A �ɇ,�)y
ۇ��C�\s��}�P�<b8E��"�ܴ�L�H�S�Z���Z��5�ٷ���c �S�5A �M��A��<��F���F�\c=���}�z�ԋ�^�F�-PD����Ըƒ@r�$3A�$%Oa[GO6,��kl����>�Ru�i��
��@�q��z`0��[`%RB�h��u��-pC1��ἵot� ��Cf�`BJ��6�$F�5LH�k��[�J�1étWA �͕,�+)y
ە(:��J�\s�}�P�<b8լ�!��|�L|H�S�>���>��5�ط`E�c �S�-A �M��A��<��E)���E�\s΁}�P�<b8��Q#����L�H�S�j��w
5�����ؗ��[$�"���}Q�<b85��$��,�L,I�SؖT�'���56��Á���+��30���㌵��>`L'ط�J��*l%*�z
%�&�3�[��b�1�yk��An'�����<mB)E�5LH�k��[�J�1étWA �͕,�+)y
ە:��J�\s�}�P�<b8լ�!��|�L|H�S�>���>��5�ط`E�c �S�-A �M��A��<��E���"}�9���(l1��֨Anjd&j��)l5��w
5������O#V/�z�������q1��XAn�d&���)lK*ѓ
K���q؋�\N63��|��~����V?�f*��@�q��zb0�L�[`'RB�e1z��D݄sƉ}�P�<�����V�@2��OY R�
1�]C�����Ⱦ�(u��R��(
� ���,�+)y
ەR�bÕ����#�С�y�p�Y�C ���� �����}(C6|H�k�5�o����@��5Z�@���	�)y
[�rt\C����#����y�p
[�F ���� �����ը@�5�H�klG�弾֗��rL�4�o����@�����Ar��6#/R��]��''��u5�s��g)�=q\�93������^n�xh��0%a�
C4L�hME{g���WO�3v�N�Ƿ���7 9���@J�*l%J�
%�'����u�XT�'[��<�4���cM�w�� ���cA�H�S�R��	R��5��zI#��p��n�+qi{�^�K��j:7ِ9�2����w[5`L'�j�`GJ�¶#�>h�Q7���-pC1����ot� ��Df�`BJ��6���0!}�����@��y�p*]�J ���� �����])��{m�J
��PJ�����D1�o����v�A�G:��s��ڂJ��G��x(�נ6.���4��j�!��uؒ�t����X�xV���)��]5%y�E��5�������#
endstream
endobj
9 0 obj
2788
endobj
10 0 obj
<<
  /Resources 11 0 R
  /Type /Page
  /MediaBox [0 0 595.275 841.889]
  /CropBox [0 0 595.275 841.889]
  /BleedBox [0 0 595.275 841.889]
  /TrimBox [0 0 595.275 841.889]
  /Parent 12 0 R
  /Contents 8 0 R
>>
endobj
13 0 obj
<< /Length 14 0 R /Filter /FlateDecode >>
stream
x��Qs�F���+�2���\�N�I�i��M/�^`��j%�H�������|l�b����$G�x���ӄ3W�L�I�q'#6[N>��s&BGz���Q�h����O�}�o����#����}\'p� d��e�Ő;��%�^8\
WzR��pBD��T�|�|�������^��+�&�p�0����-&S��PJ��c��+|%� �o�O��a�F̓�ᑈ"ɕ���.&���'i��N�����o&��kp�k���[����co'�\N^}�3�����S�����/�/~}�WIW��_�d�ŷ�"{�~?�����}���a�������:JG�K�b�4�]���Y����Я�r���"e�����Ո����-�-ˋ�#STI��t}��ɟ�%���!��ݮ/�����Ń���h<��rU������>�'o]�b���}}+�]��B����o5��%*�T�V��߱6�.���U���q��?N�{{�f�:���*���yv;O�/ɍ�^ù�BDNp��-��v��+s��UzQ��B4�|�����B-�Z{V
�6
A%��B�=��5�sƑ�a ��t��a�1a���g�$/w���������/�����/�(\u+�E�T�o�n�6�*Nm!�����]�=��0��ap;y���H'���R���e��u�V)F�h����Ҳ�0�@�(=���R�dP%ɡJP����v�ʴ"���;�}��DYL�b����5QxD�Y,İ⮴&`�:�&
F�&#T��&/�5��{����	��Z���\����[&i�.V��n��O*6d��B��e�.�q��g����I;Q �Dԇ�B�N*�%(���Q+��P$(R�K�a�W�d��g�]:�͜k�)Q�C�Y,İ>��z��Q�(���P�ڌ�f3jkF�nF�m�f����[����J�o�M��/��5{�^͒�&�>�N*z1��+�	�܉���ը�)Bg7ܩ�;ɚ;m[�g�qzc>�]��<��B+�J?F��?�`?2B5j?����ւ�b��H8��V�U�{G਋/�Q8�*��*	4qC�z%�B!b�b!�s�.�#pԅ.Q8�.��.yh�.u:R�(F
�(&��x�侑H@"�,bX�W�8G]��#����q����o��cG����_�/Y���{�D.�����l�L%#Z����%�c��C�Y,İ>�W���Q��(���T�ێ"�vÎ�ݸ$,�{1�ܫ�	��.�����Hը�)���'������� ��l�X�ae[�H�u�H$��HF���HM�p�>� ���X�aE\�J�u�J��JF�ƭJ]�P��� Q���X�a�\�K�u�K��KF�ƭK>z��K� �����Nd1��}���D�Y,İ�2'p��0'
G0'#U�6�}�0���Ն����&�\-��vD��f�����1���lL�%#Z㶥]ް%�c��C�Y,İ�T���Qǒ(���T�ڎ���n�ѳC��%r�b!��{�?�#pԅ?�8�?��?q4}ßzC����b!��m�#�#pԅ#Q8�#��#ItzÑ�C�D "�b!�q�*�#pԅ*Q8�*��*�h�*�=��BĜ�B+�*]G�]�p]2R5n]R��.u:��W�!�9���b���� �ĳX�a%^eN�uaN�`NF��mN!��aN��:�k�}=����l�^�������H�!�,��]O�7 D���P������<h���S���T�8z��8]|󿲝8cW��<M�q�V٧�x�%���C�Yg�����a?"`?F>�i?�C2:�>G�5ԇ�U��	{�or�S����b!�v"�nC"nc�ncp�i�Mk��L�����z���]-V�������b!zW"XCu(D@u�|�����M�C{3L��	,ᰟ��,.Ob���x�&���n��Ǣ��"����X���D�ְ
�#gk?��(�(�~Zۏ���h�Y��8{��P@D�Y,D��"@k������ϡ�h]���v�ٺ���Ԧe�H8����y@�`
��1�q��s��'B�2��B�2�3$��B��6 D���P���������Ѵ��޴L��f�}��M�!�1�q��s�i�hZ��>u��N]}�g����Eo2�J���t��n�N�?���]�@�`
�2�q�:$�됇.f�PkRN1��F $1���X�޵D���
�#g�=��	/��o�!q�$�X���D��p
p#p��hT���o�`�`�X��UD��P
P#g�:'�y"�-�tZ��
�g���Po4���]q@�`
š�1�q��#�*�rѯ�i�8a�A����C�Y,D��"@DSxHD@x�|���8}�Z�a<OߚC�If���
���6"�6F>�6��h;��Xo�!a�`�X��UD��P
P#g�:�[s��&d�N��VQyު�AvH`"�,�w �5\�B\���ٺ?�Bڔ�B&�#V��[�vX��P(�.���u�^'Y<_�nT&�H�X�^�Z�.�mF��$ �HH}X-�J�(0A��h�S�(��U/�KV�FiHV�N�/�+;՚u5϶�	;mZ���\?9V^�8G-8�̊���H�8ͪա��E36ݪ*��M�������j�[���ڮR��#;�h�{�n�uV?�w�	M$���v�)�s��.e@�=���{��V�����Kjko�T�o���GU�
��bw����
��ã �)����W!f
endstream
endobj
14 0 obj
2844
endobj
15 0 obj
<<
  /Resources 11 0 R
  /Type /Page
  /MediaBox [0 0 595.275 841.889]
  /CropBox [0 0 595.275 841.889]
  /BleedBox [0 0 595.275 841.889]
  /TrimBox [0 0 595.275 841.889]
  /Parent 12 0 R
  /Contents 13 0 R
>>
endobj
16 0 obj
<< /Length 17 0 R /Filter /FlateDecode >>
stream
x��[O�0���)��|�<n�����]�S/P*�}�ٹ4I����E��4��c����R;/E�m��2�bc,���,�"f0
I��e�,�$�%"��<,��3��ee�DS��Aqi�~�P��Њ1��1�p��7E	�Fi��F1��y�	�2Ǒ4�!RQ�S��+��(��k���R�	���}��+M�1�"���Y˩r��+E���h�{��d6��=Dw����O.��+�	t}�E��JD	A�?��cF4fq�>Fwg���K�{�}>G���Eg�ER���{Ի�.z��b��3oe)5��ij�2N�$�F�(�5�Vդ��P�C��|���G��I�䒅�Ob�׳d����v��є_�-Kӓ��&����JUJ6�uťۧT�־�5SmRr}*�Iڱ��_���"��.�-����~ƶ�����r��D	O)gݾ==�|֟�����Dq��[M�0-:�nrn$!�&�d��k���j�z]��f�hG��j
�G�چ#��GV�#������T@�#�h8��s���mEB:�&-sG";jү��S%/�\WYP�EHY��Z�ք@זsJF�G�͒DK���M�XCH+�I���Qsq�z��x>����W|�:t�qž\]F�Q*��k�@����$R�D�$H�m%���"L���l���T|�:t�qŶ\"F�Q)#�H�P��D$H�m%���j��i4Do��h8WI!�Ax����r�F-���@%�Bu�*IqPI��F�tZ�k�ҫc�u6�
�;uQq�:tġ4�QF�QF�؍�($PF�X��2j�7�c��P[T ��}�D1�>y�<o
b��8���^��
0��0��8�p������U�����n�G[���B���֡#5�m�90�Z�9.#PG�P��:�&v�<��ڷ� �u��n��o�p����@&�Ru�2���n�I�Z�D��q��m�&�8jgSI �j�:m�$`~w�PZ��b�y���~>�������erA�B\;��B�C���<���?�
A���^��Q9VnE_�y'�"��\�������HL��4�����ؚ
endstream
endobj
17 0 obj
1117
endobj
18 0 obj
<<
  /Resources 11 0 R
  /Type /Page
  /MediaBox [0 0 595.275 841.889]
  /CropBox [0 0 595.275 841.889]
  /BleedBox [0 0 595.275 841.889]
  /TrimBox [0 0 595.275 841.889]
  /Parent 12 0 R
  /Contents 16 0 R
>>
endobj
19 0 obj
<<
  /Type /Font
  /Subtype /Type1
  /BaseFont /Times-Bold
  /Encoding /WinAnsiEncoding
>>
endobj
20 0 obj
<<
  /Type /Font
  /Subtype /Type1
  /BaseFont /Times-Roman
  /Encoding /WinAnsiEncoding
>>
endobj
12 0 obj
<< /Type /Pages
/Count 3
/Kids [10 0 R 15 0 R 18 0 R ] >>
endobj
21 0 obj
<<
  /Type /Catalog
  /Pages 12 0 R
  /Lang (x-unknown)
  /Metadata 5 0 R
  /PageLabels 22 0 R
>>
endobj
11 0 obj
<<
  /Font << /F7 19 0 R /F5 20 0 R >>
  /ProcSet [/PDF /ImageB /ImageC /Text]
  /ColorSpace << /DefaultRGB 4 0 R >>
>>
endobj
22 0 obj
<< /Nums [0 7 0 R] >>
endobj
xref
0 23
0000000000 65535 f 
0000000015 00000 n 
0000000141 00000 n 
0000002698 00000 n 
0000002718 00000 n 
0000002751 00000 n 
0000003844 00000 n 
0000003864 00000 n 
0000003891 00000 n 
0000006753 00000 n 
0000006773 00000 n 
0000012008 00000 n 
0000011820 00000 n 
0000006998 00000 n 
0000009918 00000 n 
0000009939 00000 n 
0000010165 00000 n 
0000011358 00000 n 
0000011379 00000 n 
0000011605 00000 n 
0000011712 00000 n 
0000011894 00000 n 
0000012144 00000 n 
trailer
<<
  /Root 21 0 R
  /Info 1 0 R
  /ID [<73B0A27EF403BFFD8616203D63F89511> <73B0A27EF403BFFD8616203D63F89511>]
  /Size 23
>>
startxref
12182
%%EOF

The response may appear as raw code. To view it as a PDF, save the response as a PDF file or use a download tool, then open it with a PDF viewer.

Result

As a result, the requested QMR was downloaded.