- Explore the Sila API
- Learn to navigate the docs
- Start your integration process
Step 1. Create a Sila Console account
This doc provides you with the steps to create an account and register as a developer in the Sila console.
Step 2. Register your Application
This doc provides instructions on how to register an app using the Developer Console.
To sign in to the Sila Console you will use the username or email and password you created when you signed up for an account (Step 1).
Step 3. Use the Sila API Explorer or watch the Sila Demo to gain a better understanding of the main features of the Sila API.
It is highly recommend that your Dev team test out the Sila API Explorer as it provides an interface that allows you to interact with the API in a way the breaks down the flow. Understanding these step will make the docs easier to read and ease your integration experience.
You can use the App information you generated in Step 2 to test out the Sila API Explorer.
In order to receive production access, our onboarding team needs to perform some due diligence (phase 1) in order to learn more about your business and the intended use of the Sila API.
Once you sign your MSA you will begin your onboarding journey which is separated into two parts
- Business requirements (in the form of due diligence - phase 2)
- Technical requirements (outlined below)
Completing both parts can take up to 12 weeks or longer depending on your use case. Business requirements will be communicated to you by your Sila Onboarding Specialist.
Below outlines some of the technical requirements you can access through the docs. Please note that the following requirements will need to fulfilled by all customers however there may be additional requirements based on your use case:
BEFORE YOU START TO BUILD please familiarize yourselves with Sila's Information Management and Security Requirements and the Demo Overview for the checklist and requirements. The sooner you think through implementing these requirements the smoother your onboarding process will go.
There are many different use cases for the Sila API that will allow you to use many different endpoints. However, below we have outlined the a basic endpoint flows that all Applications must start with:
- AUTH - Sila uses ECDSA to secure and validate requests. Learn more about that here.
You can build your own Auth however we highly suggest using a provided SDK in your preferred language - doing so will make the AUTH integration much easier.
- REGISTRATION FLOW - All flows start with registering an individual or a business (aka entity).
Generating a specified blockchain address (wallet) is part of this flow and happens in the first part of the /register endpoint.
- PLAID INTEGRATION - Sila has a partnership with Plaid that uses the Plaid processor token in the Sila /link_account endpoint.
Sila requires you to make use of Plaid's Balance, Identity, and Auth products. So make sure those are included when you sign your contract with Plaid.
- TRANSACTION FLOW - Request to transaction endpoints will not work until you have successfully completed the steps above.
You will be required to successfully transact with Standard or Same-Day ACH before you will be able to use Sila's other payment instruments (such as Instant ACH).
- WEBHOOKS - Sila implements webhooks so that your application can be notified when certain events occur asynchronously, eliminating the need for your app to continuously poll the Sila API to get an up-to-date status.
Webhooks are managed in the Console.
- SILA CONSOLE - The Customer Console allows Sila customers to manage their Applications, team members, webhooks and view transactions.
- There are code samples for most endpoints provided at the bottom of the applicable docs.
Keep in mind that these are not a "cut and paste" code solutions but rather a visual guide for how the request or response should looks.
- RECIPES: if the code sample aren't helping checkout these recipes for a more step by step approach to the various flows.
Updated about 1 month ago