/check_routing_number_capabilities
This endpoint allows you to check the capabilities of a routing number without needing to link the external account first.
Request
Authorization / Authentication
Apps using Access Token Authorization
Use a valid access token in an Authorization: Bearer request header.
See Authenticating with an Access Token for more details.
Apps using ECDSA Authentication
Both authsignature and usersignature headers are required for this request. The usersignature header should be generated with a keypair registered to the user (either registered from the /register endpoint or the /register_wallet endpoint).
See the section on ECDSA Authentication for more detail about ECDSA signature generation.
Header
Please note that the header block is not required for this request.
GET /0.2/check_routing_number_capabilites HTTP/1.1
sandbox.silamoney.com
Content-Type: application/json
// if using OAuth2
Authorization: Bearer [GENERATED JWT TOKEN HERE]
// if using ECDSA
authsignature: [GENERATED AUTHSIGNATURE HEX STRING HERE]
usersignature: [GENERATED USERSIGNATURE HEX STRING HERE]
{
"routing_number": "123456789" //required
}
***
HTTP/1.1 200 OK
{
"success": true,
"capabilities": {
"aba_routing_number": "123456789",
"fednow": {
"credit_enabled": false,
"debit_enabled": false
},
"rtp": {
"credit_enabled": false,
"debit_enabled": false
}
},
"status": "SUCCESS",
"reference": "40740ca3-2f81-4d68-9e05-f0cc36782d13",
"response_time_ms": "2204"
}
Request Attributes
| Key | Type | Description |
|---|---|---|
| header | JSON object | Optional. If provided, requires keys in JSON format: createdapp_handleThe reference key is an optional string. Can be any value for your own reference. If not provided, one will be assigned. |
| routing_number | String | Required. Nine digit FI routing number. |
Responses
| Status Code | Success Attribute | Description | error_code |
|---|---|---|---|
| 200 | true |
Updated 9 days ago