Sila API Docs | Sila Banking and Payments API

Welcome to the Sila API!


Links a checking or savings bank account to a verified entity, either with a Plaid public token or with account/routing numbers.


Legacy Plaid Integration - Link Token & Plaid Public Key

If you integrated Plaid through the Sila API before July 2021, you may have a legacy integration. This documentation has moved.

Sila will support Legacy public token and Link integration for the near term, however, this functionality is marked for deprecation. Please seek a direct relationship with Plaid to use our Processor Token functionality.

If you are using the legacy Plaid public key and Link integration, supporting documentation is here:

If you are using the legacy Plaid Link Token, supporting documentation is here:


To use your Plaid Integration with Sila, please follow the steps outline here to obtain a processor Token.

This endpoint accepts a token and account ID from a customer's interaction with a Plaid Link modal. Alternatively, we offer a method for direct account linking upon approval of the use case by your Sila onboarding team.


Testing Bank Account Linking

In only the sandbox, you can test bank account linking with any bank that shows up in the Plaid Link interface. Specify the username as "user_good" and the password as "pass_good".

In only the sandbox, you can test the scenario when the entity name does not match the account holder name. Set a value of no match (case insensitive) in the ”account_name” field.



Plaid tokens and token types

In the JSON spec below, the "plaid_token" can be one of: "public-xxx-xxx" or "processor-xxx-xxx". The "plaid_token_type" can be one of: "link", "processor", or "legacy". If you are using Sila's Plaid account, use a public token and indicate a "link" token type. If you have your own Plaid account, use a processor token and indicate a "processor" token type. If you are using Sila's Plaid account with Sila's legacy public_key, use a public token and indicate a "legacy" token type.
Note- We are deprecating the use of Link and Legacy token types.

Account Linking Expiration

Once an account is linked, our /issue_sila and /redeem_sila endpoints will continue to work unless manually removed using /delete_account.

However, there are two cases in which a customer will need to re-enter their login credentials with Plaid if their login session expires.

  1. /get_account_balance will return an error with the message 'Login credentials to this financial institution are invalid. Retry linking this account.'
  2. Instant ACH is not available, as it requires our system verifying that the customer has sufficient funds with an account balance check.

Each individual banking institution controls how long a login session lasts, so there is no way to predict how long this will be. 30 days is a safe bet, though it may be either shorter or longer.

POST /0.2/link_account HTTP/1.1
Content-Type: application/json

  "header": {
    "created": 1234567890, 
    "app_handle": "handle.silamoney.eth", 
    "version": "0.2", 
    "crypto": "ETH", 
    "reference": "<your unique id>"
  "plaid_token": "processor-xxx-xxx",
  "account_name": "Custom Account Name",
  "selected_account_id": "selected_account_id",
  "plaid_token_type": "processor"


HTTP/1.1  200 OK

  "success": true,
  "status": "SUCCESS",
  "reference": "ref",
  "message": "Bank account successfully linked.",
  "account_name": "Custom Account Name",
  "match_score": 0.825,
  "account_owner_name": "Sally Smith",
  "entity_name": "Sally Smith",

// Plaid verification flow (recommended)
const res = await Sila.linkAccount(
  accountName, // Account Name is not required
  accountId, // Account Id parameters is required,
  plaidTokenType, // Required. One of 'link,' 'processor,' or 'legacy'

//Public token received in the /link/item/create plaid endpoint.

// Direct account-linking flow (restricted by use-case, contact Sila for approval)
const res = await Sila.linkAccountDirect(
); // Account Type and Account Name parameters are not required

//The only permitted account type is "CHECKING"

// Success Response Object
console.log(res.statusCode); // 200
console.log(; // Random reference number
console.log(; // SUCCESS
console.log(; // Bank account successfully linked
### Link Account with Plaid
payload = {
    "public_token": "public-development-0dc5f214-56a2-4b69-8968-f27202477d3f",  # Required token from plaid
    "user_handle": "user.silamoney.eth",                                         # Required
    "account_name": "Custom Account Name",                                       # Optional (default value is "default")
    "selected_account_id": "account id",                                        # Optional
    "plaid_token_type": "plaid token type"                                      # Optional}                                         

User.linkAccount(silaApp, payload, user_private_key, plaid=True)

### Link Account with Direct Account Linking
            "user_handle": "user.silamoney.eth",    # Required
            "account_number": "123456789012",       # Required
            "routing_number": "123456789",          # Required
            "account_type": "CHECKING",             # Optional (default value is CHECKING)
            "account_name": "Custom Account Name"   # Optional (default value is "default"),


### Success Response Object
    status: 'SUCCESS',
    success: True,
    message: 'Bank account successfully manually linked.',
    reference: 'f9f23fc2-26e7-4358-99c8-75cb8aec76fb',
    account_name: 'default',
    status_code: 200,
    match_score: 0.825,
    account_owner_name: 'Sally Smith',
    entity_name: 'Sally Smith'

### Failure Response Object
    status: 'FAILURE'
String userHandle = 'user.silamoney.eth';
String accountName = 'plaid'; // Your desired account name
String publicToken = 'public-sandbox-xxx' // Your Plaid token
String userPrivateKey = 'some private key';
String accountId = 'plaid account id'; // Required
String plaidTokenType = "Legacy";

ApiResponse response = api.linkAccountPlaidToken(userHandle, userPrivateKey, accountName, publicToken, accountId, plaidTokenType);

// For Direct Account Link
String userHandle = 'user.silamoney.eth';
String accountName = 'direct'; // Your desired account name
String accountNumber = '123456789012';
String routingNumber = '123456789';
String accountType = 'CHECKING'; // Currently the only allowed value
String userPrivateKey = 'some private key';

ApiResponse response = api.linkAccount(userHandle, userPrivateKey, accountName, accountNumber, routingNumber, accountType);

// Success Response
System.out.println(response.getStatusCode()); // 200
LinkAccountResponse parsedResponse = (LinkAccountResponse) response.getData();
System.out.println(parsedResponse.getStatus()); // SUCCESS
System.out.println(parsedResponse.isSuccess()); // true
System.out.println(parsedResponse.getReference()); // Reference number
System.out.println(parsedResponse.getMessage()); // Successfully linked
System.out.println(parsedResponse.getAccountName()); // Your desired account name
System.out.println(parsedResponse.getMatchScore()); // Match score
use Silamoney\Client\Domain\PlaidTokenType;

// **Public token received in the /link/item/create endpoint: **

// SANDBOX ONLY: You can generate a testing public token instead of using the Plaid Link plugin with:
$client = new \GuzzleHttp\Client(["base_uri" => ""]);
$options = [
    'json' => [
        "public_key" => "fa9dd19eb40982275785b09760ab79",
        "initial_products" => ["transactions"],
        "institution_id" => "ins_109508",
        "credentials" => [
            "username" => "user_good",
            "password" => "pass_good"
$response = $client->post('/link/item/create', $options);
$content = json_decode($response->getBody()->getContents());
$public_token = $content->public_token; // Public Token to pass to linkAccount()
$account_id = $content->accounts[0]->account_id; // Required Account ID to pass to linkAccount()

// **IMPORTANT!** If you do not specify an `$account_id` in `linkAccount()`, the first account returned by Plaid will be linked by default.

// Plaid token flow
// Load your information
$userHandle = 'user.silamoney.eth';
$accountName = 'Custom Account Name'; // Defaults to 'default'
$plaidToken = 'public-xxx-xxx'; // A temporary token returned from the Plaid Link plugin. See above for testing.
$accountId = 'string'; // Recommended but not required. See note above.
$userPrivateKey = 'some private key'; // The private key used to register the specified user
$plaidTokenType = PlaidTokenType::LEGACY(); // Optional. Currently supported values are LEGACY (default), LINK and PROCESSOR

// Call the api
$response = $client->linkAccount($userHandle, $userPrivateKey, $plaidToken, $accountName, $accountId, $plaidTokenType);

// Direct Link account
// Load your information
$userHandle = 'user.silamoney.eth';
$accountName = 'Custom Account Name'; // Defaults to 'default' if not provided. (not required)
$routingNumber = '123456789'; // The routing number. 
$accountNumber = '123456789012'; // The bank account number
$userPrivateKey = 'some private key'; // The private key used to register the specified user
$accountType = 'CHECKING'; // The account type (not required). Only available value is CHECKING

// Call the api
$response = $client->linkAccountDirect($userHandle, $userPrivateKey, $accountNumber, $routingNumber, $accountName, $accountType);

// Success 200
echo $response->getStatusCode(); // 200
echo $response->getData()->getStatus(); // SUCCESS
echo $response->getData()->getReference();
echo $response->getData()->getMessage();
echo tAccountName();
echo $response->getData()->ge$response->getData()->getAccountOwnerName();
echo $response->getData()->getEntityName();
echo $response->getData()->getMatchScore();
ApiResponse<object> response = api.LinkAccount(userHandle, publicToken, walletPrivateKey, accountName, accountId, plaidTokenType); 
// Account Name is not required 
// Account Id is required
// plaidTokenType is not required

ApiResponse<object> response = api.LinkAccountDirect(userHandle, walletPrivateKey, accountNumber, routingNumber, accountType, accountName); // Account Type and Account Name parameters are not required 

// Success Response Object

Console.WriteLine(response.StatusCode); // 200
Console.WriteLine(((LinkAccountResponse)response.Data).Reference); // Random reference number
Console.WriteLesponse)response.Data).Status); // SUCCESS
    PlaidTokenType = "legacy"

LinkAccountResponse response.Data).Message); // Bank account successfully linked.
Console.WriteLine(((LinkAccountResponse)response.Data).AccountName); // Account Name.





JSON object

Required. Requires these keys in JSON format: created, app_handle, user_handle. See the /check_handle endpoint for the complete list of fields in this object.



Required if not setting account_number, routing_number .

If using Sila's Plaid account: Enter a valid public token from the Plaid Link modal consisting of letters, numbers, underscores, or hyphens.

If using your own Plaid account: pass a processor token obtained from Plaid. Example: processor-xxx-xxx.

This value should be match the required regex pattern: ^[-a-zA-Z0-9_]+$



Optional. Min length 1, Max length 40, default value if not sent in request is “default” Example: Custom Account Name
NOTE- We highly recommend specifying a custom name here as this is how an account is identified for /issue_sila, /redeem_sila, and /get_transactions.



Required unless using your own Plaid account and linking with a processor token. This is the Plaid account ID from list of selected account IDs returned from Plaid Link flow.

Max Length 100



Optional. Must match either "CHECKING" or "SAVINGS".



Optional. Must match either "legacy", "link" or "processor". Default value if not sent in request is “legacy”.


The request body for this endpoint is the link_account_msg JSON object.

Both authsignature and usersignature headers are required for this request.

The account_name key is not required, but can be used to set a custom name to identify the linked checking account. If not provided, the linked account's name will be "default". We highly recommend specifying a custom name. Note: user handles cannot have two linked accounts with the same name.


For customers using our Plaid verification flow

  • a processor_token from Plaid in the case that you have your own Plaid account already. In this case, set plaid_token_type to "processor".

The selected_account_id is not required; if provided, it should be an account ID in the array of selected accounts returned in the metadata object from Plaid Link. This ID can identify either a checking account or a savings account to link. Currently, we do not link multiple accounts at once; you will need to send only one account ID. If no account ID is provided, we will link the first checking account we encounter from the array of accounts the customer has at their chosen bank.


For customers using our direct account-linking flow



Direct account linking is only available to customers who have a direct relationship with an account linking provider. End users must never be able to enter in their account and routing numbers without verifying account ownership.

The account_type is not required; if not specified, this endpoint assumes that account is a "CHECKING" account. You can also specify that this account is a "SAVINGS" account.

The account_number is required. Must be all numeric character and no longer than 17 characters.

The routing_number is required. Must be numeric and exactly 9 characters long.



Status Code

success Attribute




Bank account successfully linked.



Bank account not successfully linked (public token may have expired; tokens expire in 30 minutes after creation).



Bank account linked, but in a frozen state. Requires manual review - email [email protected] for steps to unfreeze this bank account.



Check validation_details for more information. PRODUCT_NOT_READY indicates the account is waiting to be linked (with microdeposit verification, for instance).



authsignature or usersignature header was absent or incorrect.

Updated 11 days ago


Links a checking or savings bank account to a verified entity, either with a Plaid public token or with account/routing numbers.

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.