Customer lookup (routing number required)

Checks and retreives customer lookup details based on the account type, account number, and routing number.

This is the successor to /v1/customers/lookup/{accountNumber}. The downstream Legal Entity Service is enforcing routingNumber as a mandatory field on its profile lookup API starting release 6.5.0.0; this version requires it up front so lookups continue to resolve the correct customer profile and account once that enforcement takes effect. /v1/customers/lookup/{accountNumber} remains available unchanged for existing integrations that do not yet supply a routing number.

SecurityoAuth2
Request
path Parameters
accountNumber
required
string <= 35 characters ^[a-zA-Z0-9]+$

Customer account number; all-zero values are not allowed.

Example: 1234567890
query Parameters
accountType
string

Customer account type. This is an optional field. If not provided, the default behavior is to return results for all account types.

Enum: "DEPOSIT" "LOAN"
Example: accountType=LOAN
routingNumber
required
string^[0-9]{9}$

9-digit routing number identifying which bank charter the account belongs to. Required.

Example: routingNumber=123456789
Responses
200

Successfully retrieved applicable customer lookup details

400

Bad request — invalid or missing input fields.

401

Unauthorized - You are not authorized to access the resource

403

Forbidden

404

Not Found – The requested resource could not be located. Verify the endpoint or resource identifier.

405

Method Not Allowed – HTTP method used is not supported by the requested resource.

500

Internal server error

503

Service Unavailable – The server is temporarily unavailable.

get/v2/customers/lookup/{accountNumber}
Request samples 
Response samples 
application/json
{
  • "profiles": [
    ]
}