cybrid_api_bank_ruby 0.52.15 → 0.53.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (159) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +1 -1
  3. data/README.md +13 -5
  4. data/cybrid_api_bank_ruby.gemspec +2 -2
  5. data/docs/PostTransferBankModel.md +24 -0
  6. data/docs/TransferBankModel.md +36 -0
  7. data/docs/TransferListBankModel.md +24 -0
  8. data/docs/TransfersBankApi.md +238 -0
  9. data/lib/cybrid_api_bank_ruby/api/accounts_bank_api.rb +2 -2
  10. data/lib/cybrid_api_bank_ruby/api/assets_bank_api.rb +2 -2
  11. data/lib/cybrid_api_bank_ruby/api/banks_bank_api.rb +2 -2
  12. data/lib/cybrid_api_bank_ruby/api/customers_bank_api.rb +2 -2
  13. data/lib/cybrid_api_bank_ruby/api/external_bank_accounts_bank_api.rb +2 -2
  14. data/lib/cybrid_api_bank_ruby/api/fee_configurations_bank_api.rb +2 -2
  15. data/lib/cybrid_api_bank_ruby/api/identity_records_bank_api.rb +2 -2
  16. data/lib/cybrid_api_bank_ruby/api/identity_verifications_bank_api.rb +2 -2
  17. data/lib/cybrid_api_bank_ruby/api/prices_bank_api.rb +2 -2
  18. data/lib/cybrid_api_bank_ruby/api/quotes_bank_api.rb +2 -2
  19. data/lib/cybrid_api_bank_ruby/api/rewards_bank_api.rb +2 -2
  20. data/lib/cybrid_api_bank_ruby/api/symbols_bank_api.rb +2 -2
  21. data/lib/cybrid_api_bank_ruby/api/trades_bank_api.rb +2 -2
  22. data/lib/cybrid_api_bank_ruby/api/transfers_bank_api.rb +240 -0
  23. data/lib/cybrid_api_bank_ruby/api/verification_keys_bank_api.rb +2 -2
  24. data/lib/cybrid_api_bank_ruby/api/workflows_bank_api.rb +2 -2
  25. data/lib/cybrid_api_bank_ruby/api_client.rb +2 -2
  26. data/lib/cybrid_api_bank_ruby/api_error.rb +2 -2
  27. data/lib/cybrid_api_bank_ruby/configuration.rb +2 -2
  28. data/lib/cybrid_api_bank_ruby/models/account_bank_model.rb +2 -2
  29. data/lib/cybrid_api_bank_ruby/models/account_list_bank_model.rb +2 -2
  30. data/lib/cybrid_api_bank_ruby/models/asset_bank_model.rb +2 -2
  31. data/lib/cybrid_api_bank_ruby/models/asset_list_bank_model.rb +2 -2
  32. data/lib/cybrid_api_bank_ruby/models/attestation_details_bank_model.rb +2 -2
  33. data/lib/cybrid_api_bank_ruby/models/bank_bank_model.rb +2 -2
  34. data/lib/cybrid_api_bank_ruby/models/bank_list_bank_model.rb +2 -2
  35. data/lib/cybrid_api_bank_ruby/models/customer_bank_model.rb +2 -2
  36. data/lib/cybrid_api_bank_ruby/models/customer_list_bank_model.rb +2 -2
  37. data/lib/cybrid_api_bank_ruby/models/error_response_bank_model.rb +2 -2
  38. data/lib/cybrid_api_bank_ruby/models/external_bank_account_bank_model.rb +2 -2
  39. data/lib/cybrid_api_bank_ruby/models/external_bank_account_list_bank_model.rb +2 -2
  40. data/lib/cybrid_api_bank_ruby/models/fee_bank_model.rb +2 -2
  41. data/lib/cybrid_api_bank_ruby/models/fee_configuration_bank_model.rb +2 -2
  42. data/lib/cybrid_api_bank_ruby/models/fee_configuration_list_bank_model.rb +2 -2
  43. data/lib/cybrid_api_bank_ruby/models/identity_record_bank_model.rb +2 -2
  44. data/lib/cybrid_api_bank_ruby/models/identity_record_list_bank_model.rb +2 -2
  45. data/lib/cybrid_api_bank_ruby/models/identity_verification_bank_model.rb +2 -2
  46. data/lib/cybrid_api_bank_ruby/models/identity_verification_list_bank_model.rb +2 -2
  47. data/lib/cybrid_api_bank_ruby/models/patch_bank_bank_model.rb +2 -2
  48. data/lib/cybrid_api_bank_ruby/models/post_account_bank_model.rb +2 -2
  49. data/lib/cybrid_api_bank_ruby/models/post_bank_bank_model.rb +2 -2
  50. data/lib/cybrid_api_bank_ruby/models/post_customer_bank_model.rb +2 -2
  51. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_bank_model.rb +2 -2
  52. data/lib/cybrid_api_bank_ruby/models/post_fee_bank_model.rb +2 -2
  53. data/lib/cybrid_api_bank_ruby/models/post_fee_configuration_bank_model.rb +2 -2
  54. data/lib/cybrid_api_bank_ruby/models/post_identity_record_attestation_details_bank_model.rb +2 -2
  55. data/lib/cybrid_api_bank_ruby/models/post_identity_record_bank_model.rb +2 -2
  56. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_bank_model.rb +2 -2
  57. data/lib/cybrid_api_bank_ruby/models/post_quote_bank_model.rb +4 -4
  58. data/lib/cybrid_api_bank_ruby/models/post_reward_bank_model.rb +2 -2
  59. data/lib/cybrid_api_bank_ruby/models/post_trade_bank_model.rb +2 -2
  60. data/lib/cybrid_api_bank_ruby/models/post_transfer_bank_model.rb +358 -0
  61. data/lib/cybrid_api_bank_ruby/models/post_verification_key_bank_model.rb +2 -2
  62. data/lib/cybrid_api_bank_ruby/models/post_workflow_bank_model.rb +2 -2
  63. data/lib/cybrid_api_bank_ruby/models/quote_bank_model.rb +4 -4
  64. data/lib/cybrid_api_bank_ruby/models/quote_list_bank_model.rb +2 -2
  65. data/lib/cybrid_api_bank_ruby/models/reward_bank_model.rb +2 -2
  66. data/lib/cybrid_api_bank_ruby/models/reward_list_bank_model.rb +2 -2
  67. data/lib/cybrid_api_bank_ruby/models/symbol_price_bank_model.rb +2 -2
  68. data/lib/cybrid_api_bank_ruby/models/trade_bank_model.rb +2 -2
  69. data/lib/cybrid_api_bank_ruby/models/trade_list_bank_model.rb +2 -2
  70. data/lib/cybrid_api_bank_ruby/models/transfer_bank_model.rb +440 -0
  71. data/lib/cybrid_api_bank_ruby/models/transfer_list_bank_model.rb +329 -0
  72. data/lib/cybrid_api_bank_ruby/models/verification_key_bank_model.rb +2 -2
  73. data/lib/cybrid_api_bank_ruby/models/verification_key_list_bank_model.rb +2 -2
  74. data/lib/cybrid_api_bank_ruby/models/workflow_bank_model.rb +2 -2
  75. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_all_of_bank_model.rb +2 -2
  76. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_bank_model.rb +2 -2
  77. data/lib/cybrid_api_bank_ruby/models/workflows_list_bank_model.rb +2 -2
  78. data/lib/cybrid_api_bank_ruby/version.rb +3 -3
  79. data/lib/cybrid_api_bank_ruby.rb +6 -2
  80. data/spec/api/accounts_bank_api_spec.rb +2 -2
  81. data/spec/api/assets_bank_api_spec.rb +2 -2
  82. data/spec/api/banks_bank_api_spec.rb +2 -2
  83. data/spec/api/customers_bank_api_spec.rb +2 -2
  84. data/spec/api/external_bank_accounts_bank_api_spec.rb +2 -2
  85. data/spec/api/fee_configurations_bank_api_spec.rb +2 -2
  86. data/spec/api/identity_records_bank_api_spec.rb +2 -2
  87. data/spec/api/identity_verifications_bank_api_spec.rb +2 -2
  88. data/spec/api/prices_bank_api_spec.rb +2 -2
  89. data/spec/api/quotes_bank_api_spec.rb +2 -2
  90. data/spec/api/rewards_bank_api_spec.rb +2 -2
  91. data/spec/api/symbols_bank_api_spec.rb +2 -2
  92. data/spec/api/trades_bank_api_spec.rb +2 -2
  93. data/spec/api/transfers_bank_api_spec.rb +76 -0
  94. data/spec/api/verification_keys_bank_api_spec.rb +2 -2
  95. data/spec/api/workflows_bank_api_spec.rb +2 -2
  96. data/spec/api_client_spec.rb +2 -2
  97. data/spec/configuration_spec.rb +2 -2
  98. data/spec/models/account_bank_model_spec.rb +2 -2
  99. data/spec/models/account_list_bank_model_spec.rb +2 -2
  100. data/spec/models/asset_bank_model_spec.rb +2 -2
  101. data/spec/models/asset_list_bank_model_spec.rb +2 -2
  102. data/spec/models/attestation_details_bank_model_spec.rb +2 -2
  103. data/spec/models/bank_bank_model_spec.rb +2 -2
  104. data/spec/models/bank_list_bank_model_spec.rb +2 -2
  105. data/spec/models/customer_bank_model_spec.rb +2 -2
  106. data/spec/models/customer_list_bank_model_spec.rb +2 -2
  107. data/spec/models/error_response_bank_model_spec.rb +2 -2
  108. data/spec/models/external_bank_account_bank_model_spec.rb +2 -2
  109. data/spec/models/external_bank_account_list_bank_model_spec.rb +2 -2
  110. data/spec/models/fee_bank_model_spec.rb +2 -2
  111. data/spec/models/fee_configuration_bank_model_spec.rb +2 -2
  112. data/spec/models/fee_configuration_list_bank_model_spec.rb +2 -2
  113. data/spec/models/identity_record_bank_model_spec.rb +2 -2
  114. data/spec/models/identity_record_list_bank_model_spec.rb +2 -2
  115. data/spec/models/identity_verification_bank_model_spec.rb +2 -2
  116. data/spec/models/identity_verification_list_bank_model_spec.rb +2 -2
  117. data/spec/models/patch_bank_bank_model_spec.rb +2 -2
  118. data/spec/models/post_account_bank_model_spec.rb +2 -2
  119. data/spec/models/post_bank_bank_model_spec.rb +2 -2
  120. data/spec/models/post_customer_bank_model_spec.rb +2 -2
  121. data/spec/models/post_external_bank_account_bank_model_spec.rb +2 -2
  122. data/spec/models/post_fee_bank_model_spec.rb +2 -2
  123. data/spec/models/post_fee_configuration_bank_model_spec.rb +2 -2
  124. data/spec/models/post_identity_record_attestation_details_bank_model_spec.rb +2 -2
  125. data/spec/models/post_identity_record_bank_model_spec.rb +2 -2
  126. data/spec/models/post_identity_verification_bank_model_spec.rb +2 -2
  127. data/spec/models/post_quote_bank_model_spec.rb +3 -3
  128. data/spec/models/post_reward_bank_model_spec.rb +2 -2
  129. data/spec/models/post_trade_bank_model_spec.rb +2 -2
  130. data/spec/models/post_transfer_bank_model_spec.rb +60 -0
  131. data/spec/models/post_verification_key_bank_model_spec.rb +2 -2
  132. data/spec/models/post_workflow_bank_model_spec.rb +2 -2
  133. data/spec/models/quote_bank_model_spec.rb +3 -3
  134. data/spec/models/quote_list_bank_model_spec.rb +2 -2
  135. data/spec/models/reward_bank_model_spec.rb +2 -2
  136. data/spec/models/reward_list_bank_model_spec.rb +2 -2
  137. data/spec/models/symbol_price_bank_model_spec.rb +2 -2
  138. data/spec/models/trade_bank_model_spec.rb +2 -2
  139. data/spec/models/trade_list_bank_model_spec.rb +2 -2
  140. data/spec/models/transfer_bank_model_spec.rb +100 -0
  141. data/spec/models/transfer_list_bank_model_spec.rb +52 -0
  142. data/spec/models/verification_key_bank_model_spec.rb +2 -2
  143. data/spec/models/verification_key_list_bank_model_spec.rb +2 -2
  144. data/spec/models/workflow_bank_model_spec.rb +2 -2
  145. data/spec/models/workflow_with_details_all_of_bank_model_spec.rb +2 -2
  146. data/spec/models/workflow_with_details_bank_model_spec.rb +2 -2
  147. data/spec/models/workflows_list_bank_model_spec.rb +2 -2
  148. data/spec/spec_helper.rb +2 -2
  149. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0-static/byebug-11.1.3/gem_make.out +2 -2
  150. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0-static/ffi-1.15.5/gem_make.out +2 -2
  151. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0-static/jaro_winkler-1.5.4/gem_make.out +2 -2
  152. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0-static/psych-4.0.6/gem_make.out +2 -2
  153. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0-static/stringio-3.0.2/gem_make.out +2 -2
  154. data/vendor/bundle/ruby/3.1.0/gems/byebug-11.1.3/ext/byebug/Makefile +2 -2
  155. data/vendor/bundle/ruby/3.1.0/gems/ffi-1.15.5/ext/ffi_c/Makefile +2 -2
  156. data/vendor/bundle/ruby/3.1.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler/Makefile +2 -2
  157. data/vendor/bundle/ruby/3.1.0/gems/psych-4.0.6/ext/psych/Makefile +2 -2
  158. data/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio/Makefile +2 -2
  159. metadata +18 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 2d7b61b6ca7203724085edf9cc34ef688f950fe8c206449eaca5cfd103770ddc
4
- data.tar.gz: bbf06a33469626c0e17a4e8de6cf02b28eb44ddea515a47c4fe90c957dc31d45
3
+ metadata.gz: f933b7592f9af38bb8f9946cc3671bc649d79504f5cad4ed01d17ff9d0989a88
4
+ data.tar.gz: dd7f5599b73e3366b9ffc3f3259822cc85c374d4784b1391a8f8b4a93ac19add
5
5
  SHA512:
6
- metadata.gz: 7ef4da6038f898547eac4a766a64b591bd6a15b6d0bed9be5efb201046abcfa92f0a7658b9514d068aef49d0fdbee8938a3958bf15c2758c94d5b570a5e3857e
7
- data.tar.gz: e422b464892d49da377869b0cf1904db34845c9b5d1d0d3ce6e316719700084989c27c24eb4e42a92616c4831e4496b7808c2e5bade7c0645b2cbe721d2240e2
6
+ metadata.gz: 56aa639e10d13a6bb6791dbb106cf3a63baa8b12c70d6071c2b7764bb9bfd86b6d1cb244fbe112378ebb919b80bf820966afef30020094cb29d1b975bada5d25
7
+ data.tar.gz: 60a10adcea49a51ebc27361f73c568187894d3baad0a5fbe0663dedcfe716082ca902580a31c946e46b650cc4bf6a80d84696dcbab3665f93e5cab42578505e4
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- cybrid_api_bank_ruby (0.52.15)
4
+ cybrid_api_bank_ruby (0.53.0)
5
5
  typhoeus (~> 1.0, >= 1.0.1)
6
6
 
7
7
  GEM
data/README.md CHANGED
@@ -90,6 +90,7 @@ The following scopes are available on the platform and can be requested when gen
90
90
  | Rewards | rewards:read (Bank, Customer) | | rewards:execute (Bank) |
91
91
  | External bank accounts | external_bank_accounts:read (Organization, Bank, Customer) | | external_bank_accounts:execute (Bank, Customer) |
92
92
  | Workflows | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) |
93
+ | Transfers | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) |
93
94
 
94
95
  ## Available Endpoints
95
96
 
@@ -115,6 +116,7 @@ The available APIs for the [Identity](https://id.demo.cybrid.app/api/schema/swag
115
116
  | Bank | Rewards | /api/rewards | Create a new reward (automates quote/trade for simplicity) |
116
117
  | Bank | ExternalBankAccounts | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform |
117
118
  | Bank | Workflows | /api/workflows | Create, get and list workflows |
119
+ | Bank | Transfers | /api/transfers | Create, get and list transfers |
118
120
 
119
121
  ## Understanding Object Models & Endpoints
120
122
 
@@ -141,8 +143,8 @@ An `Organization` can have multiple `banks`, in either sandbox or production env
141
143
 
142
144
  This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
143
145
 
144
- - API version: v0.52.15
145
- - Package version: 0.52.15
146
+ - API version: v0.53.0
147
+ - Package version: 0.53.0
146
148
  - Build package: org.openapitools.codegen.languages.RubyClientCodegen
147
149
 
148
150
  ## Installation
@@ -158,16 +160,16 @@ gem build cybrid_api_bank_ruby.gemspec
158
160
  Then either install the gem locally:
159
161
 
160
162
  ```shell
161
- gem install ./cybrid_api_bank_ruby-0.52.15.gem
163
+ gem install ./cybrid_api_bank_ruby-0.53.0.gem
162
164
  ```
163
165
 
164
- (for development, run `gem install --dev ./cybrid_api_bank_ruby-0.52.15.gem` to install the development dependencies)
166
+ (for development, run `gem install --dev ./cybrid_api_bank_ruby-0.53.0.gem` to install the development dependencies)
165
167
 
166
168
  or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
167
169
 
168
170
  Finally add this to the Gemfile:
169
171
 
170
- gem 'cybrid_api_bank_ruby', '~> 0.52.15'
172
+ gem 'cybrid_api_bank_ruby', '~> 0.53.0'
171
173
 
172
174
  ### Install from Git
173
175
 
@@ -253,6 +255,9 @@ Class | Method | HTTP request | Description
253
255
  *CybridApiBank::TradesBankApi* | [**create_trade**](docs/TradesBankApi.md#create_trade) | **POST** /api/trades | Create Trade
254
256
  *CybridApiBank::TradesBankApi* | [**get_trade**](docs/TradesBankApi.md#get_trade) | **GET** /api/trades/{trade_guid} | Get Trade
255
257
  *CybridApiBank::TradesBankApi* | [**list_trades**](docs/TradesBankApi.md#list_trades) | **GET** /api/trades | Get trades list
258
+ *CybridApiBank::TransfersBankApi* | [**create_transfer**](docs/TransfersBankApi.md#create_transfer) | **POST** /api/transfers | Create Transfer
259
+ *CybridApiBank::TransfersBankApi* | [**get_transfer**](docs/TransfersBankApi.md#get_transfer) | **GET** /api/transfers/{transfer_guid} | Get Transfer
260
+ *CybridApiBank::TransfersBankApi* | [**list_transfers**](docs/TransfersBankApi.md#list_transfers) | **GET** /api/transfers | Get transfers list
256
261
  *CybridApiBank::VerificationKeysBankApi* | [**create_verification_key**](docs/VerificationKeysBankApi.md#create_verification_key) | **POST** /api/bank_verification_keys | Create VerificationKey
257
262
  *CybridApiBank::VerificationKeysBankApi* | [**get_verification_key**](docs/VerificationKeysBankApi.md#get_verification_key) | **GET** /api/bank_verification_keys/{verification_key_guid} | Get VerificationKey
258
263
  *CybridApiBank::VerificationKeysBankApi* | [**list_verification_keys**](docs/VerificationKeysBankApi.md#list_verification_keys) | **GET** /api/bank_verification_keys | Get Verification Keys list
@@ -295,6 +300,7 @@ Class | Method | HTTP request | Description
295
300
  - [CybridApiBank::PostQuoteBankModel](docs/PostQuoteBankModel.md)
296
301
  - [CybridApiBank::PostRewardBankModel](docs/PostRewardBankModel.md)
297
302
  - [CybridApiBank::PostTradeBankModel](docs/PostTradeBankModel.md)
303
+ - [CybridApiBank::PostTransferBankModel](docs/PostTransferBankModel.md)
298
304
  - [CybridApiBank::PostVerificationKeyBankModel](docs/PostVerificationKeyBankModel.md)
299
305
  - [CybridApiBank::PostWorkflowBankModel](docs/PostWorkflowBankModel.md)
300
306
  - [CybridApiBank::QuoteBankModel](docs/QuoteBankModel.md)
@@ -304,6 +310,8 @@ Class | Method | HTTP request | Description
304
310
  - [CybridApiBank::SymbolPriceBankModel](docs/SymbolPriceBankModel.md)
305
311
  - [CybridApiBank::TradeBankModel](docs/TradeBankModel.md)
306
312
  - [CybridApiBank::TradeListBankModel](docs/TradeListBankModel.md)
313
+ - [CybridApiBank::TransferBankModel](docs/TransferBankModel.md)
314
+ - [CybridApiBank::TransferListBankModel](docs/TransferListBankModel.md)
307
315
  - [CybridApiBank::VerificationKeyBankModel](docs/VerificationKeyBankModel.md)
308
316
  - [CybridApiBank::VerificationKeyListBankModel](docs/VerificationKeyListBankModel.md)
309
317
  - [CybridApiBank::WorkflowBankModel](docs/WorkflowBankModel.md)
@@ -3,9 +3,9 @@
3
3
  =begin
4
4
  #Cybrid Bank API
5
5
 
6
- ## Cybrid API documentation 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](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started 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](https://bank.demo.cybrid.app/api/schema/v1/swagger.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. [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started) 2. [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading) 3. [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) (or, alternatively, [Testing with Hosted Web Demo App](https://www.cybrid.xyz/guides/testing-with-the-web-demo-crypo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), we walk you through how to use the [Cybrid Sandbox](https://id.demo.cybrid.app/) to create a test bank, generate API keys, and set banks fees. In [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform 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](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), Apple-coming soon) 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](https://organization.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API 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](https://id.demo.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.demo.cybrid.app) 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. <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> 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. ``` curl -X POST https://id.demo.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute trades:execute trades:read\" }' -H \"Content-Type: application/json\" ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## 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 or a Bank 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) | |------------------------|------------------------------------------------------------|------------------------------------|-------------------------------------------------| | Organizations | organizations:read (Organization) | organizations:write (Organization) | | | Banks | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customers | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Accounts | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Prices | prices:read (Bank, Customer) | | | | Quotes | quotes:read (Organization, Bank, Customer) | | quotes:execute (Bank, Customer) | | Trades | trades:read (Organization, Bank, Customer) | | trades:execute (Bank) | | Rewards | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | External bank accounts | external_bank_accounts:read (Organization, Bank, Customer) | | external_bank_accounts:execute (Bank, Customer) | | Workflows | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.demo.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.demo.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.demo.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | VerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | Bank | Banks | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | FeeConfiguration | /api/fee_configurations | Create and list bank fees (spread or fixed) | | Bank | Customers | /api/customers | Create and list customers | | Bank | IdentityRecord | /api/identity_records | Create and list identity records, which are attached to customers for KYC | | Bank | Accounts | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Symbols | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Prices | /api/prices | Get the current prices for assets on the platform | | Bank | Quotes | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Trades | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Rewards | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | Bank | ExternalBankAccounts | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | Workflows | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` 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 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 processes will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amout 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 in our system before they can play any part on the platform, which means they must have an associated and valid `Identity Record`. See the Identity Records 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.
6
+ ## Cybrid API documentation 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](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started 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](https://bank.demo.cybrid.app/api/schema/v1/swagger.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. [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started) 2. [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading) 3. [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) (or, alternatively, [Testing with Hosted Web Demo App](https://www.cybrid.xyz/guides/testing-with-the-web-demo-crypo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), we walk you through how to use the [Cybrid Sandbox](https://id.demo.cybrid.app/) to create a test bank, generate API keys, and set banks fees. In [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform 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](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), Apple-coming soon) 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](https://organization.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API 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](https://id.demo.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.demo.cybrid.app) 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. <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> 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. ``` curl -X POST https://id.demo.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute trades:execute trades:read\" }' -H \"Content-Type: application/json\" ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## 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 or a Bank 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) | |------------------------|------------------------------------------------------------|------------------------------------|-------------------------------------------------| | Organizations | organizations:read (Organization) | organizations:write (Organization) | | | Banks | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customers | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Accounts | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Prices | prices:read (Bank, Customer) | | | | Quotes | quotes:read (Organization, Bank, Customer) | | quotes:execute (Bank, Customer) | | Trades | trades:read (Organization, Bank, Customer) | | trades:execute (Bank) | | Rewards | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | External bank accounts | external_bank_accounts:read (Organization, Bank, Customer) | | external_bank_accounts:execute (Bank, Customer) | | Workflows | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Transfers | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.demo.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.demo.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.demo.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | VerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | Bank | Banks | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | FeeConfiguration | /api/fee_configurations | Create and list bank fees (spread or fixed) | | Bank | Customers | /api/customers | Create and list customers | | Bank | IdentityRecord | /api/identity_records | Create and list identity records, which are attached to customers for KYC | | Bank | Accounts | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Symbols | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Prices | /api/prices | Get the current prices for assets on the platform | | Bank | Quotes | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Trades | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Rewards | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | Bank | ExternalBankAccounts | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | Workflows | /api/workflows | Create, get and list workflows | | Bank | Transfers | /api/transfers | Create, get and list transfers | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` 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 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 processes will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amout 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 in our system before they can play any part on the platform, which means they must have an associated and valid `Identity Record`. See the Identity Records 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.
7
7
 
8
- The version of the OpenAPI document: v0.52.15
8
+ The version of the OpenAPI document: v0.53.0
9
9
  Contact: support@cybrid.app
10
10
  Generated by: https://openapi-generator.tech
11
11
  OpenAPI Generator version: 6.0.0
@@ -0,0 +1,24 @@
1
+ # CybridApiBank::PostTransferBankModel
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **quote_guid** | **String** | The associated quote&#39;s identifier. | |
8
+ | **transfer_type** | **String** | The type of transfer. | |
9
+ | **external_bank_account_guid** | **String** | The customer&#39;s fiat asset external bank account&#39;s identifier. | [optional] |
10
+ | **expected_error** | **String** | The optional expected error to simulate transfer failure. | [optional] |
11
+
12
+ ## Example
13
+
14
+ ```ruby
15
+ require 'cybrid_api_bank_ruby'
16
+
17
+ instance = CybridApiBank::PostTransferBankModel.new(
18
+ quote_guid: null,
19
+ transfer_type: null,
20
+ external_bank_account_guid: null,
21
+ expected_error: null
22
+ )
23
+ ```
24
+
@@ -0,0 +1,36 @@
1
+ # CybridApiBank::TransferBankModel
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **guid** | **String** | Auto-generated unique identifier for the trade. | [optional] |
8
+ | **transfer_type** | **String** | The type of transfer. | [optional] |
9
+ | **customer_guid** | **String** | The associated customer&#39;s identifier. | [optional] |
10
+ | **quote_guid** | **String** | The associated quote&#39;s identifier. | [optional] |
11
+ | **asset** | **String** | The asset the transfer is related to, e.g., USD. | [optional] |
12
+ | **side** | **String** | The direction of the quote: either &#39;buy&#39; or &#39;sell&#39;. | [optional] |
13
+ | **state** | **String** | The trade&#39;s state | [optional] |
14
+ | **amount** | **Integer** | The amount being transferred. | [optional] |
15
+ | **fee** | **Integer** | The fee associated with the trade. | [optional] |
16
+ | **created_at** | **Time** | ISO8601 datetime the bank was created at. | [optional] |
17
+
18
+ ## Example
19
+
20
+ ```ruby
21
+ require 'cybrid_api_bank_ruby'
22
+
23
+ instance = CybridApiBank::TransferBankModel.new(
24
+ guid: null,
25
+ transfer_type: null,
26
+ customer_guid: null,
27
+ quote_guid: null,
28
+ asset: null,
29
+ side: null,
30
+ state: null,
31
+ amount: null,
32
+ fee: null,
33
+ created_at: null
34
+ )
35
+ ```
36
+
@@ -0,0 +1,24 @@
1
+ # CybridApiBank::TransferListBankModel
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **total** | **Integer** | The total number of records available. | |
8
+ | **page** | **Integer** | The page index to retrieve. | |
9
+ | **per_page** | **Integer** | The number of entities per page to return. | |
10
+ | **objects** | [**Array&lt;TransferBankModel&gt;**](TransferBankModel.md) | Array of trade entities | |
11
+
12
+ ## Example
13
+
14
+ ```ruby
15
+ require 'cybrid_api_bank_ruby'
16
+
17
+ instance = CybridApiBank::TransferListBankModel.new(
18
+ total: null,
19
+ page: null,
20
+ per_page: null,
21
+ objects: null
22
+ )
23
+ ```
24
+
@@ -0,0 +1,238 @@
1
+ # CybridApiBank::TransfersBankApi
2
+
3
+ All URIs are relative to *https://bank.demo.cybrid.app*
4
+
5
+ | Method | HTTP request | Description |
6
+ | ------ | ------------ | ----------- |
7
+ | [**create_transfer**](TransfersBankApi.md#create_transfer) | **POST** /api/transfers | Create Transfer |
8
+ | [**get_transfer**](TransfersBankApi.md#get_transfer) | **GET** /api/transfers/{transfer_guid} | Get Transfer |
9
+ | [**list_transfers**](TransfersBankApi.md#list_transfers) | **GET** /api/transfers | Get transfers list |
10
+
11
+
12
+ ## create_transfer
13
+
14
+ > <TransferBankModel> create_transfer(post_transfer_bank_model)
15
+
16
+ Create Transfer
17
+
18
+ Creates a transfer. Required scope: **transfers:execute**
19
+
20
+ ### Examples
21
+
22
+ ```ruby
23
+ require 'time'
24
+ require 'cybrid_api_bank_ruby'
25
+ # setup authorization
26
+ CybridApiBank.configure do |config|
27
+ # Configure Bearer authorization (JWT): BearerAuth
28
+ config.access_token = 'YOUR_BEARER_TOKEN'
29
+
30
+ # Configure OAuth2 access token for authorization: oauth2
31
+ config.access_token = 'YOUR ACCESS TOKEN'
32
+ end
33
+
34
+ api_instance = CybridApiBank::TransfersBankApi.new
35
+ post_transfer_bank_model = CybridApiBank::PostTransferBankModel.new({quote_guid: 'quote_guid_example', transfer_type: 'funding'}) # PostTransferBankModel |
36
+
37
+ begin
38
+ # Create Transfer
39
+ result = api_instance.create_transfer(post_transfer_bank_model)
40
+ p result
41
+ rescue CybridApiBank::ApiError => e
42
+ puts "Error when calling TransfersBankApi->create_transfer: #{e}"
43
+ end
44
+ ```
45
+
46
+ #### Using the create_transfer_with_http_info variant
47
+
48
+ This returns an Array which contains the response data, status code and headers.
49
+
50
+ > <Array(<TransferBankModel>, Integer, Hash)> create_transfer_with_http_info(post_transfer_bank_model)
51
+
52
+ ```ruby
53
+ begin
54
+ # Create Transfer
55
+ data, status_code, headers = api_instance.create_transfer_with_http_info(post_transfer_bank_model)
56
+ p status_code # => 2xx
57
+ p headers # => { ... }
58
+ p data # => <TransferBankModel>
59
+ rescue CybridApiBank::ApiError => e
60
+ puts "Error when calling TransfersBankApi->create_transfer_with_http_info: #{e}"
61
+ end
62
+ ```
63
+
64
+ ### Parameters
65
+
66
+ | Name | Type | Description | Notes |
67
+ | ---- | ---- | ----------- | ----- |
68
+ | **post_transfer_bank_model** | [**PostTransferBankModel**](PostTransferBankModel.md) | | |
69
+
70
+ ### Return type
71
+
72
+ [**TransferBankModel**](TransferBankModel.md)
73
+
74
+ ### Authorization
75
+
76
+ [BearerAuth](../README.md#BearerAuth), [oauth2](../README.md#oauth2)
77
+
78
+ ### HTTP request headers
79
+
80
+ - **Content-Type**: application/json
81
+ - **Accept**: application/json
82
+
83
+
84
+ ## get_transfer
85
+
86
+ > <TransferBankModel> get_transfer(transfer_guid)
87
+
88
+ Get Transfer
89
+
90
+ Retrieves a transfer. Required scope: **transfers:read**
91
+
92
+ ### Examples
93
+
94
+ ```ruby
95
+ require 'time'
96
+ require 'cybrid_api_bank_ruby'
97
+ # setup authorization
98
+ CybridApiBank.configure do |config|
99
+ # Configure Bearer authorization (JWT): BearerAuth
100
+ config.access_token = 'YOUR_BEARER_TOKEN'
101
+
102
+ # Configure OAuth2 access token for authorization: oauth2
103
+ config.access_token = 'YOUR ACCESS TOKEN'
104
+ end
105
+
106
+ api_instance = CybridApiBank::TransfersBankApi.new
107
+ transfer_guid = 'transfer_guid_example' # String | Identifier for the transfer.
108
+
109
+ begin
110
+ # Get Transfer
111
+ result = api_instance.get_transfer(transfer_guid)
112
+ p result
113
+ rescue CybridApiBank::ApiError => e
114
+ puts "Error when calling TransfersBankApi->get_transfer: #{e}"
115
+ end
116
+ ```
117
+
118
+ #### Using the get_transfer_with_http_info variant
119
+
120
+ This returns an Array which contains the response data, status code and headers.
121
+
122
+ > <Array(<TransferBankModel>, Integer, Hash)> get_transfer_with_http_info(transfer_guid)
123
+
124
+ ```ruby
125
+ begin
126
+ # Get Transfer
127
+ data, status_code, headers = api_instance.get_transfer_with_http_info(transfer_guid)
128
+ p status_code # => 2xx
129
+ p headers # => { ... }
130
+ p data # => <TransferBankModel>
131
+ rescue CybridApiBank::ApiError => e
132
+ puts "Error when calling TransfersBankApi->get_transfer_with_http_info: #{e}"
133
+ end
134
+ ```
135
+
136
+ ### Parameters
137
+
138
+ | Name | Type | Description | Notes |
139
+ | ---- | ---- | ----------- | ----- |
140
+ | **transfer_guid** | **String** | Identifier for the transfer. | |
141
+
142
+ ### Return type
143
+
144
+ [**TransferBankModel**](TransferBankModel.md)
145
+
146
+ ### Authorization
147
+
148
+ [BearerAuth](../README.md#BearerAuth), [oauth2](../README.md#oauth2)
149
+
150
+ ### HTTP request headers
151
+
152
+ - **Content-Type**: Not defined
153
+ - **Accept**: application/json
154
+
155
+
156
+ ## list_transfers
157
+
158
+ > <TransferListBankModel> list_transfers(opts)
159
+
160
+ Get transfers list
161
+
162
+ Retrieves a listing of transfers. Required scope: **transfers:read**
163
+
164
+ ### Examples
165
+
166
+ ```ruby
167
+ require 'time'
168
+ require 'cybrid_api_bank_ruby'
169
+ # setup authorization
170
+ CybridApiBank.configure do |config|
171
+ # Configure Bearer authorization (JWT): BearerAuth
172
+ config.access_token = 'YOUR_BEARER_TOKEN'
173
+
174
+ # Configure OAuth2 access token for authorization: oauth2
175
+ config.access_token = 'YOUR ACCESS TOKEN'
176
+ end
177
+
178
+ api_instance = CybridApiBank::TransfersBankApi.new
179
+ opts = {
180
+ page: 56, # Integer | The page index to retrieve.
181
+ per_page: 56, # Integer | The number of entities per page to return.
182
+ guid: 'guid_example', # String | Comma separated trade_guids to list transfers for.
183
+ bank_guid: 'bank_guid_example', # String | Comma separated bank_guids to list transfers for.
184
+ customer_guid: 'customer_guid_example', # String | Comma separated customer_guids to list transfers for.
185
+ account_guid: 'account_guid_example' # String | Comma separated account_guids to list transfers for.
186
+ }
187
+
188
+ begin
189
+ # Get transfers list
190
+ result = api_instance.list_transfers(opts)
191
+ p result
192
+ rescue CybridApiBank::ApiError => e
193
+ puts "Error when calling TransfersBankApi->list_transfers: #{e}"
194
+ end
195
+ ```
196
+
197
+ #### Using the list_transfers_with_http_info variant
198
+
199
+ This returns an Array which contains the response data, status code and headers.
200
+
201
+ > <Array(<TransferListBankModel>, Integer, Hash)> list_transfers_with_http_info(opts)
202
+
203
+ ```ruby
204
+ begin
205
+ # Get transfers list
206
+ data, status_code, headers = api_instance.list_transfers_with_http_info(opts)
207
+ p status_code # => 2xx
208
+ p headers # => { ... }
209
+ p data # => <TransferListBankModel>
210
+ rescue CybridApiBank::ApiError => e
211
+ puts "Error when calling TransfersBankApi->list_transfers_with_http_info: #{e}"
212
+ end
213
+ ```
214
+
215
+ ### Parameters
216
+
217
+ | Name | Type | Description | Notes |
218
+ | ---- | ---- | ----------- | ----- |
219
+ | **page** | **Integer** | The page index to retrieve. | [optional] |
220
+ | **per_page** | **Integer** | The number of entities per page to return. | [optional] |
221
+ | **guid** | **String** | Comma separated trade_guids to list transfers for. | [optional] |
222
+ | **bank_guid** | **String** | Comma separated bank_guids to list transfers for. | [optional] |
223
+ | **customer_guid** | **String** | Comma separated customer_guids to list transfers for. | [optional] |
224
+ | **account_guid** | **String** | Comma separated account_guids to list transfers for. | [optional] |
225
+
226
+ ### Return type
227
+
228
+ [**TransferListBankModel**](TransferListBankModel.md)
229
+
230
+ ### Authorization
231
+
232
+ [BearerAuth](../README.md#BearerAuth), [oauth2](../README.md#oauth2)
233
+
234
+ ### HTTP request headers
235
+
236
+ - **Content-Type**: Not defined
237
+ - **Accept**: application/json
238
+
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #Cybrid Bank API
3
3
 
4
- ## Cybrid API documentation 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](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started 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](https://bank.demo.cybrid.app/api/schema/v1/swagger.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. [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started) 2. [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading) 3. [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) (or, alternatively, [Testing with Hosted Web Demo App](https://www.cybrid.xyz/guides/testing-with-the-web-demo-crypo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), we walk you through how to use the [Cybrid Sandbox](https://id.demo.cybrid.app/) to create a test bank, generate API keys, and set banks fees. In [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform 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](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), Apple-coming soon) 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](https://organization.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API 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](https://id.demo.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.demo.cybrid.app) 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. <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> 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. ``` curl -X POST https://id.demo.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute trades:execute trades:read\" }' -H \"Content-Type: application/json\" ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## 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 or a Bank 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) | |------------------------|------------------------------------------------------------|------------------------------------|-------------------------------------------------| | Organizations | organizations:read (Organization) | organizations:write (Organization) | | | Banks | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customers | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Accounts | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Prices | prices:read (Bank, Customer) | | | | Quotes | quotes:read (Organization, Bank, Customer) | | quotes:execute (Bank, Customer) | | Trades | trades:read (Organization, Bank, Customer) | | trades:execute (Bank) | | Rewards | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | External bank accounts | external_bank_accounts:read (Organization, Bank, Customer) | | external_bank_accounts:execute (Bank, Customer) | | Workflows | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.demo.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.demo.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.demo.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | VerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | Bank | Banks | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | FeeConfiguration | /api/fee_configurations | Create and list bank fees (spread or fixed) | | Bank | Customers | /api/customers | Create and list customers | | Bank | IdentityRecord | /api/identity_records | Create and list identity records, which are attached to customers for KYC | | Bank | Accounts | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Symbols | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Prices | /api/prices | Get the current prices for assets on the platform | | Bank | Quotes | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Trades | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Rewards | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | Bank | ExternalBankAccounts | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | Workflows | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` 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 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 processes will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amout 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 in our system before they can play any part on the platform, which means they must have an associated and valid `Identity Record`. See the Identity Records 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.
4
+ ## Cybrid API documentation 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](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started 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](https://bank.demo.cybrid.app/api/schema/v1/swagger.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. [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started) 2. [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading) 3. [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) (or, alternatively, [Testing with Hosted Web Demo App](https://www.cybrid.xyz/guides/testing-with-the-web-demo-crypo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), we walk you through how to use the [Cybrid Sandbox](https://id.demo.cybrid.app/) to create a test bank, generate API keys, and set banks fees. In [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform 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](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), Apple-coming soon) 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](https://organization.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API 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](https://id.demo.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.demo.cybrid.app) 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. <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> 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. ``` curl -X POST https://id.demo.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute trades:execute trades:read\" }' -H \"Content-Type: application/json\" ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## 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 or a Bank 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) | |------------------------|------------------------------------------------------------|------------------------------------|-------------------------------------------------| | Organizations | organizations:read (Organization) | organizations:write (Organization) | | | Banks | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customers | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Accounts | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Prices | prices:read (Bank, Customer) | | | | Quotes | quotes:read (Organization, Bank, Customer) | | quotes:execute (Bank, Customer) | | Trades | trades:read (Organization, Bank, Customer) | | trades:execute (Bank) | | Rewards | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | External bank accounts | external_bank_accounts:read (Organization, Bank, Customer) | | external_bank_accounts:execute (Bank, Customer) | | Workflows | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Transfers | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.demo.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.demo.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.demo.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | VerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | Bank | Banks | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | FeeConfiguration | /api/fee_configurations | Create and list bank fees (spread or fixed) | | Bank | Customers | /api/customers | Create and list customers | | Bank | IdentityRecord | /api/identity_records | Create and list identity records, which are attached to customers for KYC | | Bank | Accounts | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Symbols | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Prices | /api/prices | Get the current prices for assets on the platform | | Bank | Quotes | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Trades | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Rewards | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | Bank | ExternalBankAccounts | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | Workflows | /api/workflows | Create, get and list workflows | | Bank | Transfers | /api/transfers | Create, get and list transfers | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` 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 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 processes will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amout 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 in our system before they can play any part on the platform, which means they must have an associated and valid `Identity Record`. See the Identity Records 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.
5
5
 
6
- The version of the OpenAPI document: v0.52.15
6
+ The version of the OpenAPI document: v0.53.0
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0