Customers Administration v0.3.2

Scroll down for code samples, example requests and responses. Select a language for code samples from the tabs above or the mobile navigation menu.

An API for managing the financial institution's customers, also known as members at credit unions. This API only accesses customers enrolled in digital banking. It cannot access financial institution customers that are only in the banking core (for example, those who only bank at the branch or via ATMs).

This API provides one operation:

  • getBankingCustomers: an administrative application can fetch information about one or more customers enrolled in Apiture Digital Banking:

Authenticated Access

The operations in this API require an OAuth2 access token, which may either be obtained via the Client Credentials flow (for use by secure headless applications) or by Authorization Code Flow by financial institution (FI) administrative users who authenticate with the financial institution's workforce identity provider. Non-FI partner organizations may only use Client Credentials.

Accessing Customers for a Specific Financial Institution

The access token is associated with a unique Client ID. Client IDs are normally associated with a specific financial institution. If the Client ID is not tied to a specific institution, the client must provide the Institution-Id request header parameter to identify the target institution where the customers and customers are held. This header is ignored otherwise.

Download OpenAPI Definition (YAML)

Base URLs:

Terms of service

Email: Apiture Web: Apiture

License: Apiture API License

Authentication

  • OAuth2 authentication (clientCredentials)
Scope Scope Description
bankingAdmin/read Read a wide variety of banking and other financial institution and customer data.
bankingAdmin/write Write a wide variety of banking and other financial institution and customer data.

Banking Customers Admin

Banking Customers Administration

getBankingCustomers

Code samples

# You can also use wget
curl -X GET https://api.apiture.com/bankingAdmin/bankingCustomers?customers=b0002de89f878411c5f8,29eeb140c5ad8743507d,0afd7e9dba0a838f85d7,120d3b696d5737cc5413,75a7fce04e741365c698 \
  -H 'Accept: application/json' \
  -H 'Institution-Id: TIBURON' \
  -H 'Authorization: Bearer {access-token}'

GET https://api.apiture.com/bankingAdmin/bankingCustomers?customers=b0002de89f878411c5f8,29eeb140c5ad8743507d,0afd7e9dba0a838f85d7,120d3b696d5737cc5413,75a7fce04e741365c698 HTTP/1.1
Host: api.apiture.com
Accept: application/json
Institution-Id: TIBURON

const fetch = require('node-fetch');

const headers = {
  'Accept':'application/json',
  'Institution-Id':'TIBURON',
  'Authorization':'Bearer {access-token}'

};

fetch('https://api.apiture.com/bankingAdmin/bankingCustomers?customers=b0002de89f878411c5f8,29eeb140c5ad8743507d,0afd7e9dba0a838f85d7,120d3b696d5737cc5413,75a7fce04e741365c698',
{
  method: 'GET',

  headers: headers
})
.then(function(res) {
    return res.json();
}).then(function(body) {
    console.log(body);
});

var headers = {
  'Accept':'application/json',
  'Institution-Id':'TIBURON',
  'Authorization':'Bearer {access-token}'

};

$.ajax({
  url: 'https://api.apiture.com/bankingAdmin/bankingCustomers',
  method: 'get',
  data: '?customers=b0002de89f878411c5f8,29eeb140c5ad8743507d,0afd7e9dba0a838f85d7,120d3b696d5737cc5413,75a7fce04e741365c698',
  headers: headers,
  success: function(data) {
    console.log(JSON.stringify(data));
  }
})

require 'rest-client'
require 'json'

headers = {
  'Accept' => 'application/json',
  'Institution-Id' => 'TIBURON',
  'Authorization' => 'Bearer {access-token}'
}

result = RestClient.get 'https://api.apiture.com/bankingAdmin/bankingCustomers',
  params: {
  'customers' => 'array[string]'
}, headers: headers

p JSON.parse(result)

import requests
headers = {
  'Accept': 'application/json',
  'Institution-Id': 'TIBURON',
  'Authorization': 'Bearer {access-token}'
}

r = requests.get('https://api.apiture.com/bankingAdmin/bankingCustomers', params={
  'customers': [
  "b0002de89f878411c5f8",
  "29eeb140c5ad8743507d",
  "0afd7e9dba0a838f85d7",
  "120d3b696d5737cc5413",
  "75a7fce04e741365c698"
]
}, headers = headers)

print r.json()

URL obj = new URL("https://api.apiture.com/bankingAdmin/bankingCustomers?customers=b0002de89f878411c5f8,29eeb140c5ad8743507d,0afd7e9dba0a838f85d7,120d3b696d5737cc5413,75a7fce04e741365c698");
HttpURLConnection con = (HttpURLConnection) obj.openConnection();
con.setRequestMethod("GET");
int responseCode = con.getResponseCode();
BufferedReader in = new BufferedReader(
    new InputStreamReader(con.getInputStream()));
String inputLine;
StringBuffer response = new StringBuffer();
while ((inputLine = in.readLine()) != null) {
    response.append(inputLine);
}
in.close();
System.out.println(response.toString());

package main

import (
       "bytes"
       "net/http"
)

func main() {

    headers := map[string][]string{
        "Accept": []string{"application/json"},
        "Institution-Id": []string{"TIBURON"},
        "Authorization": []string{"Bearer {access-token}"},
        
    }

    data := bytes.NewBuffer([]byte{jsonReq})
    req, err := http.NewRequest("GET", "https://api.apiture.com/bankingAdmin/bankingCustomers", data)
    req.Header = headers

    client := &http.Client{}
    resp, err := client.Do(req)
    // ...
}

List banking customers at a financial institution.

GET https://api.apiture.com/bankingAdmin/bankingCustomers

Return banking customer (member) details for a selected list of banking customer IDs.

Parameters

ParameterDescription
customers
in: query
array[string] (required)
Fetch customer details for the customers identified in this comma-separated list of banking customer IDs.
unique items
minItems: 1
maxItems: 32
comma-delimited
items: string
» minLength: 6
» maxLength: 48
» pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$"
unmasked
in: query
boolean
When requesting customer details, the sensitive personally identifiable information (PII) about each customer is masked for security reasons. Include this query parameter with a value of true to request that the response body includes the full PII. Such requests are auditable. The following data fields are among those that are masked by default: phone numbers, email addresses, login user name, date of birth.
default: false
Institution-Id
in: header
institutionId
The unique identifier of the financial institution.
minLength: 2
maxLength: 8
pattern: "^[A-Z0-9_]{2,8}$"

Example responses

200 Response

{
  "items": [
    {
      "id": "0399abed-fd3d",
      "coreCustomerId": "12299292",
      "username": "peck_plumbing",
      "name": "Peck Plumbing",
      "state": "enabled",
      "type": "commercial",
      "commercial": {
        "contactName": "Max Peck"
      },
      "contactCard": {
        "addresses": {
          "primary": {
            "address1": "1805 Tiburon Dr.",
            "address2": "Building 14, Suite 1500",
            "locality": "Wilmington",
            "regionCode": "NC",
            "countryCode": "US",
            "postalCode": "28412"
          },
          "mailing": {
            "address1": "P.O. Box 0000000",
            "locality": "Wilmington",
            "regionCode": "NC",
            "countryCode": "US",
            "postalCode": "28412"
          }
        },
        "emailAddresses": {
          "primary": "max@example.com",
          "secondary": "plank_plumbing@example.com"
        },
        "phoneNumbers": {
          "primary": "9105555512",
          "mobile": "9105555513",
          "alternate": "910555514",
          "fax": "9105555515"
        }
      },
      "identityChallengeFactors": {
        "email": {
          "primary": true,
          "secondary": false
        },
        "sms": {
          "primary": false,
          "secondary": false,
          "mobile": true,
          "alternate": false
        },
        "voice": {
          "primary": false,
          "secondary": true,
          "mobile": true,
          "alternate": true
        }
      },
      "lastLoggedInAt": "2023-08-14T10:51:48.375Z",
      "lastLoggedInAttemptedAt": "2023-08-14T10:51:48.375Z",
      "createdAt": "2020-05-04T12:37:08.375Z",
      "enrolledAt": "2020-05-04T12:37:08.375Z",
      "employee": "unknown"
    }
  ]
}

Responses

StatusDescription
200 OK
OK. The response contains the customer information for the requested customer IDs.
Schema: bankingCustomerList
StatusDescription
400 Bad Request

Bad Request. The request body, request headers, and/or query parameters are not well-formed.

This error response may have one of the following type values:

Schema: Inline
StatusDescription
401 Unauthorized

Unauthorized. The operation requires authentication but no authentication or insufficient authentication was given.

This error response may have one of the following type values:

Schema: Inline
StatusDescription
403 Forbidden

Forbidden. The authenticated caller is not authorized to perform the requested operation.

This error response may have one of the following type values:

  • https://production.api.apiture.com/errors/forbidden/v1.0.0
    The user or agent is not allowed to perform this operation; authentication credentials were provided in the request, but the server considers them insufficient to grant access. Remediation: Check the user's permissions and entitlements before attempting the operation.
Schema: Inline
StatusDescription
404 Not Found

Not found. There is no such resource at the request URL.

This error response may have one of the following type values:

Schema: Inline
StatusDescription
422 Unprocessable Entity

Unprocessable Entity. The request body and/or query parameters were well-formed but otherwise invalid.

This error response may have one of the following type values:

Schema: problemResponse
StatusDescription
429 Too Many Requests

Too Many Requests. The client has sent too many requests in a given amount of time.

This error response may have one of the following type values:

Schema: Inline
StatusDescription
4XX Unknown
Client Request Problem. The client request had a problem not listed under another specific 400-level HTTP response code. View the detail in the problem response for additional details.
Schema: Inline
StatusDescription
5XX Unknown
Server Problem. The server encountered a problem not listed under another specific 500-level HTTP response code. View the detail in the problem response for additional details.
Schema: Inline

Response Schema

Status Code 400

Property Name Description
Problem Response (v0.4.1) object
API problem or error response, as per RFC 9457 application/problem+json.
» type string(uri-reference)
A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank".
maxLength: 2048
» title string(text)
A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type.
maxLength: 120
» status integer(int32)
The HTTP status code for this occurrence of the problem.
minimum: 100
maximum: 599
» detail string(text)
A human-readable explanation specific to this occurrence of the problem.
maxLength: 256
» instance string(uri-reference)
A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment
maxLength: 2048
» id readOnlyResourceId
The unique identifier for this problem. This is an immutable opaque string.
minLength: 6
maxLength: 48
pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$
» occurredAt readOnlyTimestamp(date-time)
The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.
minLength: 20
maxLength: 30
» problems array: [apiProblem]
Optional root-causes if there are multiple problems in the request or API call processing.
maxItems: 128
» attributes object
Additional optional attributes related to the problem. This data conforms to the schema associated with the error type.

Status Code 401

Property Name Description
Problem Response (v0.4.1) object
API problem or error response, as per RFC 9457 application/problem+json.
» type string(uri-reference)
A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank".
maxLength: 2048
» title string(text)
A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type.
maxLength: 120
» status integer(int32)
The HTTP status code for this occurrence of the problem.
minimum: 100
maximum: 599
» detail string(text)
A human-readable explanation specific to this occurrence of the problem.
maxLength: 256
» instance string(uri-reference)
A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment
maxLength: 2048
» id readOnlyResourceId
The unique identifier for this problem. This is an immutable opaque string.
minLength: 6
maxLength: 48
pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$
» occurredAt readOnlyTimestamp(date-time)
The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.
minLength: 20
maxLength: 30
» problems array: [apiProblem]
Optional root-causes if there are multiple problems in the request or API call processing.
maxItems: 128
» attributes object
Additional optional attributes related to the problem. This data conforms to the schema associated with the error type.

Status Code 403

Property Name Description
Problem Response (v0.4.1) object
API problem or error response, as per RFC 9457 application/problem+json.
» type string(uri-reference)
A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank".
maxLength: 2048
» title string(text)
A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type.
maxLength: 120
» status integer(int32)
The HTTP status code for this occurrence of the problem.
minimum: 100
maximum: 599
» detail string(text)
A human-readable explanation specific to this occurrence of the problem.
maxLength: 256
» instance string(uri-reference)
A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment
maxLength: 2048
» id readOnlyResourceId
The unique identifier for this problem. This is an immutable opaque string.
minLength: 6
maxLength: 48
pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$
» occurredAt readOnlyTimestamp(date-time)
The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.
minLength: 20
maxLength: 30
» problems array: [apiProblem]
Optional root-causes if there are multiple problems in the request or API call processing.
maxItems: 128
» attributes object
Additional optional attributes related to the problem. This data conforms to the schema associated with the error type.

Status Code 404

Property Name Description
Problem Response (v0.4.1) object
API problem or error response, as per RFC 9457 application/problem+json.
» type string(uri-reference)
A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank".
maxLength: 2048
» title string(text)
A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type.
maxLength: 120
» status integer(int32)
The HTTP status code for this occurrence of the problem.
minimum: 100
maximum: 599
» detail string(text)
A human-readable explanation specific to this occurrence of the problem.
maxLength: 256
» instance string(uri-reference)
A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment
maxLength: 2048
» id readOnlyResourceId
The unique identifier for this problem. This is an immutable opaque string.
minLength: 6
maxLength: 48
pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$
» occurredAt readOnlyTimestamp(date-time)
The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.
minLength: 20
maxLength: 30
» problems array: [apiProblem]
Optional root-causes if there are multiple problems in the request or API call processing.
maxItems: 128
» attributes object
Additional optional attributes related to the problem. This data conforms to the schema associated with the error type.

Status Code 429

Property Name Description
Problem Response (v0.4.1) object
API problem or error response, as per RFC 9457 application/problem+json.
» type string(uri-reference)
A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank".
maxLength: 2048
» title string(text)
A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type.
maxLength: 120
» status integer(int32)
The HTTP status code for this occurrence of the problem.
minimum: 100
maximum: 599
» detail string(text)
A human-readable explanation specific to this occurrence of the problem.
maxLength: 256
» instance string(uri-reference)
A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment
maxLength: 2048
» id readOnlyResourceId
The unique identifier for this problem. This is an immutable opaque string.
minLength: 6
maxLength: 48
pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$
» occurredAt readOnlyTimestamp(date-time)
The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.
minLength: 20
maxLength: 30
» problems array: [apiProblem]
Optional root-causes if there are multiple problems in the request or API call processing.
maxItems: 128
» attributes object
Additional optional attributes related to the problem. This data conforms to the schema associated with the error type.

Status Code 4XX

Property Name Description
Problem Response (v0.4.1) object
API problem or error response, as per RFC 9457 application/problem+json.
» type string(uri-reference)
A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank".
maxLength: 2048
» title string(text)
A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type.
maxLength: 120
» status integer(int32)
The HTTP status code for this occurrence of the problem.
minimum: 100
maximum: 599
» detail string(text)
A human-readable explanation specific to this occurrence of the problem.
maxLength: 256
» instance string(uri-reference)
A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment
maxLength: 2048
» id readOnlyResourceId
The unique identifier for this problem. This is an immutable opaque string.
minLength: 6
maxLength: 48
pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$
» occurredAt readOnlyTimestamp(date-time)
The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.
minLength: 20
maxLength: 30
» problems array: [apiProblem]
Optional root-causes if there are multiple problems in the request or API call processing.
maxItems: 128
» attributes object
Additional optional attributes related to the problem. This data conforms to the schema associated with the error type.

Status Code 5XX

Property Name Description
Problem Response (v0.4.1) object
API problem or error response, as per RFC 9457 application/problem+json.
» type string(uri-reference)
A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank".
maxLength: 2048
» title string(text)
A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type.
maxLength: 120
» status integer(int32)
The HTTP status code for this occurrence of the problem.
minimum: 100
maximum: 599
» detail string(text)
A human-readable explanation specific to this occurrence of the problem.
maxLength: 256
» instance string(uri-reference)
A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment
maxLength: 2048
» id readOnlyResourceId
The unique identifier for this problem. This is an immutable opaque string.
minLength: 6
maxLength: 48
pattern: ^[-_:.~$a-zA-Z0-9]{6,48}$
» occurredAt readOnlyTimestamp(date-time)
The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.
minLength: 20
maxLength: 30
» problems array: [apiProblem]
Optional root-causes if there are multiple problems in the request or API call processing.
maxItems: 128
» attributes object
Additional optional attributes related to the problem. This data conforms to the schema associated with the error type.

Schemas

address

{
  "address1": "1805 Tiburon Dr.",
  "address2": "Building 14, Suite 1500",
  "locality": "Wilmington",
  "regionCode": "NC",
  "countryCode": "US",
  "postalCode": "28403"
}

Address (v1.6.0)

A postal address that can hold a US address or an international (non-US) postal addresses.

Properties

NameDescription
Address (v1.6.0) object
A postal address that can hold a US address or an international (non-US) postal addresses.
address1 string(text) (required)
The first line of the postal address. In the US, this typically includes the building number and street name.
format: text
maxLength: 35
address2 string(text)
The second line of the street address. This should only be used if it has a value. Typical values include building numbers, suite numbers, and other identifying information beyond the first line of the postal address.
format: text
maxLength: 35
locality string(text) (required)
The city/town/municipality of the address.
format: text
maxLength: 30
countryCode string (required)
The ISO-3611 alpha-2 value for the country associated with the postal address.
minLength: 2
maxLength: 2
pattern: "^[A-Za-z]{2}$"
regionName string(text)
The state, district, or outlying area of the postal address. This is required if countryCode is not US. regionCode and regionName are mutually exclusive.
format: text
minLength: 2
maxLength: 20
regionCode string
The state, district, or outlying area of the postal address. This is required if countryCode is US. regionCode and regionName are mutually exclusive.
minLength: 2
maxLength: 2
pattern: "^[A-Za-z]{2}$"
postalCode string (required)
The postal code, which varies in format by country. If countryCode is US, this should be a five digit US ZIP code or ten character ZIP+4.
minLength: 2
maxLength: 20
pattern: "[0-9A-Za-z][- 0-9A-Za-z]{0,18}[0-9A-Za-z]"

apiProblem

{
  "id": "3fbad566-be86-4b22-9ba6-3ca99fdc0799",
  "type": "https://production.api.apiture.com/errors/accountNotFound/v1.0.0",
  "title": "Account Not Found",
  "status": 422,
  "occurredAt": "2022-04-25T12:42:21.375Z",
  "detail": "No account exists at the given account_url",
  "instance": "https://production.api.apiture.com/banking/transfers/bb709151-575041fcd617"
}

API Problem (v1.2.1)

API problem or error, as per RFC 7807 application/problem+json.

Properties

NameDescription
API Problem (v1.2.1) object
API problem or error, as per RFC 7807 application/problem+json.
type string(uri-reference)
A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank".
format: uri-reference
maxLength: 2048
title string(text)
A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type.
format: text
maxLength: 120
status integer(int32)
The HTTP status code for this occurrence of the problem.
format: int32
minimum: 100
maximum: 599
detail string(text)
A human-readable explanation specific to this occurrence of the problem.
format: text
maxLength: 256
instance string(uri-reference)
A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment
format: uri-reference
maxLength: 2048
id readOnlyResourceId
The unique identifier for this problem. This is an immutable opaque string.
read-only
minLength: 6
maxLength: 48
pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$"
occurredAt readOnlyTimestamp(date-time)
The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.
read-only
format: date-time
minLength: 20
maxLength: 30
problems array: [apiProblem]
Optional root-causes if there are multiple problems in the request or API call processing.
maxItems: 128
items: object

bankingCustomerInstitutionEmployeeState

"employee"

Banking Customer FI Employee State (v1.0.0)

Indicates if the banking customer is also an employee of the financial institution.

bankingCustomerInstitutionEmployeeState strings may have one of the following enumerated values:

ValueDescription
employeeEmployee:

This banking customer is currently a current employee of the financial institution.

notAnEmployeeNot an Employee:

This banking customer is not a current employee of the financial institution.

unknownUnknown:

The banking customer's employee status with the financial institution is unknown.

type: string


enum values: employee, notAnEmployee, unknown

bankingCustomerItem

{
  "id": "0399abed-fd3d",
  "coreCustomerId": "12299292",
  "username": "peck_plumbing",
  "name": "Peck Plumbing",
  "type": "commercial",
  "state": "enabled",
  "commercial": {
    "contactName": "Max Peck"
  },
  "contactCard": {
    "addresses": {
      "primary": {
        "address1": "1805 Tiburon Dr.",
        "address2": "Building 14, Suite 1500",
        "locality": "Wilmington",
        "regionCode": "NC",
        "countryCode": "US",
        "postalCode": "28412"
      },
      "mailing": {
        "address1": "P.O. Box 0000000",
        "locality": "Wilmington",
        "regionCode": "NC",
        "countryCode": "US",
        "postalCode": "28412"
      }
    },
    "emailAddresses": {
      "primary": "max@example.com",
      "secondary": "plank_plumbing@example.com"
    },
    "phoneNumbers": {
      "primary": "+19105555512",
      "mobile": "+19105555513",
      "alternate": "+19105555514",
      "fax": "+19105555514"
    }
  },
  "identityChallengeFactors": {
    "email": {
      "primary": true,
      "secondary": false
    },
    "sms": {
      "primary": false,
      "secondary": false,
      "mobile": true,
      "alternate": false
    },
    "voice": {
      "primary": false,
      "secondary": true,
      "mobile": true,
      "alternate": true
    }
  },
  "employee": "unknown",
  "lastLoggedInAt": "2023-08-14T10:51:48.375Z",
  "lastLoginAttemptedAt": "2023-08-14T10:51:48.375Z",
  "createdAt": "2020-05-04T12:37:08.375Z",
  "enrolledAt": "2020-05-04T12:37:08.375Z"
}

Banking Customer Item (v1.1.3)

Summary representation of a banking customer (member) resource in banking customers collections. To fetch the full representation of this banking customer, use the getBankingCustomer operation, passing this item's id field as the bankingCustomerId path parameter.

Personally Identifiable Information (PII) in the customer record are masked by default. Use ?unmasked=true in the request to unmask the data. The example shows unmasked data.

Properties

NameDescription
Banking Customer Item (v1.1.3) object
Summary representation of a banking customer (member) resource in banking customers collections. To fetch the full representation of this banking customer, use the getBankingCustomer operation, passing this item's id field as the bankingCustomerId path parameter.

Personally Identifiable Information (PII) in the customer record are masked by default. Use ?unmasked=true in the request to unmask the data. The example shows unmasked data.

id readOnlyResourceId (required)
The unique identifier for this banking customer (member) resource. This is an immutable opaque string.
read-only
minLength: 6
maxLength: 48
pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$"
coreCustomerId coreCustomerId
The unique ID of the customer (member) in the banking core. This value is not available on all banking cores.
minLength: 1
maxLength: 48
pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$"
username customerUsername(text) (required)
A customer's login username. This property may be masked (some character sequences replaced with *) unless unmasked data is requested.
format: text
maxLength: 20
name string(text) (required)
The customer's full name.
format: text
minLength: 1
maxLength: 50
type customerType (required)
Indicates the type of digital banking customer/member.
enum values: commercial, retail
state bankingCustomerState (required)

The state of the banking customer at the financial institution.

bankingCustomerState strings may have one of the following enumerated values:

ValueDescription
enabledEnabled:

An active banking customer for which digital banking is enabled.

disabledDisabled:

A banking customer for which digital banking is disabled.


enum values: enabled, disabled
retail retailBankingCustomer
Customer properties, present only if the customer type is retail. Either of the retail or commercial properties are present, but not both.
commercial commercialBankingCustomer
Customer properties, present only if the customer type is commercial. Either of the retail or commercial properties are present, but not both.
contactCard customerContactCard (required)
The contact information for the customer. Email addresses and phone numbers are masked unless the request uses ?unmasked=true.
identityChallengeFactors customerIdentityChallengeFactors (required)
Indicates which which channels (specific email addresses or specific phone numbers) are enabled for the email, sms or voice factors when performing multi-factor authentication and other identity challenges.
employee bankingCustomerInstitutionEmployeeState (required)

Indicates if the banking customer is also an employee of the financial institution.

bankingCustomerInstitutionEmployeeState strings may have one of the following enumerated values:

ValueDescription
employeeEmployee:

This banking customer is currently a current employee of the financial institution.

notAnEmployeeNot an Employee:

This banking customer is not a current employee of the financial institution.

unknownUnknown:

The banking customer's employee status with the financial institution is unknown.


enum values: employee, notAnEmployee, unknown
lastLoggedInAt readOnlyTimestamp(date-time)
The date/time when the customer last logged in via any channel.
read-only
format: date-time
minLength: 20
maxLength: 30
lastLoginAttemptedAt readOnlyTimestamp(date-time)
The date/time when the customer last attempted to log in via any channel, whether successful or failed.
read-only
format: date-time
minLength: 20
maxLength: 30
createdAt readOnlyTimestamp(date-time)
The date/time when the customer relationship with the financial institution was created.
read-only
format: date-time
minLength: 20
maxLength: 30
enrolledAt readOnlyTimestamp(date-time)
The date/time when the customer was enrolled in digital banking.
read-only
format: date-time
minLength: 20
maxLength: 30

bankingCustomerList

{
  "items": [
    {
      "id": "0399abed-fd3d",
      "coreCustomerId": "12299292",
      "username": "peck_plumbing",
      "name": "Peck Plumbing",
      "state": "enabled",
      "type": "commercial",
      "commercial": {
        "contactName": "Max Peck"
      },
      "contactCard": {
        "addresses": {
          "primary": {
            "address1": "1805 Tiburon Dr.",
            "address2": "Building 14, Suite 1500",
            "locality": "Wilmington",
            "regionCode": "NC",
            "countryCode": "US",
            "postalCode": "28412"
          },
          "mailing": {
            "address1": "P.O. Box 0000000",
            "locality": "Wilmington",
            "regionCode": "NC",
            "countryCode": "US",
            "postalCode": "28412"
          }
        },
        "emailAddresses": {
          "primary": "max@example.com",
          "secondary": "plank_plumbing@example.com"
        },
        "phoneNumbers": {
          "primary": "9105555512",
          "mobile": "9105555513",
          "alternate": "910555514",
          "fax": "9105555515"
        }
      },
      "identityChallengeFactors": {
        "email": {
          "primary": true,
          "secondary": false
        },
        "sms": {
          "primary": false,
          "secondary": false,
          "mobile": true,
          "alternate": false
        },
        "voice": {
          "primary": false,
          "secondary": true,
          "mobile": true,
          "alternate": true
        }
      },
      "lastLoggedInAt": "2023-08-14T10:51:48.375Z",
      "lastLoggedInAttemptedAt": "2023-08-14T10:51:48.375Z",
      "createdAt": "2020-05-04T12:37:08.375Z",
      "enrolledAt": "2020-05-04T12:37:08.375Z",
      "employee": "unknown"
    }
  ]
}

Banking Customer List (v1.1.4)

A list of banking customers.

Personally Identifiable Information (PII) in the customer record are masked by default. Use ?unmasked=true in the request to unmask the data. The example shows masked data, although the examples do not imply or dictate any specific masking rules. See the bankingCustomerItem schema for an example with unmasked data.

Properties

NameDescription
Banking Customer List (v1.1.4) object
A list of banking customers.

Personally Identifiable Information (PII) in the customer record are masked by default. Use ?unmasked=true in the request to unmask the data. The example shows masked data, although the examples do not imply or dictate any specific masking rules. See the bankingCustomerItem schema for an example with unmasked data.

items array: [bankingCustomerItem] (required)
An array of banking customers.
minItems: 1
maxItems: 32
items: object

bankingCustomerState

"enabled"

Banking Customer State (v1.0.0)

The state of the banking customer at the financial institution.

bankingCustomerState strings may have one of the following enumerated values:

ValueDescription
enabledEnabled:

An active banking customer for which digital banking is enabled.

disabledDisabled:

A banking customer for which digital banking is disabled.

type: string


enum values: enabled, disabled

commercialBankingCustomer

{
  "contactName": "string"
}

Commercial Banking Customer (v1.0.1)

Properties of commercial banking customers.

Properties

NameDescription
Commercial Banking Customer (v1.0.1) object
Properties of commercial banking customers.
contactName string(text)
The optional name of the primary contact at the business.
format: text
minLength: 1
maxLength: 50

coreCustomerId

"string"

Core Customer Id (v1.0.1)

The unique ID of the customer/member in the banking core.

type: string


minLength: 1
maxLength: 48
pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$"

customerAddresses

{
  "primary": {
    "address1": "1805 Tiburon Dr.",
    "locality": "Wilmington",
    "regionCode": "NC",
    "countryCode": "US",
    "postalCode": "28412"
  },
  "mailing": {
    "address1": "P.O. Box 1805",
    "locality": "Wilmington",
    "regionCode": "NC",
    "countryCode": "US",
    "postalCode": "28412"
  }
}

Customer Addresses (v1.0.0)

A customer's postal addresses.

Properties

NameDescription
Customer Addresses (v1.0.0) object
A customer's postal addresses.
primary address
The customer's primary address. For individuals, this is their home address. For businesses, this is the company's business address.
mailing address
The customer's mailing address. If present, financial institution sends statements and other documents to this address instead of the primary address.

customerContactCard

{
  "addresses": {
    "primary": {
      "address1": "1805 Tiburon Dr.",
      "locality": "Wilmington",
      "regionCode": "NC",
      "countryCode": "US",
      "postalCode": "28412"
    },
    "mailing": {
      "address1": "P.O. Box 1805",
      "locality": "Wilmington",
      "regionCode": "NC",
      "countryCode": "US",
      "postalCode": "28412"
    }
  },
  "emailAddresses": {
    "primary": "Max.Pike@example.com",
    "secondary": "MaxwellPike@me.example.com"
  },
  "phoneNumbers": {
    "primary": "+19105550155",
    "mobile": "+19105550150"
  }
}

Customer Contact Card (v1.1.0)

A customer's contact information.

Properties

NameDescription
Customer Contact Card (v1.1.0) object
A customer's contact information.
addresses customerAddresses (required)
The customer's postal addresses.
emailAddresses customerEmailAddresses (required)
The customer's email addresses.
phoneNumbers customerPhoneNumbers (required)
The customer's phone numbers.

customerEmailAddress

"Max.Pike@example.com"

Customer Email Address (v1.0.0)

A customer's single email address.

type: string(email)


format: email
maxLength: 255

customerEmailAddresses

{
  "primary": "Max.Pike@example.com",
  "secondary": "MaxwellPike@me.example.com"
}

Customer Email Addresses (v1.1.0)

A customer's email addresses.

Properties

NameDescription
Customer Email Addresses (v1.1.0) object
A customer's email addresses.
primary customerEmailAddress(email)
The primary email address of the customer.
format: email
maxLength: 255
secondary customerEmailAddress(email)
The secondary email address of the customer. This object is omitted if there is not a secondary email address.
format: email
maxLength: 255

customerEmailChallengeChannels

{
  "primary": true,
  "secondary": false
}

Customer Email Address Challenge Channels (v1.0.0)

Indicates which of the customer's email addresses may be used for email multi-factor authentication or other identity challenges. Each address is a separate channel for the email challenge factor.

Properties

NameDescription
Customer Email Address Challenge Channels (v1.0.0) object
Indicates which of the customer's email addresses may be used for email multi-factor authentication or other identity challenges. Each address is a separate channel for the email challenge factor.
primary boolean (required)
If true, the primary email address may be used as an identity challenge channel.
secondary boolean (required)
If true, the secondary email address may be used as an identity challenge channel.

customerIdentityChallengeFactors

{
  "email": {
    "primary": true,
    "secondary": false
  },
  "sms": {
    "primary": false,
    "secondary": false,
    "mobile": true,
    "alternate": false
  },
  "voice": {
    "primary": false,
    "secondary": true,
    "mobile": true,
    "alternate": true
  }
}

Customer Identity Challenge Factors (v1.0.1)

Indicates which which channels (specific email addresses or specific phone numbers) are enabled for the email, sms or voice factors when performing multi-factor authentication and other identity challenges.

Properties

NameDescription
Customer Identity Challenge Factors (v1.0.1) object
Indicates which which channels (specific email addresses or specific phone numbers) are enabled for the email, sms or voice factors when performing multi-factor authentication and other identity challenges.
email customerEmailChallengeChannels (required)
Indicates which of the customer's email addresses may be used for an email identity challenge or multi-factor authentication.
sms customerPhoneChallengeChannels (required)
Indicates which of the customer's email addresses may be used for a sms (text message) identity challenge or multi-factor authentication.
voice customerPhoneChallengeChannels (required)
Indicates which of the customer's email addresses may be used for a voice (automated voice call) identity challenge or multi-factor authentication.

customerPhoneChallengeChannels

{
  "primary": false,
  "secondary": false,
  "mobile": true,
  "alternate": true
}

Customer Phone Challenge Channels (v1.0.1)

Indicates which of the customer's phone numbers may be used for phone-based multi-factor authentication or other identity challenges. Each phone number is a separate channel for the sms and voice challenge factors.

Properties

NameDescription
Customer Phone Challenge Channels (v1.0.1) object
Indicates which of the customer's phone numbers may be used for phone-based multi-factor authentication or other identity challenges. Each phone number is a separate channel for the sms and voice challenge factors.
primary boolean (required)
If true, the customer's primary phone number may be used as an identity challenge channel.
secondary boolean (required)
If true, the customer's secondary phone number may be used as an identity challenge channel.
mobile boolean (required)
If true, the customer's mobile phone number may be used as an identity challenge channel.
alternate boolean (required)
If true, the customer's alternate phone number may be used as an identity challenge channel.

customerPhoneNumbers

{
  "primary": "+19105550155",
  "mobile": "+19105550150"
}

Customer Phone Numbers (v1.0.0)

A customer's phone numbers.

Properties

NameDescription
Customer Phone Numbers (v1.0.0) object
A customer's phone numbers.
primary simplePhoneNumber(phone-number) (required)
The primary phone number of the customer.
format: phone-number
minLength: 5
maxLength: 20
secondary simplePhoneNumber(phone-number)
The secondary phone number of the customer. This object is omitted if there is not a secondary phone number.
format: phone-number
minLength: 5
maxLength: 20
mobile simplePhoneNumber(phone-number)
The mobile phone number of the customer. This object is omitted if there is not a mobile phone number.
format: phone-number
minLength: 5
maxLength: 20
alternate simplePhoneNumber(phone-number)
The alternate phone number of the customer. This object is omitted if there is not an alternate phone number.
format: phone-number
minLength: 5
maxLength: 20
fax simplePhoneNumber(phone-number)
The fax number of the customer. This object is omitted if there is not a fax phone number.
format: phone-number
minLength: 5
maxLength: 20

customerType

"commercial"

Customer Type (v1.0.0)

Indicates the type of digital banking customer/member.

type: string


enum values: commercial, retail

customerUsername

"string"

Customer Username (v1.0.0)

A customer's login username.

type: string(text)


format: text
maxLength: 20

institutionId

"TIBURON"

Institution ID (v1.1.0)

The unique immutable identifier of a financial institution.

type: string


minLength: 2
maxLength: 8
pattern: "^[A-Z0-9_]{2,8}$"

problemResponse

{
  "id": "3fbad566-be86-4b22-9ba6-3ca99fdc0799",
  "type": "https://production.api.apiture.com/errors/noSuchAccount/v1.0.0",
  "title": "Account Not Found",
  "status": 422,
  "occurredAt": "2022-04-25T12:42:21.375Z",
  "detail": "No account exists for the given account reference",
  "instance": "https://production.api.apiture.com/banking/transfers/bb709151-575041fcd617"
}

Problem Response (v0.4.1)

API problem or error response, as per RFC 9457 application/problem+json.

Properties

NameDescription
Problem Response (v0.4.1) object
API problem or error response, as per RFC 9457 application/problem+json.
type string(uri-reference)
A URI reference (RFC3986) that identifies the problem type. If present, this is the URL of human-readable HTML documentation for the problem type. When this member is not present, its value is assumed to be "about:blank".
format: uri-reference
maxLength: 2048
title string(text)
A short, human-readable summary of the problem type. The title is usually the same for all problem with the same type.
format: text
maxLength: 120
status integer(int32)
The HTTP status code for this occurrence of the problem.
format: int32
minimum: 100
maximum: 599
detail string(text)
A human-readable explanation specific to this occurrence of the problem.
format: text
maxLength: 256
instance string(uri-reference)
A URI reference that identifies the specific occurrence of the problem. This is the URI of an API resource that the problem is related to, with a unique error correlation ID URI fragment
format: uri-reference
maxLength: 2048
id readOnlyResourceId
The unique identifier for this problem. This is an immutable opaque string.
read-only
minLength: 6
maxLength: 48
pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$"
occurredAt readOnlyTimestamp(date-time)
The timestamp when the problem occurred, in RFC 3339 date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.
read-only
format: date-time
minLength: 20
maxLength: 30
problems array: [apiProblem]
Optional root-causes if there are multiple problems in the request or API call processing.
maxItems: 128
items: object
attributes object
Additional optional attributes related to the problem. This data conforms to the schema associated with the error type.

readOnlyResourceId

"string"

Read-only Resource Identifier (v1.0.1)

The unique, opaque system-assigned identifier for a resource. This case-sensitive ID is also used in URLs as path parameters or in other properties or parameters that reference a resource by ID rather than URL. Resource IDs are immutable.

type: string


read-only
minLength: 6
maxLength: 48
pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$"

readOnlyTimestamp

"2021-10-30T19:06:04.250Z"

Read-Only Timestamp (v1.0.0)

A readonly or derived timestamp (an instant in time) formatted in RFC 3339 date-time UTC format: YYYY-MM-DDThh:mm:ss.sssZ.

type: string(date-time)


read-only
format: date-time
minLength: 20
maxLength: 30

resourceId

"string"

Resource Identifier (v1.0.1)

The unique, opaque system identifier for a resource. This case-sensitive ID is also used as path parameters in URLs or in other properties or parameters that reference a resource by ID rather than URL.

type: string


minLength: 6
maxLength: 48
pattern: "^[-_:.~$a-zA-Z0-9]{6,48}$"

retailBankingCustomer

{
  "birthdate": "20**-**-*1"
}

Retail Banking Customer (v1.0.1)

Properties of retail banking customers.

Properties

NameDescription
Retail Banking Customer (v1.0.1) object
Properties of retail banking customers.
birthdate string(text)
The customer's date of birth. This property may be masked (some digits replaced with *) unless unmasked data is requested.
format: text
minLength: 10
maxLength: 10
pattern: "^(19|20|\\*\\*)[0-9*]{2}-[0-9*]{2}-[0-9*]{2}$"

simplePhoneNumber

"+19105550155"

Simple Phone Number (v1.1.0)

The phone number as a string. The service strips all spaces, hyphens, periods and parentheses from input. The default country code prefix is +1. Phone numbers are returned in responses in E.164 format with a leading +, country code (up to 3 digits) and subscriber number for a total of up to 15 digits. See Phone Number Representations for more information. If the number is masked to hide Personally Identifiable Information, all but the last four digits are replaced with one or more *, such as *1234.

type: string(phone-number)


format: phone-number
minLength: 5
maxLength: 20


Generated by @apiture/api-doc 3.2.1 on Wed Apr 10 2024 15:36:14 GMT+0000 (Coordinated Universal Time).