View our documentation at https://github.com/Cybrid-app/cybrid-api-id-angular/
npm install @cybrid/cybrid-api-id-angular#
Welcome to Cybrid, an all-in-one crypto platform that enables you to easily build and launch white-label crypto products or services.
In these documents, you'll find details on how our REST API operates and generally how our platform functions.
If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our Github repo.
💡 We recommend bookmarking the Cybrid LinkTree which contains many helpful links to platform resources.
This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the Open API 3.0 yaml for import.
If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform:
1. Introduction
2. Platform Overview
3. Testing with Hosted Web Demo App
In Getting Started in the Cybrid Sandbox, we walk you through how to use the Cybrid Sandbox to create a test bank and generate API keys. In Getting Ready for Trading, we walk through creating customers, customer identities, accounts, as well as executing quotes and trades.
There are three primary ways you can interact with the Cybrid platform:
1. Directly via our RESTful API (this documentation)
2. Using our API clients available in a variety of languages (Angular, Java, Kotlin, Python, Ruby, Swift or Typescript)
3. Integrating a platform specific SDK (Web, Android, iOS)
Our complete set of APIs allows you to manage resources across three distinct areas: your Organization, your Banks and your Identities. For most of your testing and interaction you'll be using the Bank API, which is where the majority of APIs reside.
The complete set of APIs can be found on the following pages:
| API | Description |
|------------------------------------------------------------------|-------------------------------------------------------------|
| Organization API | APIs to manage organizations |
| Bank API | APIs to manage banks (and all downstream customer activity) |
| Identities API | APIs to manage organization and bank identities |
For questions please contact Support at any time for assistance, or contact the Product Team for product suggestions.
The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create Organization and Bank tokens can be generated via the Cybrid Sandbox. Access tokens can be generated for a Customer as well via the Cybrid IdP as well.
An Organization access token applies broadly to the whole Organization and all of its Banks, whereas, a Bank access token is specific to an individual Bank. Customer tokens, similarly, are scoped to a specific customer in a bank.
Both Organization and Bank tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique Client ID and Secret that allows for machine-to-machine authentication.
A Bank can then generate Customer access tokens via API using our Identities API.
⚠️ Never share your Client ID or Secret publicly or in your source code repository.
Your Client ID and Secret can be exchanged for a time-limited Bearer Token by interacting with the Cybrid Identity Provider or through interacting with the Authorize button in this document.
The following curl command can be used to quickly generate a Bearer Token for use in testing the API or demo applications.
``Example request when using Bank credentials
curl -X POST https://id.production.cybrid.app/oauth/token -d '{
\"grant_type\": \"client_credentials\",
\"client_id\": \"
\"client_secret\": \"
\"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\"
}' -H \"Content-Type: application/json\"
to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute'
⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.Authentication Scopes
The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal.
The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource.
| Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) |
|-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------|
| Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) |
| Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) |
| Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) |
| Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) |
| Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) |
| External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) |
| External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) |
| Organization | organizations:read (Organization) | organizations:write (Organization) | |
| User | users:read (Organization) | | users:execute (Organization) |
| Price | prices:read (Bank, Customer) | | |
| Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) |
| Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) |
| Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) |
| Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) |
| Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) |
Available Endpoints
The available APIs for the Identity, Organization and Bank API services are listed below:
| API Service | Model | API Endpoint Path | Description |
|--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------|
| Identity | Bank | /api/bank_applications | Create and list banks |
| Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens |
| Identity | Organization | /api/organization_applications | Create and list organizations |
| Identity | Organization | /api/users | Create and list organization users |
| Organization | Organization | /api/organizations | APIs to retrieve and update organization name |
| Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers |
| Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) |
| Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc |
| Bank | Customer | /api/customers | Create and list customers |
| Bank | Counterparty | /api/counterparties | Create and list counterparties |
| Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses |
| Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform |
| Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform |
| Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC |
| Bank | Invoice | /api/invoices | Create, get, cancel and list invoices |
| Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices |
| Bank | Price | /api/prices | Get the current prices for assets on the platform |
| Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades |
| Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) |
| Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency |
| Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) |
| Bank | Workflow | /api/workflows | Create, get and list workflows |
Understanding Object Models & Endpoints
Organizations
An
is meant to represent the organization partnering with Cybrid to use our platform.An
Organization typically does not directly interact with customers. Instead, an Organization has one or more banks, which encompass the financial service offerings of the platform.Banks
A
Bank is owned by an Organization and can be thought of as an environment or container for customers and product offerings. Banks are created in either Sandbox or Production mode, where Sandbox is the environment that you would test, prototype and build in prior to moving to Production.An
Organization can have multiple banks, in either Sandbox or Production environments. A Sandbox Bank will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes.Customers
Customers represent your banking users on the platform. At present, we offer support for Individuals as Customers.Customers must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing Identity Verification. See the Identity Verifications section for more details on how a customer can be verified.Customers must also have an Account to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
@cybrid/cybrid-api-id-angular@0.126.118
$3
To install the required dependencies and to build the typescript sources run:
`
npm install
npm run build
$3
First build the package then run
npm publish dist` (don't forget to specify the dist folder!)$3
Navigate to the folder of your consuming project and run one of next commands.
_published:_
`
npm install @cybrid/cybrid-api-id-angular@0.126.118 --save
_without publishing (not recommended):_
npm install PATH_TO_GENERATED_PACKAGE/dist.tgz --save
_It's important to take the tgz file, otherwise you'll get trouble with links on windows_
_using
:_In PATH_TO_GENERATED_PACKAGE/dist:
`
npm link
In your project:
npm link @cybrid/cybrid-api-id-angular
__Note for Windows users:__ The Angular CLI has troubles to use linked npm packages.
Please refer to this issue https://github.com/angular/angular-cli/issues/8284 for a solution / workaround.
Published packages are not effected by this issue.
#### General usage
In your Angular project:
// without configuring providers
import { ApiModule } from '@cybrid/cybrid-api-id-angular';
import { HttpClientModule } from '@angular/common/http';@NgModule({
imports: [
ApiModule,
// make sure to import the HttpClientModule in the AppModule only,
// see https://github.com/angular/angular/issues/20575
HttpClientModule
],
declarations: [ AppComponent ],
providers: [],
bootstrap: [ AppComponent ]
})
export class AppModule {}
// configuring providers
import { ApiModule, Configuration, ConfigurationParameters } from '@cybrid/cybrid-api-id-angular';export function apiConfigFactory (): Configuration {
const params: ConfigurationParameters = {
// set configuration parameters here.
}
return new Configuration(params);
}
@NgModule({
imports: [ ApiModule.forRoot(apiConfigFactory) ],
declarations: [ AppComponent ],
providers: [],
bootstrap: [ AppComponent ]
})
export class AppModule {}
// configuring providers with an authentication service that manages your access tokens
import { ApiModule, Configuration } from '@cybrid/cybrid-api-id-angular';@NgModule({
imports: [ ApiModule ],
declarations: [ AppComponent ],
providers: [
{
provide: Configuration,
useFactory: (authService: AuthService) => new Configuration(
{
basePath: environment.apiUrl,
accessToken: authService.getAccessToken.bind(authService)
}
),
deps: [AuthService],
multi: false
}
],
bootstrap: [ AppComponent ]
})
export class AppModule {}
import { DefaultApi } from '@cybrid/cybrid-api-id-angular';export class AppComponent {
constructor(private apiGateway: DefaultApi) { }
}
Note: The ApiModule is restricted to being instantiated once app wide.
This is to ensure that all services are treated as singletons.
#### Using multiple OpenAPI files / APIs / ApiModules
In order to use multiple
generated from different OpenAPI files,
you can create an alias name when importing the modules
in order to avoid naming conflicts:
`
import { ApiModule } from 'my-api-path';
import { ApiModule as OtherApiModule } from 'my-other-api-path';
import { HttpClientModule } from '@angular/common/http';@NgModule({
imports: [
ApiModule,
OtherApiModule,
// make sure to import the HttpClientModule in the AppModule only,
// see https://github.com/angular/angular/issues/20575
HttpClientModule
]
})
export class AppModule {
}
$3
If different than the generated base path, during app bootstrap, you can provide the base path to your service.
import { BASE_PATH } from '@cybrid/cybrid-api-id-angular';bootstrap(AppComponent, [
{ provide: BASE_PATH, useValue: 'https://your-web-service.com' },
]);
or
import { BASE_PATH } from '@cybrid/cybrid-api-id-angular';@NgModule({
imports: [],
declarations: [ AppComponent ],
providers: [ provide: BASE_PATH, useValue: 'https://your-web-service.com' ],
bootstrap: [ AppComponent ]
})
export class AppModule {}
#### Using @angular/cli
First extend your
files by adding the corresponding base path:`
export const environment = {
production: false,
API_BASE_PATH: 'http://127.0.0.1:8080'
};
In the src/app/app.module.ts:
import { BASE_PATH } from '@cybrid/cybrid-api-id-angular';
import { environment } from '../environments/environment';@NgModule({
declarations: [
AppComponent
],
imports: [ ],
providers: [{ provide: BASE_PATH, useValue: environment.API_BASE_PATH }],
bootstrap: [ AppComponent ]
})
export class AppModule { }