cybrid_api_bank_ruby 0.98.2 → 0.100.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (233) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +2 -2
  3. data/README.md +7 -5
  4. data/cybrid_api_bank_ruby.gemspec +1 -1
  5. data/docs/CustomersBankApi.md +75 -0
  6. data/docs/DepositAddressBankModel.md +3 -1
  7. data/docs/DepositAddressesBankApi.md +3 -1
  8. data/docs/PatchCustomerBankModel.md +18 -0
  9. data/docs/PostDepositAddressBankModel.md +3 -1
  10. data/lib/cybrid_api_bank_ruby/api/accounts_bank_api.rb +1 -1
  11. data/lib/cybrid_api_bank_ruby/api/assets_bank_api.rb +1 -1
  12. data/lib/cybrid_api_bank_ruby/api/banks_bank_api.rb +1 -1
  13. data/lib/cybrid_api_bank_ruby/api/customers_bank_api.rb +75 -1
  14. data/lib/cybrid_api_bank_ruby/api/deposit_addresses_bank_api.rb +4 -1
  15. data/lib/cybrid_api_bank_ruby/api/external_bank_accounts_bank_api.rb +1 -1
  16. data/lib/cybrid_api_bank_ruby/api/external_wallets_bank_api.rb +1 -1
  17. data/lib/cybrid_api_bank_ruby/api/identity_verifications_bank_api.rb +1 -1
  18. data/lib/cybrid_api_bank_ruby/api/prices_bank_api.rb +1 -1
  19. data/lib/cybrid_api_bank_ruby/api/quotes_bank_api.rb +1 -1
  20. data/lib/cybrid_api_bank_ruby/api/symbols_bank_api.rb +1 -1
  21. data/lib/cybrid_api_bank_ruby/api/trades_bank_api.rb +1 -1
  22. data/lib/cybrid_api_bank_ruby/api/transfers_bank_api.rb +1 -1
  23. data/lib/cybrid_api_bank_ruby/api/workflows_bank_api.rb +1 -1
  24. data/lib/cybrid_api_bank_ruby/api_client.rb +1 -1
  25. data/lib/cybrid_api_bank_ruby/api_error.rb +1 -1
  26. data/lib/cybrid_api_bank_ruby/configuration.rb +1 -1
  27. data/lib/cybrid_api_bank_ruby/models/account_bank_model.rb +1 -1
  28. data/lib/cybrid_api_bank_ruby/models/account_list_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/bank_bank_model.rb +1 -1
  32. data/lib/cybrid_api_bank_ruby/models/bank_list_bank_model.rb +1 -1
  33. data/lib/cybrid_api_bank_ruby/models/customer_address_bank_model.rb +1 -1
  34. data/lib/cybrid_api_bank_ruby/models/customer_bank_model.rb +1 -1
  35. data/lib/cybrid_api_bank_ruby/models/customer_list_bank_model.rb +1 -1
  36. data/lib/cybrid_api_bank_ruby/models/customer_name_bank_model.rb +1 -1
  37. data/lib/cybrid_api_bank_ruby/models/deposit_address_bank_model.rb +18 -5
  38. data/lib/cybrid_api_bank_ruby/models/deposit_address_list_bank_model.rb +1 -1
  39. data/lib/cybrid_api_bank_ruby/models/error_response_bank_model.rb +1 -1
  40. data/lib/cybrid_api_bank_ruby/models/external_bank_account_bank_model.rb +1 -1
  41. data/lib/cybrid_api_bank_ruby/models/external_bank_account_list_bank_model.rb +1 -1
  42. data/lib/cybrid_api_bank_ruby/models/external_wallet_bank_model.rb +1 -1
  43. data/lib/cybrid_api_bank_ruby/models/external_wallet_list_bank_model.rb +1 -1
  44. data/lib/cybrid_api_bank_ruby/models/identity_verification_bank_model.rb +1 -1
  45. data/lib/cybrid_api_bank_ruby/models/identity_verification_list_bank_model.rb +1 -1
  46. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_all_of_bank_model.rb +1 -1
  47. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_bank_model.rb +1 -1
  48. data/lib/cybrid_api_bank_ruby/models/list_request_owner_bank_model.rb +1 -1
  49. data/lib/cybrid_api_bank_ruby/models/patch_bank_bank_model.rb +1 -1
  50. data/lib/cybrid_api_bank_ruby/models/patch_customer_bank_model.rb +254 -0
  51. data/lib/cybrid_api_bank_ruby/models/patch_external_bank_account_bank_model.rb +1 -1
  52. data/lib/cybrid_api_bank_ruby/models/post_account_bank_model.rb +1 -1
  53. data/lib/cybrid_api_bank_ruby/models/post_bank_bank_model.rb +1 -1
  54. data/lib/cybrid_api_bank_ruby/models/post_customer_address_bank_model.rb +1 -1
  55. data/lib/cybrid_api_bank_ruby/models/post_customer_bank_model.rb +1 -1
  56. data/lib/cybrid_api_bank_ruby/models/post_customer_name_bank_model.rb +1 -1
  57. data/lib/cybrid_api_bank_ruby/models/post_deposit_address_bank_model.rb +18 -5
  58. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_bank_model.rb +1 -1
  59. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_address_bank_model.rb +1 -1
  60. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_bank_account_bank_model.rb +1 -1
  61. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_name_bank_model.rb +1 -1
  62. data/lib/cybrid_api_bank_ruby/models/post_external_wallet_bank_model.rb +1 -1
  63. data/lib/cybrid_api_bank_ruby/models/post_identification_number_bank_model.rb +1 -1
  64. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_address_bank_model.rb +1 -1
  65. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_bank_model.rb +1 -1
  66. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_name_bank_model.rb +1 -1
  67. data/lib/cybrid_api_bank_ruby/models/post_quote_bank_model.rb +1 -1
  68. data/lib/cybrid_api_bank_ruby/models/post_trade_bank_model.rb +1 -1
  69. data/lib/cybrid_api_bank_ruby/models/post_transfer_bank_model.rb +1 -1
  70. data/lib/cybrid_api_bank_ruby/models/post_workflow_bank_model.rb +1 -1
  71. data/lib/cybrid_api_bank_ruby/models/quote_bank_model.rb +1 -1
  72. data/lib/cybrid_api_bank_ruby/models/quote_list_bank_model.rb +1 -1
  73. data/lib/cybrid_api_bank_ruby/models/symbol_price_bank_model.rb +1 -1
  74. data/lib/cybrid_api_bank_ruby/models/trade_bank_model.rb +1 -1
  75. data/lib/cybrid_api_bank_ruby/models/trade_list_bank_model.rb +1 -1
  76. data/lib/cybrid_api_bank_ruby/models/transfer_bank_model.rb +1 -1
  77. data/lib/cybrid_api_bank_ruby/models/transfer_destination_account_bank_model.rb +1 -1
  78. data/lib/cybrid_api_bank_ruby/models/transfer_list_bank_model.rb +1 -1
  79. data/lib/cybrid_api_bank_ruby/models/transfer_source_account_bank_model.rb +1 -1
  80. data/lib/cybrid_api_bank_ruby/models/workflow_bank_model.rb +1 -1
  81. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_all_of_bank_model.rb +1 -1
  82. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_bank_model.rb +1 -1
  83. data/lib/cybrid_api_bank_ruby/models/workflows_list_bank_model.rb +1 -1
  84. data/lib/cybrid_api_bank_ruby/version.rb +2 -2
  85. data/lib/cybrid_api_bank_ruby.rb +2 -1
  86. data/spec/api/accounts_bank_api_spec.rb +1 -1
  87. data/spec/api/assets_bank_api_spec.rb +1 -1
  88. data/spec/api/banks_bank_api_spec.rb +1 -1
  89. data/spec/api/customers_bank_api_spec.rb +14 -1
  90. data/spec/api/deposit_addresses_bank_api_spec.rb +2 -1
  91. data/spec/api/external_bank_accounts_bank_api_spec.rb +1 -1
  92. data/spec/api/external_wallets_bank_api_spec.rb +1 -1
  93. data/spec/api/identity_verifications_bank_api_spec.rb +1 -1
  94. data/spec/api/prices_bank_api_spec.rb +1 -1
  95. data/spec/api/quotes_bank_api_spec.rb +1 -1
  96. data/spec/api/symbols_bank_api_spec.rb +1 -1
  97. data/spec/api/trades_bank_api_spec.rb +1 -1
  98. data/spec/api/transfers_bank_api_spec.rb +1 -1
  99. data/spec/api/workflows_bank_api_spec.rb +1 -1
  100. data/spec/api_client_spec.rb +1 -1
  101. data/spec/configuration_spec.rb +1 -1
  102. data/spec/models/account_bank_model_spec.rb +1 -1
  103. data/spec/models/account_list_bank_model_spec.rb +1 -1
  104. data/spec/models/asset_bank_model_spec.rb +1 -1
  105. data/spec/models/asset_list_bank_model_spec.rb +1 -1
  106. data/spec/models/bank_bank_model_spec.rb +1 -1
  107. data/spec/models/bank_list_bank_model_spec.rb +1 -1
  108. data/spec/models/customer_address_bank_model_spec.rb +1 -1
  109. data/spec/models/customer_bank_model_spec.rb +1 -1
  110. data/spec/models/customer_list_bank_model_spec.rb +1 -1
  111. data/spec/models/customer_name_bank_model_spec.rb +1 -1
  112. data/spec/models/deposit_address_bank_model_spec.rb +7 -1
  113. data/spec/models/deposit_address_list_bank_model_spec.rb +1 -1
  114. data/spec/models/error_response_bank_model_spec.rb +1 -1
  115. data/spec/models/external_bank_account_bank_model_spec.rb +1 -1
  116. data/spec/models/external_bank_account_list_bank_model_spec.rb +1 -1
  117. data/spec/models/external_wallet_bank_model_spec.rb +1 -1
  118. data/spec/models/external_wallet_list_bank_model_spec.rb +1 -1
  119. data/spec/models/identity_verification_bank_model_spec.rb +1 -1
  120. data/spec/models/identity_verification_list_bank_model_spec.rb +1 -1
  121. data/spec/models/identity_verification_with_details_all_of_bank_model_spec.rb +1 -1
  122. data/spec/models/identity_verification_with_details_bank_model_spec.rb +1 -1
  123. data/spec/models/list_request_owner_bank_model_spec.rb +1 -1
  124. data/spec/models/patch_bank_bank_model_spec.rb +1 -1
  125. data/spec/models/patch_customer_bank_model_spec.rb +38 -0
  126. data/spec/models/patch_external_bank_account_bank_model_spec.rb +1 -1
  127. data/spec/models/post_account_bank_model_spec.rb +1 -1
  128. data/spec/models/post_bank_bank_model_spec.rb +1 -1
  129. data/spec/models/post_customer_address_bank_model_spec.rb +1 -1
  130. data/spec/models/post_customer_bank_model_spec.rb +1 -1
  131. data/spec/models/post_customer_name_bank_model_spec.rb +1 -1
  132. data/spec/models/post_deposit_address_bank_model_spec.rb +7 -1
  133. data/spec/models/post_external_bank_account_bank_model_spec.rb +1 -1
  134. data/spec/models/post_external_bank_account_counterparty_address_bank_model_spec.rb +1 -1
  135. data/spec/models/post_external_bank_account_counterparty_bank_account_bank_model_spec.rb +1 -1
  136. data/spec/models/post_external_bank_account_counterparty_name_bank_model_spec.rb +1 -1
  137. data/spec/models/post_external_wallet_bank_model_spec.rb +1 -1
  138. data/spec/models/post_identification_number_bank_model_spec.rb +1 -1
  139. data/spec/models/post_identity_verification_address_bank_model_spec.rb +1 -1
  140. data/spec/models/post_identity_verification_bank_model_spec.rb +1 -1
  141. data/spec/models/post_identity_verification_name_bank_model_spec.rb +1 -1
  142. data/spec/models/post_quote_bank_model_spec.rb +1 -1
  143. data/spec/models/post_trade_bank_model_spec.rb +1 -1
  144. data/spec/models/post_transfer_bank_model_spec.rb +1 -1
  145. data/spec/models/post_workflow_bank_model_spec.rb +1 -1
  146. data/spec/models/quote_bank_model_spec.rb +1 -1
  147. data/spec/models/quote_list_bank_model_spec.rb +1 -1
  148. data/spec/models/symbol_price_bank_model_spec.rb +1 -1
  149. data/spec/models/trade_bank_model_spec.rb +1 -1
  150. data/spec/models/trade_list_bank_model_spec.rb +1 -1
  151. data/spec/models/transfer_bank_model_spec.rb +1 -1
  152. data/spec/models/transfer_destination_account_bank_model_spec.rb +1 -1
  153. data/spec/models/transfer_list_bank_model_spec.rb +1 -1
  154. data/spec/models/transfer_source_account_bank_model_spec.rb +1 -1
  155. data/spec/models/workflow_bank_model_spec.rb +1 -1
  156. data/spec/models/workflow_with_details_all_of_bank_model_spec.rb +1 -1
  157. data/spec/models/workflow_with_details_bank_model_spec.rb +1 -1
  158. data/spec/models/workflows_list_bank_model_spec.rb +1 -1
  159. data/spec/spec_helper.rb +1 -1
  160. data/vendor/bundle/ruby/3.2.0/cache/psych-5.1.1.gem +0 -0
  161. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/byebug-11.1.3/gem_make.out +5 -5
  162. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/ffi-1.16.3/gem_make.out +5 -5
  163. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/jaro_winkler-1.5.6/gem_make.out +5 -5
  164. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/{psych-5.1.0 → psych-5.1.1}/gem_make.out +18 -18
  165. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/{psych-5.1.0 → psych-5.1.1}/psych.so +0 -0
  166. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/racc-1.7.1/gem_make.out +5 -5
  167. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/stringio-3.0.8/gem_make.out +5 -5
  168. data/vendor/bundle/ruby/3.2.0/gems/psych-5.1.1/CONTRIBUTING.md +24 -0
  169. data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/versions.rb +2 -2
  170. data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych.rb +23 -19
  171. data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych.so +0 -0
  172. data/vendor/bundle/ruby/3.2.0/specifications/{psych-5.1.0.gemspec → psych-5.1.1.gemspec} +4 -4
  173. metadata +66 -68
  174. data/vendor/bundle/ruby/3.2.0/cache/psych-5.1.0.gem +0 -0
  175. data/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/.gitignore +0 -16
  176. data/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/Gemfile +0 -9
  177. data/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/Mavenfile +0 -7
  178. data/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/Rakefile +0 -41
  179. data/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/bin/console +0 -7
  180. data/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/bin/setup +0 -6
  181. data/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/psych.gemspec +0 -67
  182. /data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/{psych-5.1.0 → psych-5.1.1}/gem.build_complete +0 -0
  183. /data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/{psych-5.1.0 → psych-5.1.1}/mkmf.log +0 -0
  184. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/LICENSE +0 -0
  185. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/README.md +0 -0
  186. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/Makefile +0 -0
  187. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/depend +0 -0
  188. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/extconf.rb +0 -0
  189. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/psych.c +0 -0
  190. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/psych.h +0 -0
  191. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/psych_emitter.c +0 -0
  192. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/psych_emitter.h +0 -0
  193. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/psych_parser.c +0 -0
  194. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/psych_parser.h +0 -0
  195. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/psych_to_ruby.c +0 -0
  196. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/psych_to_ruby.h +0 -0
  197. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/psych_yaml_tree.c +0 -0
  198. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/ext/psych/psych_yaml_tree.h +0 -0
  199. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/class_loader.rb +0 -0
  200. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/coder.rb +0 -0
  201. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/core_ext.rb +0 -0
  202. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/exception.rb +0 -0
  203. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/handler.rb +0 -0
  204. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/handlers/document_stream.rb +0 -0
  205. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/handlers/recorder.rb +0 -0
  206. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/json/ruby_events.rb +0 -0
  207. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/json/stream.rb +0 -0
  208. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/json/tree_builder.rb +0 -0
  209. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/json/yaml_events.rb +0 -0
  210. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/nodes/alias.rb +0 -0
  211. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/nodes/document.rb +0 -0
  212. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/nodes/mapping.rb +0 -0
  213. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/nodes/node.rb +0 -0
  214. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/nodes/scalar.rb +0 -0
  215. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/nodes/sequence.rb +0 -0
  216. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/nodes/stream.rb +0 -0
  217. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/nodes.rb +0 -0
  218. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/omap.rb +0 -0
  219. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/parser.rb +0 -0
  220. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/scalar_scanner.rb +0 -0
  221. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/set.rb +0 -0
  222. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/stream.rb +0 -0
  223. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/streaming.rb +0 -0
  224. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/syntax_error.rb +0 -0
  225. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/tree_builder.rb +0 -0
  226. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/visitors/depth_first.rb +0 -0
  227. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/visitors/emitter.rb +0 -0
  228. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/visitors/json_tree.rb +0 -0
  229. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/visitors/to_ruby.rb +0 -0
  230. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/visitors/visitor.rb +0 -0
  231. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/visitors/yaml_tree.rb +0 -0
  232. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/visitors.rb +0 -0
  233. /data/vendor/bundle/ruby/3.2.0/gems/{psych-5.1.0 → psych-5.1.1}/lib/psych/y.rb +0 -0
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 304eb339972e864aeb1fb8ca2525e5891c1dfbc06c8b159df0b81e7c78823a43
4
- data.tar.gz: 4ea3dd0e66956dbbf51a62c15f543a1056a6bb64a07bbf878af10bb61167411a
3
+ metadata.gz: 33f7e02e0acbd41a033ca893bec8988aac9455e9cb42c2126be011ff7b240a93
4
+ data.tar.gz: 11b7e06b94f0b8bdf6cb23098aa804ec683887d93e8f564754841f78f00e688a
5
5
  SHA512:
6
- metadata.gz: ab31d2710011182336d16d497cfb98880aa7bb6f8aca479584a542258fabcb7004f605feb941de08901dda071a2c5b6d341b8816c0c6474efc655c0b5cb25df4
7
- data.tar.gz: 5bfeb48d4e511a05ae0fb667b03ef23b1e1eb9c543f5c16a21b35083061486919e2c13a9a12838ea798f6028937df3de6f5337bfb69cf35877094d9f493ce011
6
+ metadata.gz: bf868e05e4f8306695274fdaf6ecf26b0c86d2eb6f12da71070032038a61006df57d1cc22983e2cd27eba360ab2ff3a92fde41283b2d67a9970f5c6e2f9d9c95
7
+ data.tar.gz: 1814f865be10d91620b23ad65ed90c22f316aa32af55b7a257f2ba73fbb8ea6253d583c27fb6893f264ea7166db90bb533bcf032a5dde8571d23bd9714d10f4e
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- cybrid_api_bank_ruby (0.98.2)
4
+ cybrid_api_bank_ruby (0.100.0)
5
5
  typhoeus (~> 1.0, >= 1.0.1)
6
6
 
7
7
  GEM
@@ -26,7 +26,7 @@ GEM
26
26
  pry-byebug (3.10.1)
27
27
  byebug (~> 11.0)
28
28
  pry (>= 0.13, < 0.15)
29
- psych (5.1.0)
29
+ psych (5.1.1)
30
30
  stringio
31
31
  racc (1.7.1)
32
32
  rainbow (3.1.1)
data/README.md CHANGED
@@ -149,8 +149,8 @@ An `Organization` can have multiple `banks`, in either `Sandbox` or `Production`
149
149
 
150
150
  This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
151
151
 
152
- - API version: v0.98.2
153
- - Package version: 0.98.2
152
+ - API version: v0.100.0
153
+ - Package version: 0.100.0
154
154
  - Build package: org.openapitools.codegen.languages.RubyClientCodegen
155
155
 
156
156
  ## Installation
@@ -166,16 +166,16 @@ gem build cybrid_api_bank_ruby.gemspec
166
166
  Then either install the gem locally:
167
167
 
168
168
  ```shell
169
- gem install ./cybrid_api_bank_ruby-0.98.2.gem
169
+ gem install ./cybrid_api_bank_ruby-0.100.0.gem
170
170
  ```
171
171
 
172
- (for development, run `gem install --dev ./cybrid_api_bank_ruby-0.98.2.gem` to install the development dependencies)
172
+ (for development, run `gem install --dev ./cybrid_api_bank_ruby-0.100.0.gem` to install the development dependencies)
173
173
 
174
174
  or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
175
175
 
176
176
  Finally add this to the Gemfile:
177
177
 
178
- gem 'cybrid_api_bank_ruby', '~> 0.98.2'
178
+ gem 'cybrid_api_bank_ruby', '~> 0.100.0'
179
179
 
180
180
  ### Install from Git
181
181
 
@@ -238,6 +238,7 @@ Class | Method | HTTP request | Description
238
238
  *CybridApiBank::CustomersBankApi* | [**create_customer**](docs/CustomersBankApi.md#create_customer) | **POST** /api/customers | Create Customer
239
239
  *CybridApiBank::CustomersBankApi* | [**get_customer**](docs/CustomersBankApi.md#get_customer) | **GET** /api/customers/{customer_guid} | Get Customer
240
240
  *CybridApiBank::CustomersBankApi* | [**list_customers**](docs/CustomersBankApi.md#list_customers) | **GET** /api/customers | Get customers list
241
+ *CybridApiBank::CustomersBankApi* | [**update_customer**](docs/CustomersBankApi.md#update_customer) | **PATCH** /api/customers/{customer_guid} | Patch Customer
241
242
  *CybridApiBank::DepositAddressesBankApi* | [**create_deposit_address**](docs/DepositAddressesBankApi.md#create_deposit_address) | **POST** /api/deposit_addresses | Create Deposit Address
242
243
  *CybridApiBank::DepositAddressesBankApi* | [**get_deposit_address**](docs/DepositAddressesBankApi.md#get_deposit_address) | **GET** /api/deposit_addresses/{deposit_address_guid} | Get Deposit Address
243
244
  *CybridApiBank::DepositAddressesBankApi* | [**list_deposit_addresses**](docs/DepositAddressesBankApi.md#list_deposit_addresses) | **GET** /api/deposit_addresses | List Deposit Addresses
@@ -294,6 +295,7 @@ Class | Method | HTTP request | Description
294
295
  - [CybridApiBank::IdentityVerificationWithDetailsBankModel](docs/IdentityVerificationWithDetailsBankModel.md)
295
296
  - [CybridApiBank::ListRequestOwnerBankModel](docs/ListRequestOwnerBankModel.md)
296
297
  - [CybridApiBank::PatchBankBankModel](docs/PatchBankBankModel.md)
298
+ - [CybridApiBank::PatchCustomerBankModel](docs/PatchCustomerBankModel.md)
297
299
  - [CybridApiBank::PatchExternalBankAccountBankModel](docs/PatchExternalBankAccountBankModel.md)
298
300
  - [CybridApiBank::PostAccountBankModel](docs/PostAccountBankModel.md)
299
301
  - [CybridApiBank::PostBankBankModel](docs/PostBankBankModel.md)
@@ -5,7 +5,7 @@
5
5
 
6
6
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.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\" }' -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' ``` <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.
7
7
 
8
- The version of the OpenAPI document: v0.98.2
8
+ The version of the OpenAPI document: v0.100.0
9
9
  Contact: support@cybrid.app
10
10
  Generated by: https://openapi-generator.tech
11
11
  OpenAPI Generator version: 6.0.0
@@ -7,6 +7,7 @@ All URIs are relative to *https://bank.sandbox.cybrid.app*
7
7
  | [**create_customer**](CustomersBankApi.md#create_customer) | **POST** /api/customers | Create Customer |
8
8
  | [**get_customer**](CustomersBankApi.md#get_customer) | **GET** /api/customers/{customer_guid} | Get Customer |
9
9
  | [**list_customers**](CustomersBankApi.md#list_customers) | **GET** /api/customers | Get customers list |
10
+ | [**update_customer**](CustomersBankApi.md#update_customer) | **PATCH** /api/customers/{customer_guid} | Patch Customer |
10
11
 
11
12
 
12
13
  ## create_customer
@@ -236,3 +237,77 @@ end
236
237
  - **Content-Type**: Not defined
237
238
  - **Accept**: application/json
238
239
 
240
+
241
+ ## update_customer
242
+
243
+ > <CustomerBankModel> update_customer(customer_guid, patch_customer_bank_model)
244
+
245
+ Patch Customer
246
+
247
+ Update a customer. Required scope: **customers:write**
248
+
249
+ ### Examples
250
+
251
+ ```ruby
252
+ require 'time'
253
+ require 'cybrid_api_bank_ruby'
254
+ # setup authorization
255
+ CybridApiBank.configure do |config|
256
+ # Configure Bearer authorization (JWT): BearerAuth
257
+ config.access_token = 'YOUR_BEARER_TOKEN'
258
+
259
+ # Configure OAuth2 access token for authorization: oauth2
260
+ config.access_token = 'YOUR ACCESS TOKEN'
261
+ end
262
+
263
+ api_instance = CybridApiBank::CustomersBankApi.new
264
+ customer_guid = 'customer_guid_example' # String | Identifier for the customer.
265
+ patch_customer_bank_model = CybridApiBank::PatchCustomerBankModel.new # PatchCustomerBankModel |
266
+
267
+ begin
268
+ # Patch Customer
269
+ result = api_instance.update_customer(customer_guid, patch_customer_bank_model)
270
+ p result
271
+ rescue CybridApiBank::ApiError => e
272
+ puts "Error when calling CustomersBankApi->update_customer: #{e}"
273
+ end
274
+ ```
275
+
276
+ #### Using the update_customer_with_http_info variant
277
+
278
+ This returns an Array which contains the response data, status code and headers.
279
+
280
+ > <Array(<CustomerBankModel>, Integer, Hash)> update_customer_with_http_info(customer_guid, patch_customer_bank_model)
281
+
282
+ ```ruby
283
+ begin
284
+ # Patch Customer
285
+ data, status_code, headers = api_instance.update_customer_with_http_info(customer_guid, patch_customer_bank_model)
286
+ p status_code # => 2xx
287
+ p headers # => { ... }
288
+ p data # => <CustomerBankModel>
289
+ rescue CybridApiBank::ApiError => e
290
+ puts "Error when calling CustomersBankApi->update_customer_with_http_info: #{e}"
291
+ end
292
+ ```
293
+
294
+ ### Parameters
295
+
296
+ | Name | Type | Description | Notes |
297
+ | ---- | ---- | ----------- | ----- |
298
+ | **customer_guid** | **String** | Identifier for the customer. | |
299
+ | **patch_customer_bank_model** | [**PatchCustomerBankModel**](PatchCustomerBankModel.md) | | |
300
+
301
+ ### Return type
302
+
303
+ [**CustomerBankModel**](CustomerBankModel.md)
304
+
305
+ ### Authorization
306
+
307
+ [BearerAuth](../README.md#BearerAuth), [oauth2](../README.md#oauth2)
308
+
309
+ ### HTTP request headers
310
+
311
+ - **Content-Type**: application/json
312
+ - **Accept**: application/json
313
+
@@ -14,6 +14,7 @@
14
14
  | **address** | **String** | The blockchain address. | [optional] |
15
15
  | **format** | **String** | The blockchain address format. | [optional] |
16
16
  | **tag** | **String** | The blockchain address tag. | [optional] |
17
+ | **labels** | **Array&lt;String&gt;** | The labels associated with the address. | [optional] |
17
18
 
18
19
  ## Example
19
20
 
@@ -30,7 +31,8 @@ instance = CybridApiBank::DepositAddressBankModel.new(
30
31
  state: null,
31
32
  address: null,
32
33
  format: null,
33
- tag: null
34
+ tag: null,
35
+ labels: null
34
36
  )
35
37
  ```
36
38
 
@@ -181,7 +181,8 @@ opts = {
181
181
  per_page: 56, # Integer | The number of entities per page to return.
182
182
  guid: 'guid_example', # String | Comma separated guids to list deposit addresses for.
183
183
  bank_guid: 'bank_guid_example', # String | Comma separated bank_guids to list deposit addresses for.
184
- customer_guid: 'customer_guid_example' # String | Comma separated customer_guids to list deposit addresses for.
184
+ customer_guid: 'customer_guid_example', # String | Comma separated customer_guids to list deposit addresses for.
185
+ label: 'label_example' # String | Comma separated labels to list deposit addresses for.
185
186
  }
186
187
 
187
188
  begin
@@ -220,6 +221,7 @@ end
220
221
  | **guid** | **String** | Comma separated guids to list deposit addresses for. | [optional] |
221
222
  | **bank_guid** | **String** | Comma separated bank_guids to list deposit addresses for. | [optional] |
222
223
  | **customer_guid** | **String** | Comma separated customer_guids to list deposit addresses for. | [optional] |
224
+ | **label** | **String** | Comma separated labels to list deposit addresses for. | [optional] |
223
225
 
224
226
  ### Return type
225
227
 
@@ -0,0 +1,18 @@
1
+ # CybridApiBank::PatchCustomerBankModel
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **state** | **String** | The customer&#39;s state. | [optional] |
8
+
9
+ ## Example
10
+
11
+ ```ruby
12
+ require 'cybrid_api_bank_ruby'
13
+
14
+ instance = CybridApiBank::PatchCustomerBankModel.new(
15
+ state: null
16
+ )
17
+ ```
18
+
@@ -5,6 +5,7 @@
5
5
  | Name | Type | Description | Notes |
6
6
  | ---- | ---- | ----------- | ----- |
7
7
  | **account_guid** | **String** | The trading account guid. | |
8
+ | **labels** | **Array&lt;String&gt;** | The labels associated with the address. | [optional] |
8
9
 
9
10
  ## Example
10
11
 
@@ -12,7 +13,8 @@
12
13
  require 'cybrid_api_bank_ruby'
13
14
 
14
15
  instance = CybridApiBank::PostDepositAddressBankModel.new(
15
- account_guid: null
16
+ account_guid: null,
17
+ labels: null
16
18
  )
17
19
  ```
18
20
 
@@ -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\" }' -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' ``` <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.98.2
6
+ The version of the OpenAPI document: v0.100.0
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\" }' -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' ``` <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.98.2
6
+ The version of the OpenAPI document: v0.100.0
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\" }' -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' ``` <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.98.2
6
+ The version of the OpenAPI document: v0.100.0
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\" }' -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' ``` <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.98.2
6
+ The version of the OpenAPI document: v0.100.0
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -233,5 +233,79 @@ module CybridApiBank
233
233
  end
234
234
  return data, status_code, headers
235
235
  end
236
+
237
+ # Patch Customer
238
+ # Update a customer. Required scope: **customers:write**
239
+ # @param customer_guid [String] Identifier for the customer.
240
+ # @param patch_customer_bank_model [PatchCustomerBankModel]
241
+ # @param [Hash] opts the optional parameters
242
+ # @return [CustomerBankModel]
243
+ def update_customer(customer_guid, patch_customer_bank_model, opts = {})
244
+ data, _status_code, _headers = update_customer_with_http_info(customer_guid, patch_customer_bank_model, opts)
245
+ data
246
+ end
247
+
248
+ # Patch Customer
249
+ # Update a customer. Required scope: **customers:write**
250
+ # @param customer_guid [String] Identifier for the customer.
251
+ # @param patch_customer_bank_model [PatchCustomerBankModel]
252
+ # @param [Hash] opts the optional parameters
253
+ # @return [Array<(CustomerBankModel, Integer, Hash)>] CustomerBankModel data, response status code and response headers
254
+ def update_customer_with_http_info(customer_guid, patch_customer_bank_model, opts = {})
255
+ if @api_client.config.debugging
256
+ @api_client.config.logger.debug 'Calling API: CustomersBankApi.update_customer ...'
257
+ end
258
+ # verify the required parameter 'customer_guid' is set
259
+ if @api_client.config.client_side_validation && customer_guid.nil?
260
+ fail ArgumentError, "Missing the required parameter 'customer_guid' when calling CustomersBankApi.update_customer"
261
+ end
262
+ # verify the required parameter 'patch_customer_bank_model' is set
263
+ if @api_client.config.client_side_validation && patch_customer_bank_model.nil?
264
+ fail ArgumentError, "Missing the required parameter 'patch_customer_bank_model' when calling CustomersBankApi.update_customer"
265
+ end
266
+ # resource path
267
+ local_var_path = '/api/customers/{customer_guid}'.sub('{' + 'customer_guid' + '}', CGI.escape(customer_guid.to_s))
268
+
269
+ # query parameters
270
+ query_params = opts[:query_params] || {}
271
+
272
+ # header parameters
273
+ header_params = opts[:header_params] || {}
274
+ # HTTP header 'Accept' (if needed)
275
+ header_params['Accept'] = @api_client.select_header_accept(['application/json'])
276
+ # HTTP header 'Content-Type'
277
+ content_type = @api_client.select_header_content_type(['application/json'])
278
+ if !content_type.nil?
279
+ header_params['Content-Type'] = content_type
280
+ end
281
+
282
+ # form parameters
283
+ form_params = opts[:form_params] || {}
284
+
285
+ # http body (model)
286
+ post_body = opts[:debug_body] || @api_client.object_to_http_body(patch_customer_bank_model)
287
+
288
+ # return_type
289
+ return_type = opts[:debug_return_type] || 'CustomerBankModel'
290
+
291
+ # auth_names
292
+ auth_names = opts[:debug_auth_names] || ['BearerAuth', 'oauth2']
293
+
294
+ new_options = opts.merge(
295
+ :operation => :"CustomersBankApi.update_customer",
296
+ :header_params => header_params,
297
+ :query_params => query_params,
298
+ :form_params => form_params,
299
+ :body => post_body,
300
+ :auth_names => auth_names,
301
+ :return_type => return_type
302
+ )
303
+
304
+ data, status_code, headers = @api_client.call_api(:PATCH, local_var_path, new_options)
305
+ if @api_client.config.debugging
306
+ @api_client.config.logger.debug "API called: CustomersBankApi#update_customer\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
307
+ end
308
+ return data, status_code, headers
309
+ end
236
310
  end
237
311
  end
@@ -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\" }' -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' ``` <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.98.2
6
+ The version of the OpenAPI document: v0.100.0
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -158,6 +158,7 @@ module CybridApiBank
158
158
  # @option opts [String] :guid Comma separated guids to list deposit addresses for.
159
159
  # @option opts [String] :bank_guid Comma separated bank_guids to list deposit addresses for.
160
160
  # @option opts [String] :customer_guid Comma separated customer_guids to list deposit addresses for.
161
+ # @option opts [String] :label Comma separated labels to list deposit addresses for.
161
162
  # @return [DepositAddressListBankModel]
162
163
  def list_deposit_addresses(opts = {})
163
164
  data, _status_code, _headers = list_deposit_addresses_with_http_info(opts)
@@ -172,6 +173,7 @@ module CybridApiBank
172
173
  # @option opts [String] :guid Comma separated guids to list deposit addresses for.
173
174
  # @option opts [String] :bank_guid Comma separated bank_guids to list deposit addresses for.
174
175
  # @option opts [String] :customer_guid Comma separated customer_guids to list deposit addresses for.
176
+ # @option opts [String] :label Comma separated labels to list deposit addresses for.
175
177
  # @return [Array<(DepositAddressListBankModel, Integer, Hash)>] DepositAddressListBankModel data, response status code and response headers
176
178
  def list_deposit_addresses_with_http_info(opts = {})
177
179
  if @api_client.config.debugging
@@ -199,6 +201,7 @@ module CybridApiBank
199
201
  query_params[:'guid'] = opts[:'guid'] if !opts[:'guid'].nil?
200
202
  query_params[:'bank_guid'] = opts[:'bank_guid'] if !opts[:'bank_guid'].nil?
201
203
  query_params[:'customer_guid'] = opts[:'customer_guid'] if !opts[:'customer_guid'].nil?
204
+ query_params[:'label'] = opts[:'label'] if !opts[:'label'].nil?
202
205
 
203
206
  # header parameters
204
207
  header_params = opts[:header_params] || {}