cybrid_api_bank_ruby 0.113.54 → 0.113.56

Sign up to get free protection for your applications and to get access to all the features.
Files changed (331) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +2 -2
  3. data/README.md +5 -5
  4. data/cybrid_api_bank_ruby.gemspec +1 -1
  5. data/docs/TransferDestinationAccountBankModel.md +5 -1
  6. data/docs/TransferSourceAccountBankModel.md +5 -1
  7. data/lib/cybrid_api_bank_ruby/api/accounts_bank_api.rb +1 -1
  8. data/lib/cybrid_api_bank_ruby/api/assets_bank_api.rb +1 -1
  9. data/lib/cybrid_api_bank_ruby/api/banks_bank_api.rb +1 -1
  10. data/lib/cybrid_api_bank_ruby/api/customers_bank_api.rb +1 -1
  11. data/lib/cybrid_api_bank_ruby/api/deposit_addresses_bank_api.rb +1 -1
  12. data/lib/cybrid_api_bank_ruby/api/deposit_bank_accounts_bank_api.rb +1 -1
  13. data/lib/cybrid_api_bank_ruby/api/external_bank_accounts_bank_api.rb +1 -1
  14. data/lib/cybrid_api_bank_ruby/api/external_wallets_bank_api.rb +1 -1
  15. data/lib/cybrid_api_bank_ruby/api/identity_verifications_bank_api.rb +1 -1
  16. data/lib/cybrid_api_bank_ruby/api/prices_bank_api.rb +1 -1
  17. data/lib/cybrid_api_bank_ruby/api/quotes_bank_api.rb +1 -1
  18. data/lib/cybrid_api_bank_ruby/api/symbols_bank_api.rb +1 -1
  19. data/lib/cybrid_api_bank_ruby/api/trades_bank_api.rb +1 -1
  20. data/lib/cybrid_api_bank_ruby/api/transfers_bank_api.rb +1 -1
  21. data/lib/cybrid_api_bank_ruby/api/workflows_bank_api.rb +1 -1
  22. data/lib/cybrid_api_bank_ruby/api_client.rb +1 -1
  23. data/lib/cybrid_api_bank_ruby/api_error.rb +1 -1
  24. data/lib/cybrid_api_bank_ruby/configuration.rb +1 -1
  25. data/lib/cybrid_api_bank_ruby/models/account_bank_model.rb +1 -1
  26. data/lib/cybrid_api_bank_ruby/models/account_list_bank_model.rb +1 -1
  27. data/lib/cybrid_api_bank_ruby/models/account_state_bank_model.rb +1 -1
  28. data/lib/cybrid_api_bank_ruby/models/account_type_bank_model.rb +1 -1
  29. data/lib/cybrid_api_bank_ruby/models/asset_bank_model.rb +1 -1
  30. data/lib/cybrid_api_bank_ruby/models/asset_list_bank_model.rb +1 -1
  31. data/lib/cybrid_api_bank_ruby/models/asset_types_bank_model.rb +1 -1
  32. data/lib/cybrid_api_bank_ruby/models/bank_bank_model.rb +1 -1
  33. data/lib/cybrid_api_bank_ruby/models/bank_feature_bank_model.rb +1 -1
  34. data/lib/cybrid_api_bank_ruby/models/bank_list_bank_model.rb +1 -1
  35. data/lib/cybrid_api_bank_ruby/models/bank_type_bank_model.rb +1 -1
  36. data/lib/cybrid_api_bank_ruby/models/customer_address_bank_model.rb +1 -1
  37. data/lib/cybrid_api_bank_ruby/models/customer_bank_model.rb +1 -1
  38. data/lib/cybrid_api_bank_ruby/models/customer_list_bank_model.rb +1 -1
  39. data/lib/cybrid_api_bank_ruby/models/customer_name_bank_model.rb +1 -1
  40. data/lib/cybrid_api_bank_ruby/models/customer_state_bank_model.rb +1 -1
  41. data/lib/cybrid_api_bank_ruby/models/customer_type_bank_model.rb +1 -1
  42. data/lib/cybrid_api_bank_ruby/models/deposit_address_bank_model.rb +1 -1
  43. data/lib/cybrid_api_bank_ruby/models/deposit_address_format_bank_model.rb +1 -1
  44. data/lib/cybrid_api_bank_ruby/models/deposit_address_list_bank_model.rb +1 -1
  45. data/lib/cybrid_api_bank_ruby/models/deposit_address_state_bank_model.rb +1 -1
  46. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_account_details_inner_bank_model.rb +1 -1
  47. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_bank_model.rb +1 -1
  48. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_counterparty_address_bank_model.rb +1 -1
  49. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_list_bank_model.rb +1 -1
  50. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_routing_details_inner_bank_model.rb +1 -1
  51. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_routing_number_type_bank_model.rb +1 -1
  52. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_state_bank_model.rb +1 -1
  53. data/lib/cybrid_api_bank_ruby/models/error_response_bank_model.rb +1 -1
  54. data/lib/cybrid_api_bank_ruby/models/external_bank_account_balances_bank_model.rb +1 -1
  55. data/lib/cybrid_api_bank_ruby/models/external_bank_account_bank_model.rb +1 -1
  56. data/lib/cybrid_api_bank_ruby/models/external_bank_account_kind_bank_model.rb +1 -1
  57. data/lib/cybrid_api_bank_ruby/models/external_bank_account_list_bank_model.rb +1 -1
  58. data/lib/cybrid_api_bank_ruby/models/external_bank_account_pii_inner_addresses_inner_bank_model.rb +1 -1
  59. data/lib/cybrid_api_bank_ruby/models/external_bank_account_pii_inner_bank_model.rb +1 -1
  60. data/lib/cybrid_api_bank_ruby/models/external_bank_account_state_bank_model.rb +1 -1
  61. data/lib/cybrid_api_bank_ruby/models/external_wallet_bank_model.rb +1 -1
  62. data/lib/cybrid_api_bank_ruby/models/external_wallet_environment_bank_model.rb +1 -1
  63. data/lib/cybrid_api_bank_ruby/models/external_wallet_list_bank_model.rb +1 -1
  64. data/lib/cybrid_api_bank_ruby/models/external_wallet_state_bank_model.rb +1 -1
  65. data/lib/cybrid_api_bank_ruby/models/identity_verification_bank_model.rb +1 -1
  66. data/lib/cybrid_api_bank_ruby/models/identity_verification_list_bank_model.rb +1 -1
  67. data/lib/cybrid_api_bank_ruby/models/identity_verification_method_bank_model.rb +1 -1
  68. data/lib/cybrid_api_bank_ruby/models/identity_verification_outcome_bank_model.rb +1 -1
  69. data/lib/cybrid_api_bank_ruby/models/identity_verification_persona_state_bank_model.rb +1 -1
  70. data/lib/cybrid_api_bank_ruby/models/identity_verification_state_bank_model.rb +1 -1
  71. data/lib/cybrid_api_bank_ruby/models/identity_verification_type_bank_model.rb +1 -1
  72. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_all_of_bank_model.rb +1 -1
  73. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_bank_model.rb +1 -1
  74. data/lib/cybrid_api_bank_ruby/models/patch_bank_bank_model.rb +1 -1
  75. data/lib/cybrid_api_bank_ruby/models/patch_customer_bank_model.rb +1 -1
  76. data/lib/cybrid_api_bank_ruby/models/patch_external_bank_account_bank_model.rb +1 -1
  77. data/lib/cybrid_api_bank_ruby/models/post_account_bank_model.rb +1 -1
  78. data/lib/cybrid_api_bank_ruby/models/post_bank_bank_model.rb +1 -1
  79. data/lib/cybrid_api_bank_ruby/models/post_customer_address_bank_model.rb +1 -1
  80. data/lib/cybrid_api_bank_ruby/models/post_customer_bank_model.rb +1 -1
  81. data/lib/cybrid_api_bank_ruby/models/post_customer_name_bank_model.rb +1 -1
  82. data/lib/cybrid_api_bank_ruby/models/post_deposit_address_bank_model.rb +1 -1
  83. data/lib/cybrid_api_bank_ruby/models/post_deposit_bank_account_bank_model.rb +1 -1
  84. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_bank_model.rb +1 -1
  85. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_address_bank_model.rb +1 -1
  86. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_bank_account_bank_model.rb +1 -1
  87. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_name_bank_model.rb +1 -1
  88. data/lib/cybrid_api_bank_ruby/models/post_external_wallet_bank_model.rb +1 -1
  89. data/lib/cybrid_api_bank_ruby/models/post_identification_number_bank_model.rb +1 -1
  90. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_address_bank_model.rb +1 -1
  91. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_bank_model.rb +1 -1
  92. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_name_bank_model.rb +1 -1
  93. data/lib/cybrid_api_bank_ruby/models/post_quote_bank_model.rb +1 -1
  94. data/lib/cybrid_api_bank_ruby/models/post_trade_bank_model.rb +1 -1
  95. data/lib/cybrid_api_bank_ruby/models/post_transfer_bank_model.rb +1 -1
  96. data/lib/cybrid_api_bank_ruby/models/post_workflow_bank_model.rb +1 -1
  97. data/lib/cybrid_api_bank_ruby/models/quote_bank_model.rb +1 -1
  98. data/lib/cybrid_api_bank_ruby/models/quote_list_bank_model.rb +1 -1
  99. data/lib/cybrid_api_bank_ruby/models/quote_side_bank_model.rb +1 -1
  100. data/lib/cybrid_api_bank_ruby/models/quote_type_bank_model.rb +1 -1
  101. data/lib/cybrid_api_bank_ruby/models/symbol_price_bank_model.rb +1 -1
  102. data/lib/cybrid_api_bank_ruby/models/trade_bank_model.rb +1 -1
  103. data/lib/cybrid_api_bank_ruby/models/trade_list_bank_model.rb +1 -1
  104. data/lib/cybrid_api_bank_ruby/models/trade_side_bank_model.rb +1 -1
  105. data/lib/cybrid_api_bank_ruby/models/trade_state_bank_model.rb +1 -1
  106. data/lib/cybrid_api_bank_ruby/models/trade_type_bank_model.rb +1 -1
  107. data/lib/cybrid_api_bank_ruby/models/transfer_account_type_bank_model.rb +1 -1
  108. data/lib/cybrid_api_bank_ruby/models/transfer_bank_model.rb +1 -1
  109. data/lib/cybrid_api_bank_ruby/models/transfer_destination_account_bank_model.rb +75 -5
  110. data/lib/cybrid_api_bank_ruby/models/transfer_list_bank_model.rb +1 -1
  111. data/lib/cybrid_api_bank_ruby/models/transfer_side_bank_model.rb +1 -1
  112. data/lib/cybrid_api_bank_ruby/models/transfer_source_account_bank_model.rb +75 -5
  113. data/lib/cybrid_api_bank_ruby/models/transfer_state_bank_model.rb +1 -1
  114. data/lib/cybrid_api_bank_ruby/models/transfer_type_bank_model.rb +1 -1
  115. data/lib/cybrid_api_bank_ruby/models/verification_check_bank_model.rb +1 -1
  116. data/lib/cybrid_api_bank_ruby/models/verification_check_state_bank_model.rb +1 -1
  117. data/lib/cybrid_api_bank_ruby/models/verification_check_type_bank_model.rb +1 -1
  118. data/lib/cybrid_api_bank_ruby/models/workflow_bank_model.rb +1 -1
  119. data/lib/cybrid_api_bank_ruby/models/workflow_state_bank_model.rb +1 -1
  120. data/lib/cybrid_api_bank_ruby/models/workflow_type_bank_model.rb +1 -1
  121. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_all_of_bank_model.rb +1 -1
  122. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_bank_model.rb +1 -1
  123. data/lib/cybrid_api_bank_ruby/models/workflows_list_bank_model.rb +1 -1
  124. data/lib/cybrid_api_bank_ruby/version.rb +2 -2
  125. data/lib/cybrid_api_bank_ruby.rb +1 -1
  126. data/spec/api/accounts_bank_api_spec.rb +1 -1
  127. data/spec/api/assets_bank_api_spec.rb +1 -1
  128. data/spec/api/banks_bank_api_spec.rb +1 -1
  129. data/spec/api/customers_bank_api_spec.rb +1 -1
  130. data/spec/api/deposit_addresses_bank_api_spec.rb +1 -1
  131. data/spec/api/deposit_bank_accounts_bank_api_spec.rb +1 -1
  132. data/spec/api/external_bank_accounts_bank_api_spec.rb +1 -1
  133. data/spec/api/external_wallets_bank_api_spec.rb +1 -1
  134. data/spec/api/identity_verifications_bank_api_spec.rb +1 -1
  135. data/spec/api/prices_bank_api_spec.rb +1 -1
  136. data/spec/api/quotes_bank_api_spec.rb +1 -1
  137. data/spec/api/symbols_bank_api_spec.rb +1 -1
  138. data/spec/api/trades_bank_api_spec.rb +1 -1
  139. data/spec/api/transfers_bank_api_spec.rb +1 -1
  140. data/spec/api/workflows_bank_api_spec.rb +1 -1
  141. data/spec/api_client_spec.rb +1 -1
  142. data/spec/configuration_spec.rb +1 -1
  143. data/spec/models/account_bank_model_spec.rb +1 -1
  144. data/spec/models/account_list_bank_model_spec.rb +1 -1
  145. data/spec/models/account_state_bank_model_spec.rb +1 -1
  146. data/spec/models/account_type_bank_model_spec.rb +1 -1
  147. data/spec/models/asset_bank_model_spec.rb +1 -1
  148. data/spec/models/asset_list_bank_model_spec.rb +1 -1
  149. data/spec/models/asset_types_bank_model_spec.rb +1 -1
  150. data/spec/models/bank_bank_model_spec.rb +1 -1
  151. data/spec/models/bank_feature_bank_model_spec.rb +1 -1
  152. data/spec/models/bank_list_bank_model_spec.rb +1 -1
  153. data/spec/models/bank_type_bank_model_spec.rb +1 -1
  154. data/spec/models/customer_address_bank_model_spec.rb +1 -1
  155. data/spec/models/customer_bank_model_spec.rb +1 -1
  156. data/spec/models/customer_list_bank_model_spec.rb +1 -1
  157. data/spec/models/customer_name_bank_model_spec.rb +1 -1
  158. data/spec/models/customer_state_bank_model_spec.rb +1 -1
  159. data/spec/models/customer_type_bank_model_spec.rb +1 -1
  160. data/spec/models/deposit_address_bank_model_spec.rb +1 -1
  161. data/spec/models/deposit_address_format_bank_model_spec.rb +1 -1
  162. data/spec/models/deposit_address_list_bank_model_spec.rb +1 -1
  163. data/spec/models/deposit_address_state_bank_model_spec.rb +1 -1
  164. data/spec/models/deposit_bank_account_account_details_inner_bank_model_spec.rb +1 -1
  165. data/spec/models/deposit_bank_account_bank_model_spec.rb +1 -1
  166. data/spec/models/deposit_bank_account_counterparty_address_bank_model_spec.rb +1 -1
  167. data/spec/models/deposit_bank_account_list_bank_model_spec.rb +1 -1
  168. data/spec/models/deposit_bank_account_routing_details_inner_bank_model_spec.rb +1 -1
  169. data/spec/models/deposit_bank_account_routing_number_type_bank_model_spec.rb +1 -1
  170. data/spec/models/deposit_bank_account_state_bank_model_spec.rb +1 -1
  171. data/spec/models/error_response_bank_model_spec.rb +1 -1
  172. data/spec/models/external_bank_account_balances_bank_model_spec.rb +1 -1
  173. data/spec/models/external_bank_account_bank_model_spec.rb +1 -1
  174. data/spec/models/external_bank_account_kind_bank_model_spec.rb +1 -1
  175. data/spec/models/external_bank_account_list_bank_model_spec.rb +1 -1
  176. data/spec/models/external_bank_account_pii_inner_addresses_inner_bank_model_spec.rb +1 -1
  177. data/spec/models/external_bank_account_pii_inner_bank_model_spec.rb +1 -1
  178. data/spec/models/external_bank_account_state_bank_model_spec.rb +1 -1
  179. data/spec/models/external_wallet_bank_model_spec.rb +1 -1
  180. data/spec/models/external_wallet_environment_bank_model_spec.rb +1 -1
  181. data/spec/models/external_wallet_list_bank_model_spec.rb +1 -1
  182. data/spec/models/external_wallet_state_bank_model_spec.rb +1 -1
  183. data/spec/models/identity_verification_bank_model_spec.rb +1 -1
  184. data/spec/models/identity_verification_list_bank_model_spec.rb +1 -1
  185. data/spec/models/identity_verification_method_bank_model_spec.rb +1 -1
  186. data/spec/models/identity_verification_outcome_bank_model_spec.rb +1 -1
  187. data/spec/models/identity_verification_persona_state_bank_model_spec.rb +1 -1
  188. data/spec/models/identity_verification_state_bank_model_spec.rb +1 -1
  189. data/spec/models/identity_verification_type_bank_model_spec.rb +1 -1
  190. data/spec/models/identity_verification_with_details_all_of_bank_model_spec.rb +1 -1
  191. data/spec/models/identity_verification_with_details_bank_model_spec.rb +1 -1
  192. data/spec/models/patch_bank_bank_model_spec.rb +1 -1
  193. data/spec/models/patch_customer_bank_model_spec.rb +1 -1
  194. data/spec/models/patch_external_bank_account_bank_model_spec.rb +1 -1
  195. data/spec/models/post_account_bank_model_spec.rb +1 -1
  196. data/spec/models/post_bank_bank_model_spec.rb +1 -1
  197. data/spec/models/post_customer_address_bank_model_spec.rb +1 -1
  198. data/spec/models/post_customer_bank_model_spec.rb +1 -1
  199. data/spec/models/post_customer_name_bank_model_spec.rb +1 -1
  200. data/spec/models/post_deposit_address_bank_model_spec.rb +1 -1
  201. data/spec/models/post_deposit_bank_account_bank_model_spec.rb +1 -1
  202. data/spec/models/post_external_bank_account_bank_model_spec.rb +1 -1
  203. data/spec/models/post_external_bank_account_counterparty_address_bank_model_spec.rb +1 -1
  204. data/spec/models/post_external_bank_account_counterparty_bank_account_bank_model_spec.rb +1 -1
  205. data/spec/models/post_external_bank_account_counterparty_name_bank_model_spec.rb +1 -1
  206. data/spec/models/post_external_wallet_bank_model_spec.rb +1 -1
  207. data/spec/models/post_identification_number_bank_model_spec.rb +1 -1
  208. data/spec/models/post_identity_verification_address_bank_model_spec.rb +1 -1
  209. data/spec/models/post_identity_verification_bank_model_spec.rb +1 -1
  210. data/spec/models/post_identity_verification_name_bank_model_spec.rb +1 -1
  211. data/spec/models/post_quote_bank_model_spec.rb +1 -1
  212. data/spec/models/post_trade_bank_model_spec.rb +1 -1
  213. data/spec/models/post_transfer_bank_model_spec.rb +1 -1
  214. data/spec/models/post_workflow_bank_model_spec.rb +1 -1
  215. data/spec/models/quote_bank_model_spec.rb +1 -1
  216. data/spec/models/quote_list_bank_model_spec.rb +1 -1
  217. data/spec/models/quote_side_bank_model_spec.rb +1 -1
  218. data/spec/models/quote_type_bank_model_spec.rb +1 -1
  219. data/spec/models/symbol_price_bank_model_spec.rb +1 -1
  220. data/spec/models/trade_bank_model_spec.rb +1 -1
  221. data/spec/models/trade_list_bank_model_spec.rb +1 -1
  222. data/spec/models/trade_side_bank_model_spec.rb +1 -1
  223. data/spec/models/trade_state_bank_model_spec.rb +1 -1
  224. data/spec/models/trade_type_bank_model_spec.rb +1 -1
  225. data/spec/models/transfer_account_type_bank_model_spec.rb +1 -1
  226. data/spec/models/transfer_bank_model_spec.rb +1 -1
  227. data/spec/models/transfer_destination_account_bank_model_spec.rb +13 -1
  228. data/spec/models/transfer_list_bank_model_spec.rb +1 -1
  229. data/spec/models/transfer_side_bank_model_spec.rb +1 -1
  230. data/spec/models/transfer_source_account_bank_model_spec.rb +13 -1
  231. data/spec/models/transfer_state_bank_model_spec.rb +1 -1
  232. data/spec/models/transfer_type_bank_model_spec.rb +1 -1
  233. data/spec/models/verification_check_bank_model_spec.rb +1 -1
  234. data/spec/models/verification_check_state_bank_model_spec.rb +1 -1
  235. data/spec/models/verification_check_type_bank_model_spec.rb +1 -1
  236. data/spec/models/workflow_bank_model_spec.rb +1 -1
  237. data/spec/models/workflow_state_bank_model_spec.rb +1 -1
  238. data/spec/models/workflow_type_bank_model_spec.rb +1 -1
  239. data/spec/models/workflow_with_details_all_of_bank_model_spec.rb +1 -1
  240. data/spec/models/workflow_with_details_bank_model_spec.rb +1 -1
  241. data/spec/models/workflows_list_bank_model_spec.rb +1 -1
  242. data/spec/spec_helper.rb +1 -1
  243. data/vendor/bundle/ruby/3.2.0/cache/parser-3.3.0.2.gem +0 -0
  244. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/byebug-11.1.3/gem_make.out +5 -5
  245. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/ffi-1.16.3/gem_make.out +5 -5
  246. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/jaro_winkler-1.5.6/gem_make.out +5 -5
  247. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/psych-5.1.2/gem_make.out +5 -5
  248. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/racc-1.7.3/gem_make.out +5 -5
  249. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/stringio-3.1.0/gem_make.out +5 -5
  250. data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/lexer/literal.rb +1 -1
  251. data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/version.rb +1 -1
  252. data/vendor/bundle/ruby/3.2.0/specifications/{parser-3.3.0.0.gemspec → parser-3.3.0.2.gemspec} +4 -4
  253. metadata +83 -83
  254. data/vendor/bundle/ruby/3.2.0/cache/parser-3.3.0.0.gem +0 -0
  255. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/LICENSE.txt +0 -0
  256. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/bin/ruby-parse +0 -0
  257. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/bin/ruby-rewrite +0 -0
  258. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/gauntlet_parser.rb +0 -0
  259. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/all.rb +0 -0
  260. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ast/node.rb +0 -0
  261. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ast/processor.rb +0 -0
  262. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/base.rb +0 -0
  263. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/builders/default.rb +0 -0
  264. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/clobbering_error.rb +0 -0
  265. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/color.rb +0 -0
  266. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/context.rb +0 -0
  267. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/current.rb +0 -0
  268. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/current_arg_stack.rb +0 -0
  269. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/deprecation.rb +0 -0
  270. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/diagnostic/engine.rb +0 -0
  271. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/diagnostic.rb +0 -0
  272. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/lexer/dedenter.rb +0 -0
  273. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/lexer/explanation.rb +0 -0
  274. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/lexer/stack_state.rb +0 -0
  275. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/lexer-F0.rb +0 -0
  276. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/lexer-F1.rb +0 -0
  277. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/lexer-strings.rb +0 -0
  278. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/macruby.rb +0 -0
  279. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/max_numparam_stack.rb +0 -0
  280. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/messages.rb +0 -0
  281. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/meta.rb +0 -0
  282. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/rewriter.rb +0 -0
  283. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby18.rb +0 -0
  284. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby19.rb +0 -0
  285. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby20.rb +0 -0
  286. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby21.rb +0 -0
  287. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby22.rb +0 -0
  288. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby23.rb +0 -0
  289. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby24.rb +0 -0
  290. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby25.rb +0 -0
  291. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby26.rb +0 -0
  292. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby27.rb +0 -0
  293. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby28.rb +0 -0
  294. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby30.rb +0 -0
  295. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby31.rb +0 -0
  296. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby32.rb +0 -0
  297. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/ruby33.rb +0 -0
  298. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/rubymotion.rb +0 -0
  299. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/runner/ruby_parse.rb +0 -0
  300. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/runner/ruby_rewrite.rb +0 -0
  301. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/runner.rb +0 -0
  302. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/buffer.rb +0 -0
  303. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/comment/associator.rb +0 -0
  304. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/comment.rb +0 -0
  305. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/collection.rb +0 -0
  306. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/condition.rb +0 -0
  307. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/constant.rb +0 -0
  308. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/definition.rb +0 -0
  309. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/for.rb +0 -0
  310. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/heredoc.rb +0 -0
  311. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/index.rb +0 -0
  312. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/keyword.rb +0 -0
  313. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/method_definition.rb +0 -0
  314. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/objc_kwarg.rb +0 -0
  315. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/operator.rb +0 -0
  316. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/rescue_body.rb +0 -0
  317. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/send.rb +0 -0
  318. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/ternary.rb +0 -0
  319. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map/variable.rb +0 -0
  320. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/map.rb +0 -0
  321. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/range.rb +0 -0
  322. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/rewriter/action.rb +0 -0
  323. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/rewriter.rb +0 -0
  324. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/tree_rewriter/action.rb +0 -0
  325. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/source/tree_rewriter.rb +0 -0
  326. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/static_environment.rb +0 -0
  327. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/syntax_error.rb +0 -0
  328. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/tree_rewriter.rb +0 -0
  329. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser/variables_stack.rb +0 -0
  330. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/lib/parser.rb +0 -0
  331. /data/vendor/bundle/ruby/3.2.0/gems/{parser-3.3.0.0 → parser-3.3.0.2}/parser.gemspec +0 -0
@@ -3,7 +3,7 @@
3
3
 
4
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.sandbox.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. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/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://kb.cybrid.xyz/locally-running-the-web-demo-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), [iOS](https://github.com/Cybrid-app/cybrid-sdk-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](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.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.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.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 using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <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. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts: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\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read' ``` <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, 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) | | 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) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.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 | 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 | 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 | 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 `Organization` 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.
5
5
 
6
- The version of the OpenAPI document: v0.113.54
6
+ The version of the OpenAPI document: v0.113.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -22,11 +22,19 @@ module CybridApiBank
22
22
  # The type of transfer account; one of trading, fiat, external_bank_account, external_wallet, or one_time_address.
23
23
  attr_accessor :type
24
24
 
25
+ # The account's identifier.
26
+ attr_accessor :bank_guid
27
+
28
+ # The account's identifier.
29
+ attr_accessor :customer_guid
30
+
25
31
  # Attribute mapping from ruby-style variable name to JSON key.
26
32
  def self.attribute_map
27
33
  {
28
34
  :'guid' => :'guid',
29
- :'type' => :'type'
35
+ :'type' => :'type',
36
+ :'bank_guid' => :'bank_guid',
37
+ :'customer_guid' => :'customer_guid'
30
38
  }
31
39
  end
32
40
 
@@ -39,13 +47,17 @@ module CybridApiBank
39
47
  def self.openapi_types
40
48
  {
41
49
  :'guid' => :'String',
42
- :'type' => :'String'
50
+ :'type' => :'String',
51
+ :'bank_guid' => :'String',
52
+ :'customer_guid' => :'String'
43
53
  }
44
54
  end
45
55
 
46
56
  # List of attributes with nullable: true
47
57
  def self.openapi_nullable
48
58
  Set.new([
59
+ :'bank_guid',
60
+ :'customer_guid'
49
61
  ])
50
62
  end
51
63
 
@@ -71,6 +83,14 @@ module CybridApiBank
71
83
  if attributes.key?(:'type')
72
84
  self.type = attributes[:'type']
73
85
  end
86
+
87
+ if attributes.key?(:'bank_guid')
88
+ self.bank_guid = attributes[:'bank_guid']
89
+ end
90
+
91
+ if attributes.key?(:'customer_guid')
92
+ self.customer_guid = attributes[:'customer_guid']
93
+ end
74
94
  end
75
95
 
76
96
  # Show invalid properties with the reasons. Usually used together with valid?
@@ -85,6 +105,22 @@ module CybridApiBank
85
105
  invalid_properties.push('invalid value for "guid", the character length must be great than or equal to 32.')
86
106
  end
87
107
 
108
+ if !@bank_guid.nil? && @bank_guid.to_s.length > 32
109
+ invalid_properties.push('invalid value for "bank_guid", the character length must be smaller than or equal to 32.')
110
+ end
111
+
112
+ if !@bank_guid.nil? && @bank_guid.to_s.length < 32
113
+ invalid_properties.push('invalid value for "bank_guid", the character length must be great than or equal to 32.')
114
+ end
115
+
116
+ if !@customer_guid.nil? && @customer_guid.to_s.length > 32
117
+ invalid_properties.push('invalid value for "customer_guid", the character length must be smaller than or equal to 32.')
118
+ end
119
+
120
+ if !@customer_guid.nil? && @customer_guid.to_s.length < 32
121
+ invalid_properties.push('invalid value for "customer_guid", the character length must be great than or equal to 32.')
122
+ end
123
+
88
124
  invalid_properties
89
125
  end
90
126
 
@@ -93,6 +129,10 @@ module CybridApiBank
93
129
  def valid?
94
130
  return false if !@guid.nil? && @guid.to_s.length > 32
95
131
  return false if !@guid.nil? && @guid.to_s.length < 32
132
+ return false if !@bank_guid.nil? && @bank_guid.to_s.length > 32
133
+ return false if !@bank_guid.nil? && @bank_guid.to_s.length < 32
134
+ return false if !@customer_guid.nil? && @customer_guid.to_s.length > 32
135
+ return false if !@customer_guid.nil? && @customer_guid.to_s.length < 32
96
136
  true
97
137
  end
98
138
 
@@ -110,13 +150,43 @@ module CybridApiBank
110
150
  @guid = guid
111
151
  end
112
152
 
153
+ # Custom attribute writer method with validation
154
+ # @param [Object] bank_guid Value to be assigned
155
+ def bank_guid=(bank_guid)
156
+ if !bank_guid.nil? && bank_guid.to_s.length > 32
157
+ fail ArgumentError, 'invalid value for "bank_guid", the character length must be smaller than or equal to 32.'
158
+ end
159
+
160
+ if !bank_guid.nil? && bank_guid.to_s.length < 32
161
+ fail ArgumentError, 'invalid value for "bank_guid", the character length must be great than or equal to 32.'
162
+ end
163
+
164
+ @bank_guid = bank_guid
165
+ end
166
+
167
+ # Custom attribute writer method with validation
168
+ # @param [Object] customer_guid Value to be assigned
169
+ def customer_guid=(customer_guid)
170
+ if !customer_guid.nil? && customer_guid.to_s.length > 32
171
+ fail ArgumentError, 'invalid value for "customer_guid", the character length must be smaller than or equal to 32.'
172
+ end
173
+
174
+ if !customer_guid.nil? && customer_guid.to_s.length < 32
175
+ fail ArgumentError, 'invalid value for "customer_guid", the character length must be great than or equal to 32.'
176
+ end
177
+
178
+ @customer_guid = customer_guid
179
+ end
180
+
113
181
  # Checks equality by comparing each attribute.
114
182
  # @param [Object] Object to be compared
115
183
  def ==(o)
116
184
  return true if self.equal?(o)
117
185
  self.class == o.class &&
118
186
  guid == o.guid &&
119
- type == o.type
187
+ type == o.type &&
188
+ bank_guid == o.bank_guid &&
189
+ customer_guid == o.customer_guid
120
190
  end
121
191
 
122
192
  # @see the `==` method
@@ -128,7 +198,7 @@ module CybridApiBank
128
198
  # Calculates hash code according to all attributes.
129
199
  # @return [Integer] Hash code
130
200
  def hash
131
- [guid, type].hash
201
+ [guid, type, bank_guid, customer_guid].hash
132
202
  end
133
203
 
134
204
  # Builds the object from hash
@@ -3,7 +3,7 @@
3
3
 
4
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.sandbox.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. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/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://kb.cybrid.xyz/locally-running-the-web-demo-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), [iOS](https://github.com/Cybrid-app/cybrid-sdk-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](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.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.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.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 using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <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. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts: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\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read' ``` <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, 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) | | 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) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.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 | 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 | 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 | 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 `Organization` 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.
5
5
 
6
- The version of the OpenAPI document: v0.113.54
6
+ The version of the OpenAPI document: v0.113.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
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.sandbox.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. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/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://kb.cybrid.xyz/locally-running-the-web-demo-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), [iOS](https://github.com/Cybrid-app/cybrid-sdk-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](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.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.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.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 using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <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. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts: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\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read' ``` <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, 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) | | 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) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.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 | 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 | 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 | 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 `Organization` 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.
5
5
 
6
- The version of the OpenAPI document: v0.113.54
6
+ The version of the OpenAPI document: v0.113.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
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.sandbox.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. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/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://kb.cybrid.xyz/locally-running-the-web-demo-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), [iOS](https://github.com/Cybrid-app/cybrid-sdk-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](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.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.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.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 using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <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. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts: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\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read' ``` <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, 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) | | 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) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.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 | 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 | 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 | 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 `Organization` 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.
5
5
 
6
- The version of the OpenAPI document: v0.113.54
6
+ The version of the OpenAPI document: v0.113.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -22,11 +22,19 @@ module CybridApiBank
22
22
  # The type of transfer account; one of trading, fiat, external_bank_account, external_wallet, or one_time_address.
23
23
  attr_accessor :type
24
24
 
25
+ # The account's identifier.
26
+ attr_accessor :bank_guid
27
+
28
+ # The account's identifier.
29
+ attr_accessor :customer_guid
30
+
25
31
  # Attribute mapping from ruby-style variable name to JSON key.
26
32
  def self.attribute_map
27
33
  {
28
34
  :'guid' => :'guid',
29
- :'type' => :'type'
35
+ :'type' => :'type',
36
+ :'bank_guid' => :'bank_guid',
37
+ :'customer_guid' => :'customer_guid'
30
38
  }
31
39
  end
32
40
 
@@ -39,13 +47,17 @@ module CybridApiBank
39
47
  def self.openapi_types
40
48
  {
41
49
  :'guid' => :'String',
42
- :'type' => :'String'
50
+ :'type' => :'String',
51
+ :'bank_guid' => :'String',
52
+ :'customer_guid' => :'String'
43
53
  }
44
54
  end
45
55
 
46
56
  # List of attributes with nullable: true
47
57
  def self.openapi_nullable
48
58
  Set.new([
59
+ :'bank_guid',
60
+ :'customer_guid'
49
61
  ])
50
62
  end
51
63
 
@@ -71,6 +83,14 @@ module CybridApiBank
71
83
  if attributes.key?(:'type')
72
84
  self.type = attributes[:'type']
73
85
  end
86
+
87
+ if attributes.key?(:'bank_guid')
88
+ self.bank_guid = attributes[:'bank_guid']
89
+ end
90
+
91
+ if attributes.key?(:'customer_guid')
92
+ self.customer_guid = attributes[:'customer_guid']
93
+ end
74
94
  end
75
95
 
76
96
  # Show invalid properties with the reasons. Usually used together with valid?
@@ -85,6 +105,22 @@ module CybridApiBank
85
105
  invalid_properties.push('invalid value for "guid", the character length must be great than or equal to 32.')
86
106
  end
87
107
 
108
+ if !@bank_guid.nil? && @bank_guid.to_s.length > 32
109
+ invalid_properties.push('invalid value for "bank_guid", the character length must be smaller than or equal to 32.')
110
+ end
111
+
112
+ if !@bank_guid.nil? && @bank_guid.to_s.length < 32
113
+ invalid_properties.push('invalid value for "bank_guid", the character length must be great than or equal to 32.')
114
+ end
115
+
116
+ if !@customer_guid.nil? && @customer_guid.to_s.length > 32
117
+ invalid_properties.push('invalid value for "customer_guid", the character length must be smaller than or equal to 32.')
118
+ end
119
+
120
+ if !@customer_guid.nil? && @customer_guid.to_s.length < 32
121
+ invalid_properties.push('invalid value for "customer_guid", the character length must be great than or equal to 32.')
122
+ end
123
+
88
124
  invalid_properties
89
125
  end
90
126
 
@@ -93,6 +129,10 @@ module CybridApiBank
93
129
  def valid?
94
130
  return false if !@guid.nil? && @guid.to_s.length > 32
95
131
  return false if !@guid.nil? && @guid.to_s.length < 32
132
+ return false if !@bank_guid.nil? && @bank_guid.to_s.length > 32
133
+ return false if !@bank_guid.nil? && @bank_guid.to_s.length < 32
134
+ return false if !@customer_guid.nil? && @customer_guid.to_s.length > 32
135
+ return false if !@customer_guid.nil? && @customer_guid.to_s.length < 32
96
136
  true
97
137
  end
98
138
 
@@ -110,13 +150,43 @@ module CybridApiBank
110
150
  @guid = guid
111
151
  end
112
152
 
153
+ # Custom attribute writer method with validation
154
+ # @param [Object] bank_guid Value to be assigned
155
+ def bank_guid=(bank_guid)
156
+ if !bank_guid.nil? && bank_guid.to_s.length > 32
157
+ fail ArgumentError, 'invalid value for "bank_guid", the character length must be smaller than or equal to 32.'
158
+ end
159
+
160
+ if !bank_guid.nil? && bank_guid.to_s.length < 32
161
+ fail ArgumentError, 'invalid value for "bank_guid", the character length must be great than or equal to 32.'
162
+ end
163
+
164
+ @bank_guid = bank_guid
165
+ end
166
+
167
+ # Custom attribute writer method with validation
168
+ # @param [Object] customer_guid Value to be assigned
169
+ def customer_guid=(customer_guid)
170
+ if !customer_guid.nil? && customer_guid.to_s.length > 32
171
+ fail ArgumentError, 'invalid value for "customer_guid", the character length must be smaller than or equal to 32.'
172
+ end
173
+
174
+ if !customer_guid.nil? && customer_guid.to_s.length < 32
175
+ fail ArgumentError, 'invalid value for "customer_guid", the character length must be great than or equal to 32.'
176
+ end
177
+
178
+ @customer_guid = customer_guid
179
+ end
180
+
113
181
  # Checks equality by comparing each attribute.
114
182
  # @param [Object] Object to be compared
115
183
  def ==(o)
116
184
  return true if self.equal?(o)
117
185
  self.class == o.class &&
118
186
  guid == o.guid &&
119
- type == o.type
187
+ type == o.type &&
188
+ bank_guid == o.bank_guid &&
189
+ customer_guid == o.customer_guid
120
190
  end
121
191
 
122
192
  # @see the `==` method
@@ -128,7 +198,7 @@ module CybridApiBank
128
198
  # Calculates hash code according to all attributes.
129
199
  # @return [Integer] Hash code
130
200
  def hash
131
- [guid, type].hash
201
+ [guid, type, bank_guid, customer_guid].hash
132
202
  end
133
203
 
134
204
  # Builds the object from hash
@@ -3,7 +3,7 @@
3
3
 
4
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.sandbox.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. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/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://kb.cybrid.xyz/locally-running-the-web-demo-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), [iOS](https://github.com/Cybrid-app/cybrid-sdk-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](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.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.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.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 using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <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. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts: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\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read' ``` <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, 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) | | 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) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.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 | 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 | 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 | 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 `Organization` 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.
5
5
 
6
- The version of the OpenAPI document: v0.113.54
6
+ The version of the OpenAPI document: v0.113.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
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.sandbox.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. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/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://kb.cybrid.xyz/locally-running-the-web-demo-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), [iOS](https://github.com/Cybrid-app/cybrid-sdk-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](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.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.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.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 using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <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. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts: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\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read' ``` <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, 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) | | 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) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.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 | 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 | 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 | 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 `Organization` 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.
5
5
 
6
- The version of the OpenAPI document: v0.113.54
6
+ The version of the OpenAPI document: v0.113.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
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.sandbox.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. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/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://kb.cybrid.xyz/locally-running-the-web-demo-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), [iOS](https://github.com/Cybrid-app/cybrid-sdk-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](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.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.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.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 using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <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. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts: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\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read' ``` <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, 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) | | 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) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.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 | 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 | 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 | 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 `Organization` 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.
5
5
 
6
- The version of the OpenAPI document: v0.113.54
6
+ The version of the OpenAPI document: v0.113.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0