APIX > Products > Sandbox

Sandbox

APIX Sandbox is a collaborative Integrated Development Environment (IDE) that simulates the characteristics of a bank-grade production environment. It allows developers to plug their API codes with other APIs from APIX Marketplace to create innovative solutions for the financial services industry. The Sandbox also offers an interface to a live Core banking application and an ability to import or export data via external sources like GitHub. 

versio

Collaborate with our Community

115

Financial Institutions

1463

FinTechs

285

APIs

45

Problem Statements

What APIX Sandbox has to offer

APIX Sandbox contains a large catalogue of APIs which users can subscribe to. Developers can use this Low-Code/No-Code environment to create and edit code, and integrate APIs across different solution domains such as core banking, payments, digital currency and many more. Data can be provisioned in a secure environment by the Financial Institutions to validate the efficacy of the solutions tailored. 

Leading-Edge Technology

Access cutting-edge domain-specific APIs from APIX members in your sandbox at the click of a button.

Infra Agnostic Platform

There is flexibility to move between cloud or in-prem infrastructure without being bound by operating dependencies.

Security and Privacy

Use a secure, private development environment with the assurance that your code, data and IP are safe. Your private sandbox will auto-destruct after a specified period.

Live Core Bank

Utilise a fully functional open-source core banking system with test data and over 60+ common APIs.

Seamless Collaboration

Collaborate with your teams using GitHub. Bring in pre-built code for integration with on-platform APIs for rapid prototyping.

Multi-Lingual

We support up to 10+ databases and 17+ programming languages, including Java, Javascript, Python, PHP and more.

Download Brochure
APIX Open Core - Transactions
APIX Model FinTech

See the Open Bank Documentation for more details on accessing the API. ### **Instructions to access the APIs** _Transactions_ API comprises the endpoints responsible for creating Deposits, BulkDeposits, Fee, Transfers, Seizure and Withdrawals belong to the Deposit transactions and List them. Transactions API also comprises the endpoints responsible for creating _Disbursement, Payment, RedrawPaymement, Repayment, Fee, Withdrawals and WithdrawalsRedraw_ belong to the Loan transactions and List them. If you need to make several deposits you can do it through the _BulkDeposits_ option. _Fee_ refers to the amount you can set up as a fee when creating a deposit or loan transactions. _Transfers_ refers to the amount transferred from one deposit account to an another deposit account. _Seizure_ refers to the amount seized from a deposit account. _Withdrawals_ refers to the amount withdrawn from a deposit account. _Disbursement_ refers to the amount disbursed to a transaction channel from the loan account. _Payment_ reefers to the amount paid back to the loan as a loan transaction. When using the _RedrawPaymement_ capability of a loan, borrowers can redraw or reborrow any principal amount that they had already repaid in excess of their scheduled instalments. You can process single, partial, custom or bulk \_Repayment\_s. These may be entered in the present or backdated. The amount to be paid can be customised. _WithdrawalRedraw_ creates a transaction where the user withdraws from their redraw balance.

icon

Endpoints: 21/21

icon

Subscribers: 9

APIX Open Core - Users
APIX Model FinTech

The user may create an API key with a scope that allows them to access the API programmatically without OAuth2. This feature may be "disabled" by not granting any users the permission to create API keys. Each user may create multiple API consumers which may have multiple API keys. For example, the user may create one consumer per project and assign a different API key to each program inside the project, granting different scopes of permissions. An API key is not necessary to access the API but is recommended to limit the capabilities of automated programs and reduce the risk through principle of least privilege. See the Open Bank Documentation for more details on accessing the API. ### **Instructions to access the API** Users API comprises the set of endpoints that perform create, retrieve, update and delete of _Users, UserRoles, Consumers, APIKeys,_ and _ClientRoles_. The _Users_ enables System/ Bank administrators to onboard and manage users and their access permissions. This module defines the ability of the bank’s internal users (administrators) to access the information and perform certain tasks in the system. Each permission covers an action or a small set of actions. Permissions can be assigned to users through _UserRoles_. _UserRoles_ is a way to group permissions and to control other forms of access within the core banking system. The primary purpose of a _Consumers_ is to generate API keys, which are used to authenticate API requests by including them in an `apiKey` header. Multiple users may be able to create and access one or many API consumers with different degrees of access, and each API consumer may generate multiple keys. When creating an API consumer via API, you must assign permissions explicitly. When you create an API consumer, you must assign the consumer type, which controls what actions the keys it creates may be used to authorise. _APIKeys_ inherit the access permission scope from the _Consumers_ that was used to create them. One _Consumer_ may generate multiple API keys, and they may be used concurrently. You may optionally set an expiration time for any _APIKeys_ that you create. A client models any customer that is just an individual and group models a group of customer. _ClientRoles_ define the permissions of client or group.

icon

Endpoints: 24/24

icon

Subscribers: 9

APIX Open Core - Loan Accounts
APIX Model FinTech

These are the banking assets-based products. This module includes the aspect of new loan account creation, loan update, loan closure, early settlement of loans, interest/charges, write off. See the Open Bank Documentation for more details on accessing the API. ### **Instructions to access API** Loan Accounts API comprises the set of endpoints perform create, retrieve, update and delete of _LoanAccounts, RevolvingAccounts, Funding_ and _Cards_. LoanAccounts refers to the terms and conditions determines the new loan accounts. The few of the loan account terms include the loan amount, interest rate, repayment frequency, the arrears tolerance period, and the arrears tolerance amount of your account. Various transactions can be posted including disbursing loan amount, applying interest, applying/undoing reschedule, applying/undoing refinance, applying/undoing writeoff and lock/unlock account. _Funding_ creates a new funding source for an existing loan account\_. Funding\_ are very basic deposit accounts with limited functionality, and intended only for funding fractionalized loans and receiving their repayments. _RevolvingAccounts_ and _Cards_ are lines of credit that allow multiple disbursements and repayments on the loan account. _Card_ is associated with an existing loan account. _Cards_ are payment instruments issued by the bank and electronically linked to the loan accounts belonging to the cardholder. _RevolvingAccounts_ refers to the pre-approved loan limit of a client (individual, group, or company).

icon

Endpoints: 35/35

icon

Subscribers: 9

APIX Open Core - Organizations
APIX Model FinTech

An organization refers to the entirety of your business, along with all of your branches and staff members. You may subdivide your organization into branches and centres. Clients may be assigned to a centre, which can be useful if you wish to collect centre-specific reporting. Each centre can then contain multiple clients. A client may be an individual client, managed by the Clients service, or a group client composed from multiple clients, which are managed by the Groups service. Comments may be added for all clients by users but they cannot be deleted. In addition, this API includes holidays for the organization, allowing the management of non-working days and general holidays (such as a public holiday). See the Open Bank Documentation for more details on accessing the API. ### **Instructions to access the API** Organization API comprises the set of endpoints that perform create, retrieve, update and delete of _Branches, Centres, Clients, Comments, Documents, Notifications, Channels, Holidays,_ and _Groups_. Also the API comprises endpoints for retrieving and updating of _Organization, NonWorkingDays, Config and Setup._ _Organization_ refers to the entirety of your business, along with all of your branches and staff members. _Branches_ are an organization's subdivision operating locally or having a particular function. They often represent a geographical subdivision of an organization or a product line. Each branch can have multiple centres assigned to it. A list of branch-specific _Holidays_ that may not apply to all branches in the organization. _Centres_ are subdivisions of a branch, and they may be used for a variety of reasons. They are not widely-used, but can be helpful, depending on your needs. _Client_ refers to any customer of your organization, such as a person with an account at your bank. _Group_ is not an individual person, such as a business or legal entity. Individual clients may be added to groups as members. _Client_ and _Group_ may be associated with loans and deposits and perform various transactions and roles can be assigned to it. _Comments_ are the text content owned by the owner. _Documents_ are the raw content of the file encoded in base64 owned by the owner. The list of events are defined and triggers the _Notifications_. C\_hannel\_ is a form of payment responsible for the transactions made between a client and a financial institution, such as loan disbursements, repayments, deposits, and withdrawals. _NonWorkingDays_ apply to your entire organisation, _Holidays_ can be defined as either organisation-wide or for specific branches. _Holidays_ may be configured as either recurring or non-recurring. _Config_ implies custom transfer rules overriding the default general ledger code for inter-branch transactions. This rule will be applied if the transaction is being done between the two branches specified in the rule. _Setup_ refers the general setup of the _Organization_

icon

Endpoints: 70/70

icon

Subscribers: 9

APIX Open Core - Products
APIX Model FinTech

Endpoints for managing risk levels are included in this API. See the Open Bank Documentation for more details on accessing the API. ### **Instructions to access the APIs** Products API comprises the set of endpoints perform create, retrieve, update and delete of _DepositProduct, LoanProduct_ and _RiskLevels_. A _DepositProduct_ allows you to set up in advance the parameters for a type of deposit that you wish to regularly offer. The deposit product category helps us better understand how your product is used so we can provide better service and address the specific needs of your use cases. The deposit controls section allows you to define a few internal controls for the deposit product. The deposit settings section allows you to specify the terms and constraints you define when creating a deposit product will apply to all of the deposit accounts created using that product. However, some attributes can be changed when creating a new account from a product. These include fields like **Maximum Withdrawal** and **Minimum Deposit** amounts, **Overdraft Limits** and **Overdraft Terms**, depending on the type of deposit product being used to create a deposit account. A _LoanProduct_ allows you to set up in advance the parameters for a type of loan that you wish to regularly offer. Loan products are flexible and customisable templates for creating individual loans. The loan product category helps us better understand how your product is used so we can provide better service and address the specific needs of your use cases. You can also set up internal controls for loans, such as the dormancy period, the number of days to wait before locking accounts in arrears. The terms and constraints you define when creating a loan product will apply to all of the loan accounts created using that product. However, some attributes can be changed when creating a new account from a product. These may include loan amount constraints or interest rate constraints, depending on the type of loan product being used to create a loan account. _RiskLevels_ are user defined categories composed by an interval for number of days in arrears and a correspondent provision amount. Risk levels will be used to calculate the organisation's portfolio at risk (PAR), based on the number of loans in arrears that fall into each level.

icon

Endpoints: 16/16

icon

Subscribers: 9

Stay Connected

Follow Us On
Thanks for subscribing to APIX