ISECure WS Channel API API Reference

The API provides secure file exchange with all common banks in Finland via SEPA WebServices channel on the API side towards the banks, including certificate enrollment (PKI) with automatic renewals.

The API specification in OpenAPI v2 format can be found on GitHub isecurefi/wsapi-v2. Command line CLI and beefed-up PHP SDK are also available on GitHub isecurefi/wscli-php.

API provides simple role based access control (RBAC) and user account management, password recovery, and SMS based Multi Factor Authentication based on AWS Cognito Your User Pool managed service.

NOTE: The API endpoint for production is the same as for test, but without test. in the URL. Production and test APIs are deployd on separate AWS accounts.

NOTE: The API is run on AWS API Gateway and with AWS Lambda backend. When Lambda functions are cold, there is a small delay in response time. Additionally, banks have considerable delays in their processings, especially with certificate enrollments.

Service enrollment

Every integrator (partner) has own API Key and every user account belongs to one integrator. API Key is bound with service subscription. In other words, enrolling fresh API Key requires service agreement before file transfers are allowed on production accounts.

If user registers with 0 API Key (i.e. no API Key) she gets a fresh API Key and becomes the API Key owner. The API Key owner account can list all users under the same API Key, see the Integrator API. Integrators (partners) registers their own API Key owner accounts and use it to register their client accounts.

NOTE: API call rate limits are set and tracked per API Key by AWS API Gateway.

Account management

A user (email address) can register either admin or data or both roles. The role in the API is referred to as mode. Both modes have separate passwords and provide differing capabilities for the user.

Login always requires account mode parameter in addition to user's email address and password. Admin mode login always requires an additional SMS one-time-password (MFA), whilst with data mode password is enough (suitable for automation). Admin mode is used to configure the account (e.g. adding PGP keys and sharing certs) and data mode to exchange files. Listing files is allowed on both modes.

NOTE: Integrator (partner) registers her customers by using her API Key from the API Key owner account.

Bank certificate enrollment

The SEPA WebServices connection to the bank requires enrolling PKI certificate with the bank. The Admin mode can enroll certificates for different banks, but only one certificate per bank. The corresponding private key is stored encrypted with AWS KMS service.

Bank certificate sharing

It is possible to share the same bank certificate with multiple accounts. Certificate sharing between accounts can be configured when accounts have the same API Key. Account that holds the certificate can share/unshare it with another account ( admin mode operation). Note that only the account that has the certificate can PGP export the certificate and corresponding private key. This allows creating e.g. one admin mode only account and multiple data mode only accounts, where the admin account shares its certificates with other data accounts.

An account can never have multiple certificates per bank, be it shared or account's enrolled certificate. This is because the API requires identification of the bank, but not the certificate and private key pair.

Access security

Access is secured with TLS on Amazon Web Services (AWS) API Gateway. Inside TLS, secure sessions are established by using email address as username and by RSA encrypting password along with dynamic username specific parameters fetched from the API with InitRegister or InitLogin API commands (challenge response).

Successful login provides a session token (AWS Cognito User Pool). Authorization happens with the session token (Authorization) and API Key (x-api-key) headers.

Administrative actions require SMS based MFA authentication (see admin mode). User account management is handled with AWS Cognito User Pools and each user (email) has separate admin and/or data mode (role) accounts sharing the same API account data.

API Endpoint
https://ws-api.test.isecure.fi/v2
Terms of Service: https://www.isecure.fi/ws-api-terms
Contact: dan.forsberg@isecure.fi
Schemes: https
Version: v2.4.0

Authentication

Authorizer

description

Successful login provides IdToken that must be provided in the Authorizer header

in
header
name
Authorization

X-Api-Key

description

Integrator specific API Key. For all integrator customers, the API key must be the same.

in
header
name
x-api-key

Account

InitRegister

GET /account/{Email}/{Mode}

Before register (or login), client must fetch challenge from the API. Then on register (or login), the challenge must be passed along to the API (as response to the challenge). The challenge is always fresh for some period of time and the API validates it when passed with register (or login). The challenge has form of base64-string|timestamp|uuid. For example:

ezwXceQ63fV9oWTSJBAE2Zq1Cw5tBIJe+7+Rl8jrgbk=|1475429754114|4017bda8-0a15-4154-a8b7-88069b05cb4e

NOTE: The call must contain the same email as used for registration itself.

Email

Email address as the account username, e.g. dan.forsberg@isecure.fi

type
string
in
path
Mode

Administer account with admin mode, exchange files with data mode

type
string admin, data
in
path

Operation succesfully processed. See response.

400 Bad Request

Request validation error

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "Challenge": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

VerifyEmail

POST /account/{Email}/{Mode}

Provide Code received to Email address for email address verification. Provide also AccessToken received during login.

NOTE: Phone and EMail verification can be bypassed per API key on request to dan.forsberg@isecure.fi. E.g. if integrator verifies EMail and Phone beforehand.

Account parameters

Email

Email address as the account username, e.g. dan.forsberg@isecure.fi

type
string
in
path
Mode

Administer account with admin mode, exchange files with data mode

type
string admin, data
in
path
Request Content-Types: application/json
Request Example
{
  "AccessToken": "...",
  "Code": "123456"
}
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

Register

PUT /account/{Email}/{Mode}

You need to register both admin and data accounts with the same email address. Both accounts share the same data, but are used for different purposes. Admin account must be registered first, then data account.

Admin account is used to configure setup with Certs and Pgp operations, while the data account is used with Files operations only. Both accounts use Account and Session operations.

Admin account always requires SMS MFA during login, whilst data account does not. Generally, the data account is considered read-noly when no PGP keys are configured, since PGP Keys are used to verify file upload signatures and are thus required to successfully upload files with Files UploadFile operation.

Registrations are independent for both accounts, admin and data and both require phone number and email verifications.

email is the login username for both accounts and mode defines the selected "mode" for the login, i.e. admin or data.

Before registration client must fetch challenge from API (see Account InitRegister operation) and pass it back within the ChResp parameter.

The following parameters name, phone, and company are required and must be valid (phone, email) as they need to be confirmed before registration becomes successful and login possible.

Client must RSA encrypt (OAEP padding) the password and the challenge timestamp as string in the form password||timestamp, base64 encode it and provide the resulting string as Encrypted parameter. The RSA encryption can be done e.g. for illustration purposes within command line with openssl rsautl:

echo -n 'Toddler_..123456789012345||1475175151231' |
    openssl rsautl -oaep -encrypt -pubin -inkey server_rsa_public_key.pem |
    base64

The test API's RSA public key is as follows:

-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkuSaoSZztGAIGDTY7Rff
psBHJJT1k207UodOJbYFhHAq0lWJnvMPLl5Q1DUUZdTGtTdL8Dsaj/Bo2+gSykMM
R5QiKewvQsLfvqjwOO8JDItnhJl0lUqcPpdQV4M/Ai3YNRjNcVy4a+pichqtSAWl
9S1HV01MNeouk8PEr/zoUasmgfO3mz6N6XTUtF/tIi8K2kBOsLAtqltihFSd/zT8
ifYZE9cZTJ09lUs7kMz1wxFIsiegaE1jUYV+VSLu3PJ97oKhQpqop8EnkBAoBl6r
mdmFryBQIdakPIdd4rO5Yg+to10n4u7Wij9ePIwWMfbqY4QoW5nXqMgFJQkIt4TG
eQIDAQAB
-----END PUBLIC KEY-----

The production API's RSA public key is as follows:

-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA7wx4l7P3eLsaEyK7ZRME
g5urEHwaEoY9LjkYcpMw9gmPIi3RoGjQX7HzPad2D7ES2yIGdmyxjN8R2LyFa8ke
EE+VY3ISYzP2cOjd/zDkX01yjDXQLRxntXbtqIypGQAzmZbCyIB226ZKEE+ldh6M
YyM41YWYikfocYssFEjY7fpPGeUg4FOmHmyWIZeMkXYovskoi1jZ1Ay1qn95XlpA
/Ptru2efro4T1xksv4WBBrj8bMNwdDpf4oyzH2PKYkn3/KlNTBCHlAmzP0jd4pIa
N0tAf2m8TcNq7kuBzyfs8AcCUj870p8SEiko0PMx6K+zVsTVWsxfUX+/+kmapmp/
AwIDAQAB
-----END PUBLIC KEY-----

NOTE: Password must be at least 20 characters long, have lower and upper case letters, numbers, and special characters. NOTE: Phone number must be provided with country code, e.g. +358404982201.

Account parameters

Email

Email address as the account username, e.g. dan.forsberg@isecure.fi

type
string
in
path
Mode

Administer account with admin mode, exchange files with data mode

type
string admin, data
in
path
Request Content-Types: application/json
Request Example
{
  "ApiKey": "hzYAVO9Sg98nsNh81M84O2kyXVy6K1xwHD8",
  "ChResp": "ezwXceQ63fV9oWTSJBAE2Zq1Cw5tBIJe+7+Rl8jrgbk=|1475429754114|4017bda8-0a15-4154-a8b7-88069b05cb4e",
  "Company": "ISECure Oy",
  "Encrypted": "...",
  "Name": "Dan Forsberg",
  "Phone": "+358404835507"
}
201 Created

Operation succesfully processed. Resource created. See response.

400 Bad Request

Request validation error

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (201 Created)
{
  "ApiKey": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

InitPasswordReset

GET /account/{Email}/{Mode}/password

Start password reset by getting confirmation SMS code.

Email

Email address as the account username, e.g. dan.forsberg@isecure.fi

type
string
in
path
Mode

Administer account with admin mode, exchange files with data mode

type
string admin, data
in
path
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

PasswordReset

POST /account/{Email}/{Mode}/password

Set new password for user with Email. Provide received SMS Code.

NOTE: the password must be encrypted, see Register for more details.

Account parameters

Email

Email address as the account username, e.g. dan.forsberg@isecure.fi

type
string
in
path
Mode

Administer account with admin mode, exchange files with data mode

type
string admin, data
in
path
Request Content-Types: application/json
Request Example
{
  "ChResp": "ezwXceQ63fV9oWTSJBAE2Zq1Cw5tBIJe+7+Rl8jrgbk=|1475429754114|4017bda8-0a15-4154-a8b7-88069b05cb4e",
  "Code": "123456",
  "Encrypted": "..."
}
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

VerifyPhone

POST /account/{Email}/{Mode}/{Phone}

Confirm phone number for Email Mode user, with Code received via SMS.

NOTE: Phone and EMail verification can be bypassed per API key on request to dan.forsberg@isecure.fi. E.g. if integrator verifies EMail and Phone beforehand.

Account parameters

Email

Email address as the account username, e.g. dan.forsberg@isecure.fi

type
string
in
path
Mode

Administer account with admin mode, exchange files with data mode

type
string admin, data
in
path
Phone

Phone number with country code, e.g. +358401234567

type
string
in
path
Request Content-Types: application/json
Request Example
{
  "Code": "123456"
}
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

Certs

ListCerts

GET /certs/

List certs from all banks

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "Certs": [
    {
      "CertName": "osuuspankki_customer_signing_cert",
      "Expires": "Oct 28 06:30:08 2017 GMT",
      "Issuer": "CUSTOMER TEST OP-Pohjola WS CA",
      "PEM": "-----BEGIN CERTIFICATE-----\nMIIF+DCCA+CgAwIBAgIDEaBdMA0GCS...x0t6Cnd5lyGKg=\n-----END CERTIFICATE-----",
      "Serial": "11A05D",
      "Subject": "1000038023"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

ConfigCerts

POST /certs/

Configure certificate usage parameters. Currently, only settable (permanent) parameter is export. Set it to disabled for disallowing private key export.

NOTE: When export is disabled it is permanent, it can not be re-enabled through the API (safety feature).

Certs handling settings

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Request Content-Types: application/json
Request Example
{
  "Export": "disabled"
}
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

UnshareCerts

DELETE /certs/shared/{ExtEmail}

Unshare certs with an existing ExtEmail account.

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
ExtEmail

Unshare certs with ExtEMail account.

type
string
in
path

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "ResponseCode": "string",
  "ResponseText": "string",
  "SharedFrom": [
    "string"
  ],
  "SharedTo": [
    "string"
  ]
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

ShareCerts

PUT /certs/shared/{ExtEmail}

Share certs with an existing account ExtEmail under the same API Key.

If the ExtEmail account does not have the specific bank certificate (key pair), then certs (key pair) from this account will be used (shared), if any. Both accounts must be registered and using the same integrator API Key.

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
ExtEmail

Share certs with ExtEMail account.

type
string
in
path
201 Created

Operation succesfully processed. Resource created. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (201 Created)
{
  "ResponseCode": "string",
  "ResponseText": "string",
  "SharedFrom": [
    "string"
  ],
  "SharedTo": [
    "string"
  ]
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

ExportCert

GET /certs/{Bank}

Download bank certificate and private key encrypted with stored PGP key.

NOTE: The previously uploaded PgpKeyId must have purpose type export. I.e. purpose type authorize PGP keys can not be used for exporting.

NOTE: If export has been set to disabled (see ConfigCerts), then exporting private keys is not possible through API.

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Bank

Bank used for this operation, can have values of nordea, osuuspankki, danskebank, aktia, sp, shb, pop, spankki, or alandsbanken.

type
string
in
path
PgpKeyId

Short version of a PGP Key id idenfiying the exported Private Key, e.g. 3A3A59B2

type
string
in
query

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "CertsAndKeys": [
    {
      "Certificate": "string",
      "EncryptedPrivateKey": "string"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

EnrollCert

POST /certs/{Bank}

Provide WS-Channel user id, WsUserId, Company, and PIN Code for Bank certificate enrollment. Company must match with the contract with the bank and is part of enrollment process. Note that certificate private key is securely generated and stored encrypted with AWS KMS encrypted authentication on API side. Certificates are automatically renewed when needed.

NOTE: For OP bank, ensure that you set the PIN code blocks 1 and 2 in correct order. If not initially in correct order, bank will lock the registration and you need to call them for unlock.

Certs parameters

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Bank

Bank used for this operation, can have values of nordea, osuuspankki, danskebank, aktia, sp, shb, pop, spankki, or alandsbanken.

type
string
in
path
Request Content-Types: application/json
Request Example
{
  "Code": "8642603384107437",
  "Company": "ISECURE OY",
  "WsUserId": "..."
}
201 Created

Operation succesfully processed. Resource created. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (201 Created)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

ImportCert

PUT /certs/{Bank}

Provide WsUserId, Company, PrivateKey, and Certificate for importing existing WS Channel certificate and private key. Company must match with the contract with the bank. Certificate(s) and private key(s) must be PEM formatted.

NOTE: EncCcertificate and EncPrivatekey are for DanskeBank only.

Certs parameters

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Bank

Bank used for this operation, can have values of nordea, osuuspankki, danskebank, aktia, sp, shb, pop, spankki, or alandsbanken.

type
string
in
path
Request Content-Types: application/json
Request Example
{
  "Certificate": "...",
  "Company": "ISECURE OY",
  "EncCertificate": "...",
  "EncPrivatekey": "...",
  "PrivateKey": "...",
  "WsUserId": "..."
}
201 Created

Operation succesfully processed. Resource created. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (201 Created)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

Files

ListFiles

GET /files/{Bank}

Asks bank to list downloadable files matching filters. Status can be e.g. NEW, ALL, or DLD. Filetype is bank specific (ALL is not accepted), see bank specification. Bank is the name of the bank. Returns a list of FileDescriptors.

NOTE: Certificate must be enrolled before files can be listed, downloaded or uploaded.

NOTE: The uploaded files do not show up on the file listing.

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Bank

Bank used for this operation, can have values of nordea, osuuspankki, danskebank, aktia, sp, shb, pop, spankki, alandsbanken or SEB.

type
string
in
path
Status

Status of the file, e.g. ALL. NEW, DLD

type
string
in
query
FileType

Bank specific FileType identifies the file type to be listed

type
string
in
query
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "FileDescriptors": [
    {
      "FileReference": "227166",
      "FileTimestamp": "2017-05-20T03:36:21.148+03:00",
      "FileType": "VA",
      "ServiceId": "N/A",
      "Status": "NEW",
      "TargetId": "MLP"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

UploadFile

PUT /files/{Bank}

Uploads file to bank if PGP signature(s) are valid. FileContents is a Base64 encoded string parameter. FileType is bank specific. Signature is detached PGP signature or concatenation of PGP detached signatures in ASCII armor format. PGP signatures are used for authorizing file uploads. Currently one valid PGP authorize registered key signature is enough. FileName is upload filename.

Files parameters

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Bank

Bank used for this operation, can have values of nordea, osuuspankki, danskebank, aktia, sp, shb, pop, spankki, alandsbanken or SEB.

type
string
in
path
Request Content-Types: application/json
Request Example
{
  "FileContents": "...",
  "FileName": "testfile",
  "FileType": "KTL",
  "Signature": "string"
}
201 Created

Operation succesfully processed. Resource created. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (201 Created)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

DeleteFile

DELETE /files/{Bank}/{FileType}/{FileReference}

Deletes file on bank side. File is identified with filereference.

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Bank

Bank used for this operation, can have values of nordea, osuuspankki, danskebank, aktia, sp, shb, pop, spankki, alandsbanken or SEB.

type
string
in
path
FileType

File reference id from list files

type
string
in
path
FileReference

File reference id from list files

type
string
in
path
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

DownloadFile

GET /files/{Bank}/{FileType}/{FileReference}

Downloads file identified with filereference, filetype, and bank. Filereference is received in file list from bank. Returns base64 encoded file content.

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Bank

Bank used for this operation, can have values of nordea, osuuspankki, danskebank, aktia, sp, shb, pop, spankki, alandsbanken or SEB.

type
string
in
path
FileType

File type from list files

type
string
in
path
FileReference

File reference identifier from list files

type
string
in
path

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "Content": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

Integrator

ListAccounts

GET /integrator/accounts

List accounts registered under the integrator's API key. Account that created the API key is authorized to call this.

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "Accounts": [
    {
      "AdminMode": "registered",
      "DataMode": "unregistered",
      "Email": "dan.forsberg@isecure.fi",
      "Name": "Dan Forsberg",
      "Phone": "+358404835507",
      "export": "allowed"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

Pgp

Pgp

DeleteKey

DELETE /pgp

Delete PGP key.

Pgp parameters

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Request Content-Types: application/json
Request Example
{
  "PgpKeyId": "DBCBE671"
}
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "PgpKeys": [
    {
      "PgpKeyId": "3A3A59B2",
      "PgpKeyPurpose": "authorize"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Pgp

ListKeys

GET /pgp

List PGP keys.

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "PgpKeys": [
    {
      "PgpKeyId": "3A3A59B2",
      "PgpKeyPurpose": "authorize"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Pgp

UploadKey

PUT /pgp

Upload PGP key.

ASCII armored PGP Key in PgpKey and key purpose, i.e. export (exporting cert private key) or authorize (upload content authorization verification) in PgpKeyPurpose.

NOTE: The same PGP key can not be used for both export and authorize purpose at the same time.

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Request Content-Types: application/json
Request Example
{
  "PgpKey": "...",
  "PgpKeyPurpose": "authorize"
}
201 Created

Operation succesfully processed. Resource created. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (201 Created)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

Session

Logout

DELETE /session/{Email}/{Mode}

Logout user.

NOTE: AWS Cognito allows user logout, but the received authorization IdToken is still valid. AWS hopefully fixes this soon.

Authorization

Use IdToken from the Login response as the Authorization header

type
string
in
header
Email

Email address as the account username, e.g. dan.forsberg@isecure.fi

type
string
in
path
Mode

Administer account with admin mode, exchange files with data mode

type
string admin, data
in
path
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

401 Unauthorized

Unauthorized

403 Forbidden

Unauthenticated

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (401 Unauthorized)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (403 Forbidden)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

InitLogin

GET /session/{Email}/{Mode}

Before login, client must fetch challenge from the API. Then on login, the challenge must be passed along to the API (as response to the challenge). The challenge is always fresh for some period of time and the API validates it when passed with login. The challenge has form of base64-string|timestamp|uuid. For example:

ezwXceQ63fV9oWTSJBAE2Zq1Cw5tBIJe+7+Rl8jrgbk=|1475429754114|4017bda8-0a15-4154-a8b7-88069b05cb4e

NOTE: The call must contain the same email as used for registration itself.

Email

Email address as the account username, e.g. dan.forsberg@isecure.fi

type
string
in
path
Mode

Administer account with admin mode, exchange files with data mode

type
string admin, data
in
path
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "Challenge": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

Login

POST /session/{Email}/{Mode}

After getchallenge, call login with Email, Mode, and RSA encrypted admin or data account password and challenge timestamp. For further API calls (requiring authroization), include the received IdToken into the Authorization header of the request (pass idtoken as required parameter with the client SDK API calls). The IdToken expires in ExpiresIn seconds, after which new login must be performed.

NOTE: In case SMS Code is required, the call returns Session. NOTE: If Email has not been yet verified, successful login provides only AccessToken that must be used to verify email address.

Login body parameters

Email

Email address as the account username, e.g. dan.forsberg@isecure.fi

type
string
in
path
Mode

Administer account with admin mode, exchange files with data mode

type
string admin, data
in
path
Request Content-Types: application/json
Request Example
{
  "ChResp": "ezwXceQ63fV9oWTSJBAE2Zq1Cw5tBIJe+7+Rl8jrgbk=|1475429754114|4017bda8-0a15-4154-a8b7-88069b05cb4e",
  "Encrypted": "..."
}
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "AccessToken": "string",
  "ApiKey": "string",
  "ExpiresIn": "string",
  "IdToken": "string",
  "ResponseCode": "string",
  "ResponseText": "string",
  "Session": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

LoginMFA

PUT /session/{Email}/{Mode}/mfacode

Send SMS Code along with previously received Session token. If Email has not been yet verified, successful login provides only AccessToken that must be used to verify email address. If email is already verified and the login succeeds, add the IdToken from the login response as Authorization header in API requests requiring authorization (i.e. pass as parameter to client SDK API calls). IdToken expires in ExpiresIn seconds.

Session parameters

Email

Email address as the account username, e.g. dan.forsberg@isecure.fi

type
string
in
path
Mode

Administer account with admin mode, exchange files with data mode

type
string admin, data
in
path
Request Content-Types: application/json
Request Example
{
  "Code": "123456",
  "Session": "..."
}
200 OK

Operation succesfully processed. See response.

400 Bad Request

Request validation error

500 Internal Server Error

Unexpected error occurred

Response Content-Types: application/json
Response Example (200 OK)
{
  "AccessToken": "string",
  "ApiKey": "string",
  "ExpiresIn": "string",
  "IdToken": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (400 Bad Request)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}
Response Example (500 Internal Server Error)
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

Schema Definitions

AccountDescriptor: object

AdminMode: string registered, unregistered

admin mode status

Certs: CertDescriptor
DataMode: string registered, unregistered

data mode status

Email: string

Email address as the account username

Export: string disabled, allowed

Status for certificate and private key export allowance. See ConfigCerts.

Name: string

Full name of registrant

Phone: string

Phone number with country code and + in front

Example
{
  "AdminMode": "registered",
  "DataMode": "unregistered",
  "Email": "dan.forsberg@isecure.fi",
  "Name": "Dan Forsberg",
  "Phone": "+358404835507",
  "export": "allowed"
}

CertDescriptor: object

CertName: string

Certificate common name

Expires: string

Date of expiry

Issuer: string

Certificate issuer

PEM: string

Certificate in PEM format

Serial: string

Certificate serial number

Subject: string

Certificate subject

Example
{
  "CertName": "osuuspankki_customer_signing_cert",
  "Expires": "Oct 28 06:30:08 2017 GMT",
  "Issuer": "CUSTOMER TEST OP-Pohjola WS CA",
  "PEM": "-----BEGIN CERTIFICATE-----\nMIIF+DCCA+CgAwIBAgIDEaBdMA0GCS...x0t6Cnd5lyGKg=\n-----END CERTIFICATE-----",
  "Serial": "11A05D",
  "Subject": "1000038023"
}

CertsAndKeys: object

Certificate: string

Certificate in PEM format

EncryptedPrivateKey: string

PGP encrypted ascii armored private key

Example
{
  "Certificate": "string",
  "EncryptedPrivateKey": "string"
}

ConfigCertsReq: object

Export: string

Set export to disabled to disallow certificate and private key pair exporting

Example
{
  "Export": "disabled"
}

DeleteKeyReq: object

PgpKeyId: string

8 chars hexadecimal PGP Key Id (see e.g. gpg --list-keys)

Example
{
  "PgpKeyId": "DBCBE671"
}

DeleteKeyResp: object

PgpKeys: PgpKeyDescriptor

List of PGP keys in API

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "PgpKeys": [
    {
      "PgpKeyId": "3A3A59B2",
      "PgpKeyPurpose": "authorize"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}

DownloadFileResp: object

Content: string

Downloaded file content as from bank (e.g. in Base64 form)

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "Content": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

EnrollCertReq: object

Code: string

Full PIN code from bank (e.g. combined from SMS and letter)

Company: string

Company name as registered with bank (e.g. full capital letters, see contract). NOTE: The value of this field is not compared with the account company name set during registration because the format for cert enrollment differs between banks.

WsUserId: string

SEPA WebServices channel user id as in contract with bank

Example
{
  "Code": "8642603384107437",
  "Company": "ISECURE OY",
  "WsUserId": "..."
}

ErrorResponse: object

RequestId: string

Service side request id for problem tracing purposes

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "RequestId": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

ExportCertResp: object

CertsAndKeys: CertsAndKeys

List of certificate and encrypted private key pairs

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "CertsAndKeys": [
    {
      "Certificate": "string",
      "EncryptedPrivateKey": "string"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}

FileDescriptor: object

FileReference: string

File reference id, use e.g. when downloading the file

FileTimestamp: string

Creation time stamp of the file from bank

FileType: string

Bank specific file type

ServiceId: string

Bank specific service id (e.g. bank account number)

Status: string

File download status

TargetId: string

Bank specific target id

Example
{
  "FileReference": "227166",
  "FileTimestamp": "2017-05-20T03:36:21.148+03:00",
  "FileType": "VA",
  "ServiceId": "N/A",
  "Status": "NEW",
  "TargetId": "MLP"
}

ImportCertReq: object

Certificate: string

Certificate in PEM format

Company: string

Company name as registered with bank (e.g. full capital letters without Oy, see contract)

EncCertificate: string

Certificate in PEM format (encryption certificate for DanskeBank)

EncPrivatekey: string

Private key in PEM format (encryption certificate for DanskeBank)

PrivateKey: string

Private key in PEM format

WsUserId: string

SEPA WebServices channel user id as in contract with bank

Example
{
  "Certificate": "...",
  "Company": "ISECURE OY",
  "EncCertificate": "...",
  "EncPrivatekey": "...",
  "PrivateKey": "...",
  "WsUserId": "..."
}

InitLoginResp: object

Challenge: string

Challenge copied from API response

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "Challenge": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

InitRegisterResp: object

Challenge: string

Challenge copied from API response

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "Challenge": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

ListAccountsResp: object

Accounts: AccountDescriptor

List of accounts under the API key

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "Accounts": [
    {
      "AdminMode": "registered",
      "DataMode": "unregistered",
      "Email": "dan.forsberg@isecure.fi",
      "Name": "Dan Forsberg",
      "Phone": "+358404835507",
      "export": "allowed"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}

ListCertsResp: object

Certs: CertDescriptor

List of certificates

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "Certs": [
    {
      "CertName": "osuuspankki_customer_signing_cert",
      "Expires": "Oct 28 06:30:08 2017 GMT",
      "Issuer": "CUSTOMER TEST OP-Pohjola WS CA",
      "PEM": "-----BEGIN CERTIFICATE-----\nMIIF+DCCA+CgAwIBAgIDEaBdMA0GCS...x0t6Cnd5lyGKg=\n-----END CERTIFICATE-----",
      "Serial": "11A05D",
      "Subject": "1000038023"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}

ListFilesResp: object

FileDescriptors: FileDescriptor

List of downloadable files from bank

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "FileDescriptors": [
    {
      "FileReference": "227166",
      "FileTimestamp": "2017-05-20T03:36:21.148+03:00",
      "FileType": "VA",
      "ServiceId": "N/A",
      "Status": "NEW",
      "TargetId": "MLP"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}

ListKeysResp: object

PgpKeys: PgpKeyDescriptor

List of PGP keys in API

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "PgpKeys": [
    {
      "PgpKeyId": "3A3A59B2",
      "PgpKeyPurpose": "authorize"
    }
  ],
  "ResponseCode": "string",
  "ResponseText": "string"
}

LoginMFAReq: object

Code: string

Code from SMS

Session: string

Session token from login response

Example
{
  "Code": "123456",
  "Session": "..."
}

LoginMFAResp: object

AccessToken: string

Access token

ApiKey: string

Integrator API Key

ExpiresIn: string

Session expiration time

IdToken: string

ID token

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "AccessToken": "string",
  "ApiKey": "string",
  "ExpiresIn": "string",
  "IdToken": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

LoginReq: object

ChResp: string

Challenge copied from API response

Encrypted: string

RSA encrypted password and timestamp

Example
{
  "ChResp": "ezwXceQ63fV9oWTSJBAE2Zq1Cw5tBIJe+7+Rl8jrgbk=|1475429754114|4017bda8-0a15-4154-a8b7-88069b05cb4e",
  "Encrypted": "..."
}

LoginResp: object

AccessToken: string

Access token

ApiKey: string

Integrator API Key

ExpiresIn: string

Session expiration time

IdToken: string

ID token

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Session: string

Session token

Example
{
  "AccessToken": "string",
  "ApiKey": "string",
  "ExpiresIn": "string",
  "IdToken": "string",
  "ResponseCode": "string",
  "ResponseText": "string",
  "Session": "string"
}

PasswordResetReq: object

ChResp: string

Challenge copied from API response

Code: string

Code from SMS

Encrypted: string

RSA encrypted NEW password and timestamp

Example
{
  "ChResp": "ezwXceQ63fV9oWTSJBAE2Zq1Cw5tBIJe+7+Rl8jrgbk=|1475429754114|4017bda8-0a15-4154-a8b7-88069b05cb4e",
  "Code": "123456",
  "Encrypted": "..."
}

PgpKeyDescriptor: object

PgpKeyId: string

Short version of a PGP Key id idenfiying the key, e.g. 3A3A59B2

PgpKeyPurpose: string export, authorize

PGP Key purpose

Example
{
  "PgpKeyId": "3A3A59B2",
  "PgpKeyPurpose": "authorize"
}

RegisterReq: object

ApiKey: string

Integrator API Key, or 0 if not already known (e.g. initial integrator registration)

ChResp: string

Challenge copied from API response

Company: string

Company name

Encrypted: string

RSA encrypted password and timestamp

Name: string

Full name of registrant

Phone: string

Phone number with country code and + in front

Example
{
  "ApiKey": "hzYAVO9Sg98nsNh81M84O2kyXVy6K1xwHD8",
  "ChResp": "ezwXceQ63fV9oWTSJBAE2Zq1Cw5tBIJe+7+Rl8jrgbk=|1475429754114|4017bda8-0a15-4154-a8b7-88069b05cb4e",
  "Company": "ISECure Oy",
  "Encrypted": "...",
  "Name": "Dan Forsberg",
  "Phone": "+358404835507"
}

RegisterResp: object

ApiKey: string

Integrator API Key

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "ApiKey": "string",
  "ResponseCode": "string",
  "ResponseText": "string"
}

Response: object

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

Example
{
  "ResponseCode": "string",
  "ResponseText": "string"
}

ShareCertsResp: object

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

SharedFrom: string[]

ExtEmail account that this account shares certs from

SharedTo: string[]

ExtEmail account that this account shares certs for

Example
{
  "ResponseCode": "string",
  "ResponseText": "string",
  "SharedFrom": [
    "string"
  ],
  "SharedTo": [
    "string"
  ]
}

UnshareCertsResp: object

ResponseCode: string

Two digit response code in string format

ResponseText: string

Human readable response text

SharedFrom: string[]

ExtEmail account that this account shares certs from

SharedTo: string[]

ExtEmail account that this account shares certs for

Example
{
  "ResponseCode": "string",
  "ResponseText": "string",
  "SharedFrom": [
    "string"
  ],
  "SharedTo": [
    "string"
  ]
}

UploadFileReq: object

FileContents: string

Base64 encoded file contents

FileName: string

Upload file name

FileType: string

Bank specific file type

Signature: string

Detached PGP signature(s) made with registered PGP key(s)

Example
{
  "FileContents": "...",
  "FileName": "testfile",
  "FileType": "KTL",
  "Signature": "string"
}

UploadKeyReq: object

PgpKey: string

ASCII armored PGP Key

PgpKeyPurpose: string

PGP key purpose, i.e. export (exporting cert private key) or authorize (upload content authorization verification).

Example
{
  "PgpKey": "...",
  "PgpKeyPurpose": "authorize"
}

VerifyEmailReq: object

AccessToken: string

Access token from login response

Code: string

Code from email

Example
{
  "AccessToken": "...",
  "Code": "123456"
}

VerifyPhoneReq: object

Code: string

Code from SMS

Example
{
  "Code": "123456"
}