cybrid_api_bank_ruby 0.128.60 → 0.128.61

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (556) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +24 -24
  3. data/README.md +5 -5
  4. data/cybrid_api_bank_ruby.gemspec +1 -1
  5. data/lib/cybrid_api_bank_ruby/api/accounts_bank_api.rb +1 -1
  6. data/lib/cybrid_api_bank_ruby/api/assets_bank_api.rb +1 -1
  7. data/lib/cybrid_api_bank_ruby/api/banks_bank_api.rb +1 -1
  8. data/lib/cybrid_api_bank_ruby/api/counterparties_bank_api.rb +1 -1
  9. data/lib/cybrid_api_bank_ruby/api/customers_bank_api.rb +1 -1
  10. data/lib/cybrid_api_bank_ruby/api/deposit_addresses_bank_api.rb +1 -1
  11. data/lib/cybrid_api_bank_ruby/api/deposit_bank_accounts_bank_api.rb +1 -1
  12. data/lib/cybrid_api_bank_ruby/api/executions_bank_api.rb +1 -1
  13. data/lib/cybrid_api_bank_ruby/api/external_bank_accounts_bank_api.rb +1 -1
  14. data/lib/cybrid_api_bank_ruby/api/external_wallets_bank_api.rb +1 -1
  15. data/lib/cybrid_api_bank_ruby/api/files_bank_api.rb +1 -1
  16. data/lib/cybrid_api_bank_ruby/api/identity_verifications_bank_api.rb +1 -1
  17. data/lib/cybrid_api_bank_ruby/api/invoices_bank_api.rb +1 -1
  18. data/lib/cybrid_api_bank_ruby/api/payment_instructions_bank_api.rb +1 -1
  19. data/lib/cybrid_api_bank_ruby/api/persona_sessions_bank_api.rb +1 -1
  20. data/lib/cybrid_api_bank_ruby/api/plans_bank_api.rb +1 -1
  21. data/lib/cybrid_api_bank_ruby/api/prices_bank_api.rb +1 -1
  22. data/lib/cybrid_api_bank_ruby/api/quotes_bank_api.rb +1 -1
  23. data/lib/cybrid_api_bank_ruby/api/symbols_bank_api.rb +1 -1
  24. data/lib/cybrid_api_bank_ruby/api/trades_bank_api.rb +1 -1
  25. data/lib/cybrid_api_bank_ruby/api/transfers_bank_api.rb +1 -1
  26. data/lib/cybrid_api_bank_ruby/api/workflows_bank_api.rb +1 -1
  27. data/lib/cybrid_api_bank_ruby/api_client.rb +1 -1
  28. data/lib/cybrid_api_bank_ruby/api_error.rb +1 -1
  29. data/lib/cybrid_api_bank_ruby/configuration.rb +1 -1
  30. data/lib/cybrid_api_bank_ruby/models/account_association_bank_model.rb +1 -1
  31. data/lib/cybrid_api_bank_ruby/models/account_bank_model.rb +1 -1
  32. data/lib/cybrid_api_bank_ruby/models/account_list_bank_model.rb +1 -1
  33. data/lib/cybrid_api_bank_ruby/models/account_state_bank_model.rb +1 -1
  34. data/lib/cybrid_api_bank_ruby/models/account_type_bank_model.rb +1 -1
  35. data/lib/cybrid_api_bank_ruby/models/activity_limit_bank_model.rb +1 -1
  36. data/lib/cybrid_api_bank_ruby/models/activity_side_bank_model.rb +1 -1
  37. data/lib/cybrid_api_bank_ruby/models/activity_type_bank_model.rb +1 -1
  38. data/lib/cybrid_api_bank_ruby/models/asset_bank_model.rb +1 -1
  39. data/lib/cybrid_api_bank_ruby/models/asset_list_bank_model.rb +1 -1
  40. data/lib/cybrid_api_bank_ruby/models/asset_types_bank_model.rb +1 -1
  41. data/lib/cybrid_api_bank_ruby/models/bank_bank_model.rb +1 -1
  42. data/lib/cybrid_api_bank_ruby/models/bank_feature_bank_model.rb +1 -1
  43. data/lib/cybrid_api_bank_ruby/models/bank_list_bank_model.rb +1 -1
  44. data/lib/cybrid_api_bank_ruby/models/bank_supported_payout_symbols_inner_bank_model.rb +1 -1
  45. data/lib/cybrid_api_bank_ruby/models/bank_type_bank_model.rb +1 -1
  46. data/lib/cybrid_api_bank_ruby/models/compliance_check_bank_model.rb +1 -1
  47. data/lib/cybrid_api_bank_ruby/models/compliance_check_outcome_bank_model.rb +1 -1
  48. data/lib/cybrid_api_bank_ruby/models/compliance_check_type_bank_model.rb +1 -1
  49. data/lib/cybrid_api_bank_ruby/models/compliance_decision_bank_model.rb +1 -1
  50. data/lib/cybrid_api_bank_ruby/models/compliance_decision_state_bank_model.rb +1 -1
  51. data/lib/cybrid_api_bank_ruby/models/compliance_decision_type_bank_model.rb +1 -1
  52. data/lib/cybrid_api_bank_ruby/models/counterparty_address_bank_model.rb +1 -1
  53. data/lib/cybrid_api_bank_ruby/models/counterparty_aliases_inner_bank_model.rb +1 -1
  54. data/lib/cybrid_api_bank_ruby/models/counterparty_bank_model.rb +1 -1
  55. data/lib/cybrid_api_bank_ruby/models/counterparty_list_bank_model.rb +1 -1
  56. data/lib/cybrid_api_bank_ruby/models/counterparty_name_bank_model.rb +1 -1
  57. data/lib/cybrid_api_bank_ruby/models/counterparty_state_bank_model.rb +1 -1
  58. data/lib/cybrid_api_bank_ruby/models/counterparty_type_bank_model.rb +1 -1
  59. data/lib/cybrid_api_bank_ruby/models/customer_address_bank_model.rb +1 -1
  60. data/lib/cybrid_api_bank_ruby/models/customer_aliases_inner_bank_model.rb +1 -1
  61. data/lib/cybrid_api_bank_ruby/models/customer_bank_model.rb +1 -1
  62. data/lib/cybrid_api_bank_ruby/models/customer_list_bank_model.rb +1 -1
  63. data/lib/cybrid_api_bank_ruby/models/customer_name_bank_model.rb +1 -1
  64. data/lib/cybrid_api_bank_ruby/models/customer_state_bank_model.rb +1 -1
  65. data/lib/cybrid_api_bank_ruby/models/customer_type_bank_model.rb +1 -1
  66. data/lib/cybrid_api_bank_ruby/models/deposit_address_bank_model.rb +1 -1
  67. data/lib/cybrid_api_bank_ruby/models/deposit_address_format_bank_model.rb +1 -1
  68. data/lib/cybrid_api_bank_ruby/models/deposit_address_list_bank_model.rb +1 -1
  69. data/lib/cybrid_api_bank_ruby/models/deposit_address_state_bank_model.rb +1 -1
  70. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_account_details_inner_bank_model.rb +1 -1
  71. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_bank_model.rb +1 -1
  72. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_counterparty_address_bank_model.rb +1 -1
  73. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_list_bank_model.rb +1 -1
  74. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_routing_details_inner_bank_model.rb +1 -1
  75. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_routing_number_type_bank_model.rb +1 -1
  76. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_state_bank_model.rb +1 -1
  77. data/lib/cybrid_api_bank_ruby/models/error_response_bank_model.rb +1 -1
  78. data/lib/cybrid_api_bank_ruby/models/execution_bank_model.rb +1 -1
  79. data/lib/cybrid_api_bank_ruby/models/execution_list_bank_model.rb +1 -1
  80. data/lib/cybrid_api_bank_ruby/models/execution_travel_rule_info_bank_model.rb +1 -1
  81. data/lib/cybrid_api_bank_ruby/models/external_bank_account_balances_bank_model.rb +1 -1
  82. data/lib/cybrid_api_bank_ruby/models/external_bank_account_bank_model.rb +1 -1
  83. data/lib/cybrid_api_bank_ruby/models/external_bank_account_kind_bank_model.rb +1 -1
  84. data/lib/cybrid_api_bank_ruby/models/external_bank_account_list_bank_model.rb +1 -1
  85. data/lib/cybrid_api_bank_ruby/models/external_bank_account_pii_inner_addresses_inner_bank_model.rb +1 -1
  86. data/lib/cybrid_api_bank_ruby/models/external_bank_account_pii_inner_bank_model.rb +1 -1
  87. data/lib/cybrid_api_bank_ruby/models/external_bank_account_pii_inner_routing_details_inner_bank_model.rb +1 -1
  88. data/lib/cybrid_api_bank_ruby/models/external_bank_account_state_bank_model.rb +1 -1
  89. data/lib/cybrid_api_bank_ruby/models/external_wallet_bank_model.rb +1 -1
  90. data/lib/cybrid_api_bank_ruby/models/external_wallet_environment_bank_model.rb +1 -1
  91. data/lib/cybrid_api_bank_ruby/models/external_wallet_list_bank_model.rb +1 -1
  92. data/lib/cybrid_api_bank_ruby/models/external_wallet_state_bank_model.rb +1 -1
  93. data/lib/cybrid_api_bank_ruby/models/fee_association_bank_model.rb +1 -1
  94. data/lib/cybrid_api_bank_ruby/models/fee_detail_bank_model.rb +1 -1
  95. data/lib/cybrid_api_bank_ruby/models/identification_number_bank_model.rb +1 -1
  96. data/lib/cybrid_api_bank_ruby/models/identity_verification_bank_model.rb +1 -1
  97. data/lib/cybrid_api_bank_ruby/models/identity_verification_business_associate_bank_model.rb +1 -1
  98. data/lib/cybrid_api_bank_ruby/models/identity_verification_document_bank_model.rb +1 -1
  99. data/lib/cybrid_api_bank_ruby/models/identity_verification_document_file_bank_model.rb +1 -1
  100. data/lib/cybrid_api_bank_ruby/models/identity_verification_document_file_metadata_bank_model.rb +1 -1
  101. data/lib/cybrid_api_bank_ruby/models/identity_verification_list_bank_model.rb +1 -1
  102. data/lib/cybrid_api_bank_ruby/models/identity_verification_method_bank_model.rb +1 -1
  103. data/lib/cybrid_api_bank_ruby/models/identity_verification_options_bank_model.rb +1 -1
  104. data/lib/cybrid_api_bank_ruby/models/identity_verification_outcome_bank_model.rb +1 -1
  105. data/lib/cybrid_api_bank_ruby/models/identity_verification_persona_state_bank_model.rb +1 -1
  106. data/lib/cybrid_api_bank_ruby/models/identity_verification_state_bank_model.rb +1 -1
  107. data/lib/cybrid_api_bank_ruby/models/identity_verification_type_bank_model.rb +1 -1
  108. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_bank_model.rb +1 -1
  109. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_pii_address_bank_model.rb +1 -1
  110. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_pii_aliases_inner_bank_model.rb +1 -1
  111. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_pii_bank_model.rb +1 -1
  112. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_pii_name_bank_model.rb +1 -1
  113. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_pii_registered_address_bank_model.rb +1 -1
  114. data/lib/cybrid_api_bank_ruby/models/invoice_bank_model.rb +1 -1
  115. data/lib/cybrid_api_bank_ruby/models/invoice_list_bank_model.rb +1 -1
  116. data/lib/cybrid_api_bank_ruby/models/patch_bank_bank_model.rb +1 -1
  117. data/lib/cybrid_api_bank_ruby/models/patch_customer_bank_model.rb +1 -1
  118. data/lib/cybrid_api_bank_ruby/models/patch_external_bank_account_bank_model.rb +1 -1
  119. data/lib/cybrid_api_bank_ruby/models/patch_transfer_bank_model.rb +1 -1
  120. data/lib/cybrid_api_bank_ruby/models/patch_transfer_participant_bank_model.rb +1 -1
  121. data/lib/cybrid_api_bank_ruby/models/payment_instruction_bank_model.rb +1 -1
  122. data/lib/cybrid_api_bank_ruby/models/payment_instruction_list_bank_model.rb +1 -1
  123. data/lib/cybrid_api_bank_ruby/models/persona_session_bank_model.rb +1 -1
  124. data/lib/cybrid_api_bank_ruby/models/plan_bank_model.rb +1 -1
  125. data/lib/cybrid_api_bank_ruby/models/plan_list_bank_model.rb +1 -1
  126. data/lib/cybrid_api_bank_ruby/models/plan_travel_rule_info_bank_model.rb +1 -1
  127. data/lib/cybrid_api_bank_ruby/models/platform_file_bank_model.rb +1 -1
  128. data/lib/cybrid_api_bank_ruby/models/platform_file_list_bank_model.rb +1 -1
  129. data/lib/cybrid_api_bank_ruby/models/post_account_bank_model.rb +1 -1
  130. data/lib/cybrid_api_bank_ruby/models/post_bank_account_details_bank_model.rb +1 -1
  131. data/lib/cybrid_api_bank_ruby/models/post_bank_bank_model.rb +1 -1
  132. data/lib/cybrid_api_bank_ruby/models/post_counterparty_address_bank_model.rb +1 -1
  133. data/lib/cybrid_api_bank_ruby/models/post_counterparty_aliases_inner_bank_model.rb +1 -1
  134. data/lib/cybrid_api_bank_ruby/models/post_counterparty_bank_model.rb +1 -1
  135. data/lib/cybrid_api_bank_ruby/models/post_counterparty_name_bank_model.rb +1 -1
  136. data/lib/cybrid_api_bank_ruby/models/post_customer_address_bank_model.rb +1 -1
  137. data/lib/cybrid_api_bank_ruby/models/post_customer_aliases_inner_bank_model.rb +1 -1
  138. data/lib/cybrid_api_bank_ruby/models/post_customer_bank_model.rb +1 -1
  139. data/lib/cybrid_api_bank_ruby/models/post_customer_name_bank_model.rb +1 -1
  140. data/lib/cybrid_api_bank_ruby/models/post_deposit_address_bank_model.rb +1 -1
  141. data/lib/cybrid_api_bank_ruby/models/post_deposit_bank_account_bank_model.rb +1 -1
  142. data/lib/cybrid_api_bank_ruby/models/post_execution_bank_model.rb +1 -1
  143. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_bank_model.rb +1 -1
  144. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_address_bank_model.rb +1 -1
  145. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_name_bank_model.rb +1 -1
  146. data/lib/cybrid_api_bank_ruby/models/post_external_wallet_bank_model.rb +1 -1
  147. data/lib/cybrid_api_bank_ruby/models/post_fee_bank_model.rb +1 -1
  148. data/lib/cybrid_api_bank_ruby/models/post_file_bank_model.rb +1 -1
  149. data/lib/cybrid_api_bank_ruby/models/post_file_metadata_bank_model.rb +1 -1
  150. data/lib/cybrid_api_bank_ruby/models/post_identification_number_bank_model.rb +1 -1
  151. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_address_bank_model.rb +1 -1
  152. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_aliases_inner_bank_model.rb +1 -1
  153. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_bank_model.rb +1 -1
  154. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_name_bank_model.rb +1 -1
  155. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_registered_address_bank_model.rb +1 -1
  156. data/lib/cybrid_api_bank_ruby/models/post_invoice_bank_model.rb +1 -1
  157. data/lib/cybrid_api_bank_ruby/models/post_payment_instruction_bank_model.rb +1 -1
  158. data/lib/cybrid_api_bank_ruby/models/post_persona_session_bank_model.rb +1 -1
  159. data/lib/cybrid_api_bank_ruby/models/post_plan_bank_model.rb +1 -1
  160. data/lib/cybrid_api_bank_ruby/models/post_plan_destination_account_bank_model.rb +1 -1
  161. data/lib/cybrid_api_bank_ruby/models/post_plan_source_account_bank_model.rb +1 -1
  162. data/lib/cybrid_api_bank_ruby/models/post_plan_travel_rule_info_bank_model.rb +1 -1
  163. data/lib/cybrid_api_bank_ruby/models/post_quote_bank_model.rb +1 -1
  164. data/lib/cybrid_api_bank_ruby/models/post_quote_entry_bank_model.rb +1 -1
  165. data/lib/cybrid_api_bank_ruby/models/post_supported_payout_symbols_bank_model.rb +1 -1
  166. data/lib/cybrid_api_bank_ruby/models/post_trade_bank_model.rb +1 -1
  167. data/lib/cybrid_api_bank_ruby/models/post_transfer_bank_model.rb +1 -1
  168. data/lib/cybrid_api_bank_ruby/models/post_transfer_participant_bank_model.rb +1 -1
  169. data/lib/cybrid_api_bank_ruby/models/post_ultimate_beneficial_owner_bank_model.rb +1 -1
  170. data/lib/cybrid_api_bank_ruby/models/post_workflow_bank_model.rb +1 -1
  171. data/lib/cybrid_api_bank_ruby/models/quote_bank_model.rb +1 -1
  172. data/lib/cybrid_api_bank_ruby/models/quote_entry_bank_model.rb +1 -1
  173. data/lib/cybrid_api_bank_ruby/models/quote_entry_destination_account_bank_model.rb +1 -1
  174. data/lib/cybrid_api_bank_ruby/models/quote_entry_source_account_bank_model.rb +1 -1
  175. data/lib/cybrid_api_bank_ruby/models/quote_list_bank_model.rb +1 -1
  176. data/lib/cybrid_api_bank_ruby/models/quote_side_bank_model.rb +1 -1
  177. data/lib/cybrid_api_bank_ruby/models/quote_type_bank_model.rb +1 -1
  178. data/lib/cybrid_api_bank_ruby/models/stage_bank_model.rb +1 -1
  179. data/lib/cybrid_api_bank_ruby/models/symbol_price_bank_model.rb +1 -1
  180. data/lib/cybrid_api_bank_ruby/models/trade_bank_model.rb +1 -1
  181. data/lib/cybrid_api_bank_ruby/models/trade_failure_code_bank_model.rb +1 -1
  182. data/lib/cybrid_api_bank_ruby/models/trade_list_bank_model.rb +1 -1
  183. data/lib/cybrid_api_bank_ruby/models/trade_side_bank_model.rb +1 -1
  184. data/lib/cybrid_api_bank_ruby/models/trade_state_bank_model.rb +1 -1
  185. data/lib/cybrid_api_bank_ruby/models/trade_type_bank_model.rb +1 -1
  186. data/lib/cybrid_api_bank_ruby/models/transfer_account_type_bank_model.rb +1 -1
  187. data/lib/cybrid_api_bank_ruby/models/transfer_bank_model.rb +1 -1
  188. data/lib/cybrid_api_bank_ruby/models/transfer_destination_account_bank_model.rb +1 -1
  189. data/lib/cybrid_api_bank_ruby/models/transfer_entry_bank_model.rb +1 -1
  190. data/lib/cybrid_api_bank_ruby/models/transfer_entry_destination_account_bank_model.rb +1 -1
  191. data/lib/cybrid_api_bank_ruby/models/transfer_failure_code_bank_model.rb +1 -1
  192. data/lib/cybrid_api_bank_ruby/models/transfer_hold_details_bank_model.rb +1 -1
  193. data/lib/cybrid_api_bank_ruby/models/transfer_identifiers_inner_bank_model.rb +1 -1
  194. data/lib/cybrid_api_bank_ruby/models/transfer_list_bank_model.rb +1 -1
  195. data/lib/cybrid_api_bank_ruby/models/transfer_participant_bank_model.rb +1 -1
  196. data/lib/cybrid_api_bank_ruby/models/transfer_side_bank_model.rb +1 -1
  197. data/lib/cybrid_api_bank_ruby/models/transfer_source_account_bank_model.rb +1 -1
  198. data/lib/cybrid_api_bank_ruby/models/transfer_state_bank_model.rb +1 -1
  199. data/lib/cybrid_api_bank_ruby/models/transfer_type_bank_model.rb +1 -1
  200. data/lib/cybrid_api_bank_ruby/models/travel_rule_info_party_bank_model.rb +1 -1
  201. data/lib/cybrid_api_bank_ruby/models/workflow_bank_model.rb +1 -1
  202. data/lib/cybrid_api_bank_ruby/models/workflow_state_bank_model.rb +1 -1
  203. data/lib/cybrid_api_bank_ruby/models/workflow_type_bank_model.rb +1 -1
  204. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_all_of_bank_model.rb +1 -1
  205. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_bank_model.rb +1 -1
  206. data/lib/cybrid_api_bank_ruby/models/workflows_list_bank_model.rb +1 -1
  207. data/lib/cybrid_api_bank_ruby/version.rb +2 -2
  208. data/lib/cybrid_api_bank_ruby.rb +1 -1
  209. data/spec/api/accounts_bank_api_spec.rb +1 -1
  210. data/spec/api/assets_bank_api_spec.rb +1 -1
  211. data/spec/api/banks_bank_api_spec.rb +1 -1
  212. data/spec/api/counterparties_bank_api_spec.rb +1 -1
  213. data/spec/api/customers_bank_api_spec.rb +1 -1
  214. data/spec/api/deposit_addresses_bank_api_spec.rb +1 -1
  215. data/spec/api/deposit_bank_accounts_bank_api_spec.rb +1 -1
  216. data/spec/api/executions_bank_api_spec.rb +1 -1
  217. data/spec/api/external_bank_accounts_bank_api_spec.rb +1 -1
  218. data/spec/api/external_wallets_bank_api_spec.rb +1 -1
  219. data/spec/api/files_bank_api_spec.rb +1 -1
  220. data/spec/api/identity_verifications_bank_api_spec.rb +1 -1
  221. data/spec/api/invoices_bank_api_spec.rb +1 -1
  222. data/spec/api/payment_instructions_bank_api_spec.rb +1 -1
  223. data/spec/api/persona_sessions_bank_api_spec.rb +1 -1
  224. data/spec/api/plans_bank_api_spec.rb +1 -1
  225. data/spec/api/prices_bank_api_spec.rb +1 -1
  226. data/spec/api/quotes_bank_api_spec.rb +1 -1
  227. data/spec/api/symbols_bank_api_spec.rb +1 -1
  228. data/spec/api/trades_bank_api_spec.rb +1 -1
  229. data/spec/api/transfers_bank_api_spec.rb +1 -1
  230. data/spec/api/workflows_bank_api_spec.rb +1 -1
  231. data/spec/api_client_spec.rb +1 -1
  232. data/spec/configuration_spec.rb +1 -1
  233. data/spec/models/account_association_bank_model_spec.rb +1 -1
  234. data/spec/models/account_bank_model_spec.rb +1 -1
  235. data/spec/models/account_list_bank_model_spec.rb +1 -1
  236. data/spec/models/account_state_bank_model_spec.rb +1 -1
  237. data/spec/models/account_type_bank_model_spec.rb +1 -1
  238. data/spec/models/activity_limit_bank_model_spec.rb +1 -1
  239. data/spec/models/activity_side_bank_model_spec.rb +1 -1
  240. data/spec/models/activity_type_bank_model_spec.rb +1 -1
  241. data/spec/models/asset_bank_model_spec.rb +1 -1
  242. data/spec/models/asset_list_bank_model_spec.rb +1 -1
  243. data/spec/models/asset_types_bank_model_spec.rb +1 -1
  244. data/spec/models/bank_bank_model_spec.rb +1 -1
  245. data/spec/models/bank_feature_bank_model_spec.rb +1 -1
  246. data/spec/models/bank_list_bank_model_spec.rb +1 -1
  247. data/spec/models/bank_supported_payout_symbols_inner_bank_model_spec.rb +1 -1
  248. data/spec/models/bank_type_bank_model_spec.rb +1 -1
  249. data/spec/models/compliance_check_bank_model_spec.rb +1 -1
  250. data/spec/models/compliance_check_outcome_bank_model_spec.rb +1 -1
  251. data/spec/models/compliance_check_type_bank_model_spec.rb +1 -1
  252. data/spec/models/compliance_decision_bank_model_spec.rb +1 -1
  253. data/spec/models/compliance_decision_state_bank_model_spec.rb +1 -1
  254. data/spec/models/compliance_decision_type_bank_model_spec.rb +1 -1
  255. data/spec/models/counterparty_address_bank_model_spec.rb +1 -1
  256. data/spec/models/counterparty_aliases_inner_bank_model_spec.rb +1 -1
  257. data/spec/models/counterparty_bank_model_spec.rb +1 -1
  258. data/spec/models/counterparty_list_bank_model_spec.rb +1 -1
  259. data/spec/models/counterparty_name_bank_model_spec.rb +1 -1
  260. data/spec/models/counterparty_state_bank_model_spec.rb +1 -1
  261. data/spec/models/counterparty_type_bank_model_spec.rb +1 -1
  262. data/spec/models/customer_address_bank_model_spec.rb +1 -1
  263. data/spec/models/customer_aliases_inner_bank_model_spec.rb +1 -1
  264. data/spec/models/customer_bank_model_spec.rb +1 -1
  265. data/spec/models/customer_list_bank_model_spec.rb +1 -1
  266. data/spec/models/customer_name_bank_model_spec.rb +1 -1
  267. data/spec/models/customer_state_bank_model_spec.rb +1 -1
  268. data/spec/models/customer_type_bank_model_spec.rb +1 -1
  269. data/spec/models/deposit_address_bank_model_spec.rb +1 -1
  270. data/spec/models/deposit_address_format_bank_model_spec.rb +1 -1
  271. data/spec/models/deposit_address_list_bank_model_spec.rb +1 -1
  272. data/spec/models/deposit_address_state_bank_model_spec.rb +1 -1
  273. data/spec/models/deposit_bank_account_account_details_inner_bank_model_spec.rb +1 -1
  274. data/spec/models/deposit_bank_account_bank_model_spec.rb +1 -1
  275. data/spec/models/deposit_bank_account_counterparty_address_bank_model_spec.rb +1 -1
  276. data/spec/models/deposit_bank_account_list_bank_model_spec.rb +1 -1
  277. data/spec/models/deposit_bank_account_routing_details_inner_bank_model_spec.rb +1 -1
  278. data/spec/models/deposit_bank_account_routing_number_type_bank_model_spec.rb +1 -1
  279. data/spec/models/deposit_bank_account_state_bank_model_spec.rb +1 -1
  280. data/spec/models/error_response_bank_model_spec.rb +1 -1
  281. data/spec/models/execution_bank_model_spec.rb +1 -1
  282. data/spec/models/execution_list_bank_model_spec.rb +1 -1
  283. data/spec/models/execution_travel_rule_info_bank_model_spec.rb +1 -1
  284. data/spec/models/external_bank_account_balances_bank_model_spec.rb +1 -1
  285. data/spec/models/external_bank_account_bank_model_spec.rb +1 -1
  286. data/spec/models/external_bank_account_kind_bank_model_spec.rb +1 -1
  287. data/spec/models/external_bank_account_list_bank_model_spec.rb +1 -1
  288. data/spec/models/external_bank_account_pii_inner_addresses_inner_bank_model_spec.rb +1 -1
  289. data/spec/models/external_bank_account_pii_inner_bank_model_spec.rb +1 -1
  290. data/spec/models/external_bank_account_pii_inner_routing_details_inner_bank_model_spec.rb +1 -1
  291. data/spec/models/external_bank_account_state_bank_model_spec.rb +1 -1
  292. data/spec/models/external_wallet_bank_model_spec.rb +1 -1
  293. data/spec/models/external_wallet_environment_bank_model_spec.rb +1 -1
  294. data/spec/models/external_wallet_list_bank_model_spec.rb +1 -1
  295. data/spec/models/external_wallet_state_bank_model_spec.rb +1 -1
  296. data/spec/models/fee_association_bank_model_spec.rb +1 -1
  297. data/spec/models/fee_detail_bank_model_spec.rb +1 -1
  298. data/spec/models/identification_number_bank_model_spec.rb +1 -1
  299. data/spec/models/identity_verification_bank_model_spec.rb +1 -1
  300. data/spec/models/identity_verification_business_associate_bank_model_spec.rb +1 -1
  301. data/spec/models/identity_verification_document_bank_model_spec.rb +1 -1
  302. data/spec/models/identity_verification_document_file_bank_model_spec.rb +1 -1
  303. data/spec/models/identity_verification_document_file_metadata_bank_model_spec.rb +1 -1
  304. data/spec/models/identity_verification_list_bank_model_spec.rb +1 -1
  305. data/spec/models/identity_verification_method_bank_model_spec.rb +1 -1
  306. data/spec/models/identity_verification_options_bank_model_spec.rb +1 -1
  307. data/spec/models/identity_verification_outcome_bank_model_spec.rb +1 -1
  308. data/spec/models/identity_verification_persona_state_bank_model_spec.rb +1 -1
  309. data/spec/models/identity_verification_state_bank_model_spec.rb +1 -1
  310. data/spec/models/identity_verification_type_bank_model_spec.rb +1 -1
  311. data/spec/models/identity_verification_with_details_bank_model_spec.rb +1 -1
  312. data/spec/models/identity_verification_with_details_pii_address_bank_model_spec.rb +1 -1
  313. data/spec/models/identity_verification_with_details_pii_aliases_inner_bank_model_spec.rb +1 -1
  314. data/spec/models/identity_verification_with_details_pii_bank_model_spec.rb +1 -1
  315. data/spec/models/identity_verification_with_details_pii_name_bank_model_spec.rb +1 -1
  316. data/spec/models/identity_verification_with_details_pii_registered_address_bank_model_spec.rb +1 -1
  317. data/spec/models/invoice_bank_model_spec.rb +1 -1
  318. data/spec/models/invoice_list_bank_model_spec.rb +1 -1
  319. data/spec/models/patch_bank_bank_model_spec.rb +1 -1
  320. data/spec/models/patch_customer_bank_model_spec.rb +1 -1
  321. data/spec/models/patch_external_bank_account_bank_model_spec.rb +1 -1
  322. data/spec/models/patch_transfer_bank_model_spec.rb +1 -1
  323. data/spec/models/patch_transfer_participant_bank_model_spec.rb +1 -1
  324. data/spec/models/payment_instruction_bank_model_spec.rb +1 -1
  325. data/spec/models/payment_instruction_list_bank_model_spec.rb +1 -1
  326. data/spec/models/persona_session_bank_model_spec.rb +1 -1
  327. data/spec/models/plan_bank_model_spec.rb +1 -1
  328. data/spec/models/plan_list_bank_model_spec.rb +1 -1
  329. data/spec/models/plan_travel_rule_info_bank_model_spec.rb +1 -1
  330. data/spec/models/platform_file_bank_model_spec.rb +1 -1
  331. data/spec/models/platform_file_list_bank_model_spec.rb +1 -1
  332. data/spec/models/post_account_bank_model_spec.rb +1 -1
  333. data/spec/models/post_bank_account_details_bank_model_spec.rb +1 -1
  334. data/spec/models/post_bank_bank_model_spec.rb +1 -1
  335. data/spec/models/post_counterparty_address_bank_model_spec.rb +1 -1
  336. data/spec/models/post_counterparty_aliases_inner_bank_model_spec.rb +1 -1
  337. data/spec/models/post_counterparty_bank_model_spec.rb +1 -1
  338. data/spec/models/post_counterparty_name_bank_model_spec.rb +1 -1
  339. data/spec/models/post_customer_address_bank_model_spec.rb +1 -1
  340. data/spec/models/post_customer_aliases_inner_bank_model_spec.rb +1 -1
  341. data/spec/models/post_customer_bank_model_spec.rb +1 -1
  342. data/spec/models/post_customer_name_bank_model_spec.rb +1 -1
  343. data/spec/models/post_deposit_address_bank_model_spec.rb +1 -1
  344. data/spec/models/post_deposit_bank_account_bank_model_spec.rb +1 -1
  345. data/spec/models/post_execution_bank_model_spec.rb +1 -1
  346. data/spec/models/post_external_bank_account_bank_model_spec.rb +1 -1
  347. data/spec/models/post_external_bank_account_counterparty_address_bank_model_spec.rb +1 -1
  348. data/spec/models/post_external_bank_account_counterparty_name_bank_model_spec.rb +1 -1
  349. data/spec/models/post_external_wallet_bank_model_spec.rb +1 -1
  350. data/spec/models/post_fee_bank_model_spec.rb +1 -1
  351. data/spec/models/post_file_bank_model_spec.rb +1 -1
  352. data/spec/models/post_file_metadata_bank_model_spec.rb +1 -1
  353. data/spec/models/post_identification_number_bank_model_spec.rb +1 -1
  354. data/spec/models/post_identity_verification_address_bank_model_spec.rb +1 -1
  355. data/spec/models/post_identity_verification_aliases_inner_bank_model_spec.rb +1 -1
  356. data/spec/models/post_identity_verification_bank_model_spec.rb +1 -1
  357. data/spec/models/post_identity_verification_name_bank_model_spec.rb +1 -1
  358. data/spec/models/post_identity_verification_registered_address_bank_model_spec.rb +1 -1
  359. data/spec/models/post_invoice_bank_model_spec.rb +1 -1
  360. data/spec/models/post_payment_instruction_bank_model_spec.rb +1 -1
  361. data/spec/models/post_persona_session_bank_model_spec.rb +1 -1
  362. data/spec/models/post_plan_bank_model_spec.rb +1 -1
  363. data/spec/models/post_plan_destination_account_bank_model_spec.rb +1 -1
  364. data/spec/models/post_plan_source_account_bank_model_spec.rb +1 -1
  365. data/spec/models/post_plan_travel_rule_info_bank_model_spec.rb +1 -1
  366. data/spec/models/post_quote_bank_model_spec.rb +1 -1
  367. data/spec/models/post_quote_entry_bank_model_spec.rb +1 -1
  368. data/spec/models/post_supported_payout_symbols_bank_model_spec.rb +1 -1
  369. data/spec/models/post_trade_bank_model_spec.rb +1 -1
  370. data/spec/models/post_transfer_bank_model_spec.rb +1 -1
  371. data/spec/models/post_transfer_participant_bank_model_spec.rb +1 -1
  372. data/spec/models/post_ultimate_beneficial_owner_bank_model_spec.rb +1 -1
  373. data/spec/models/post_workflow_bank_model_spec.rb +1 -1
  374. data/spec/models/quote_bank_model_spec.rb +1 -1
  375. data/spec/models/quote_entry_bank_model_spec.rb +1 -1
  376. data/spec/models/quote_entry_destination_account_bank_model_spec.rb +1 -1
  377. data/spec/models/quote_entry_source_account_bank_model_spec.rb +1 -1
  378. data/spec/models/quote_list_bank_model_spec.rb +1 -1
  379. data/spec/models/quote_side_bank_model_spec.rb +1 -1
  380. data/spec/models/quote_type_bank_model_spec.rb +1 -1
  381. data/spec/models/stage_bank_model_spec.rb +1 -1
  382. data/spec/models/symbol_price_bank_model_spec.rb +1 -1
  383. data/spec/models/trade_bank_model_spec.rb +1 -1
  384. data/spec/models/trade_failure_code_bank_model_spec.rb +1 -1
  385. data/spec/models/trade_list_bank_model_spec.rb +1 -1
  386. data/spec/models/trade_side_bank_model_spec.rb +1 -1
  387. data/spec/models/trade_state_bank_model_spec.rb +1 -1
  388. data/spec/models/trade_type_bank_model_spec.rb +1 -1
  389. data/spec/models/transfer_account_type_bank_model_spec.rb +1 -1
  390. data/spec/models/transfer_bank_model_spec.rb +1 -1
  391. data/spec/models/transfer_destination_account_bank_model_spec.rb +1 -1
  392. data/spec/models/transfer_entry_bank_model_spec.rb +1 -1
  393. data/spec/models/transfer_entry_destination_account_bank_model_spec.rb +1 -1
  394. data/spec/models/transfer_failure_code_bank_model_spec.rb +1 -1
  395. data/spec/models/transfer_hold_details_bank_model_spec.rb +1 -1
  396. data/spec/models/transfer_identifiers_inner_bank_model_spec.rb +1 -1
  397. data/spec/models/transfer_list_bank_model_spec.rb +1 -1
  398. data/spec/models/transfer_participant_bank_model_spec.rb +1 -1
  399. data/spec/models/transfer_side_bank_model_spec.rb +1 -1
  400. data/spec/models/transfer_source_account_bank_model_spec.rb +1 -1
  401. data/spec/models/transfer_state_bank_model_spec.rb +1 -1
  402. data/spec/models/transfer_type_bank_model_spec.rb +1 -1
  403. data/spec/models/travel_rule_info_party_bank_model_spec.rb +1 -1
  404. data/spec/models/workflow_bank_model_spec.rb +1 -1
  405. data/spec/models/workflow_state_bank_model_spec.rb +1 -1
  406. data/spec/models/workflow_type_bank_model_spec.rb +1 -1
  407. data/spec/models/workflow_with_details_all_of_bank_model_spec.rb +1 -1
  408. data/spec/models/workflow_with_details_bank_model_spec.rb +1 -1
  409. data/spec/models/workflows_list_bank_model_spec.rb +1 -1
  410. data/spec/spec_helper.rb +1 -1
  411. data/vendor/bundle/ruby/3.3.0/cache/ffi-1.17.4-x86_64-linux-gnu.gem +0 -0
  412. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/byebug-13.0.0/gem_make.out +5 -5
  413. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/date-3.5.1/gem_make.out +5 -5
  414. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/io-console-0.8.2/gem_make.out +5 -5
  415. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/jaro_winkler-1.5.6/gem_make.out +5 -5
  416. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/psych-5.3.1/gem_make.out +5 -5
  417. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/racc-1.8.1/gem_make.out +5 -5
  418. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/stringio-3.2.0/gem_make.out +5 -5
  419. data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/CHANGELOG.md +10 -1
  420. data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/ffi.gemspec +3 -1
  421. data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/3.0/ffi_c.so +0 -0
  422. data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/3.1/ffi_c.so +0 -0
  423. data/vendor/bundle/ruby/3.3.0/gems/ffi-1.17.4-x86_64-linux-gnu/lib/3.2/ffi_c.so +0 -0
  424. data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/3.3/ffi_c.so +0 -0
  425. data/vendor/bundle/ruby/3.3.0/gems/ffi-1.17.4-x86_64-linux-gnu/lib/3.4/ffi_c.so +0 -0
  426. data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/4.0/ffi_c.so +0 -0
  427. data/vendor/bundle/ruby/3.3.0/gems/ffi-1.17.4-x86_64-linux-gnu/lib/ffi/version.rb +3 -0
  428. data/vendor/bundle/ruby/3.3.0/specifications/{ffi-1.17.3-x86_64-linux-gnu.gemspec → ffi-1.17.4-x86_64-linux-gnu.gemspec} +2 -2
  429. metadata +135 -135
  430. data/vendor/bundle/ruby/3.3.0/cache/ffi-1.17.3-x86_64-linux-gnu.gem +0 -0
  431. data/vendor/bundle/ruby/3.3.0/gems/ffi-1.17.3-x86_64-linux-gnu/lib/3.2/ffi_c.so +0 -0
  432. data/vendor/bundle/ruby/3.3.0/gems/ffi-1.17.3-x86_64-linux-gnu/lib/3.4/ffi_c.so +0 -0
  433. data/vendor/bundle/ruby/3.3.0/gems/ffi-1.17.3-x86_64-linux-gnu/lib/ffi/version.rb +0 -3
  434. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/COPYING +0 -0
  435. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/Gemfile +0 -0
  436. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/LICENSE +0 -0
  437. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/LICENSE.SPECS +0 -0
  438. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/README.md +0 -0
  439. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/Rakefile +0 -0
  440. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/Steepfile +0 -0
  441. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/abstract_memory.rb +0 -0
  442. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/autopointer.rb +0 -0
  443. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/buffer.rb +0 -0
  444. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/callback.rb +0 -0
  445. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/compat.rb +0 -0
  446. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/data_converter.rb +0 -0
  447. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/dynamic_library.rb +0 -0
  448. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/enum.rb +0 -0
  449. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/errno.rb +0 -0
  450. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/ffi.rb +0 -0
  451. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/function.rb +0 -0
  452. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/io.rb +0 -0
  453. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/library.rb +0 -0
  454. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/library_path.rb +0 -0
  455. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/managedstruct.rb +0 -0
  456. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/memorypointer.rb +0 -0
  457. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/aarch64-darwin/types.conf +0 -0
  458. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/aarch64-freebsd/types.conf +0 -0
  459. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/aarch64-freebsd12/types.conf +0 -0
  460. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/aarch64-linux/types.conf +0 -0
  461. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/aarch64-openbsd/types.conf +0 -0
  462. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/aarch64-windows/types.conf +0 -0
  463. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/arm-freebsd/types.conf +0 -0
  464. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/arm-freebsd12/types.conf +0 -0
  465. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/arm-linux/types.conf +0 -0
  466. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/hppa1.1-linux/types.conf +0 -0
  467. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/hppa2.0-linux/types.conf +0 -0
  468. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/i386-cygwin/types.conf +0 -0
  469. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/i386-darwin/types.conf +0 -0
  470. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/i386-freebsd/types.conf +0 -0
  471. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/i386-freebsd12/types.conf +0 -0
  472. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/i386-gnu/types.conf +0 -0
  473. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/i386-linux/types.conf +0 -0
  474. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/i386-netbsd/types.conf +0 -0
  475. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/i386-openbsd/types.conf +0 -0
  476. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/i386-solaris/types.conf +0 -0
  477. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/i386-windows/types.conf +0 -0
  478. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/ia64-linux/types.conf +0 -0
  479. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/loongarch64-linux/types.conf +0 -0
  480. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/mips-linux/types.conf +0 -0
  481. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/mips64-linux/types.conf +0 -0
  482. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/mips64el-linux/types.conf +0 -0
  483. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/mipsel-linux/types.conf +0 -0
  484. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/mipsisa32r6-linux/types.conf +0 -0
  485. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/mipsisa32r6el-linux/types.conf +0 -0
  486. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/mipsisa64r6-linux/types.conf +0 -0
  487. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/mipsisa64r6el-linux/types.conf +0 -0
  488. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/powerpc-aix/types.conf +0 -0
  489. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/powerpc-darwin/types.conf +0 -0
  490. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/powerpc-linux/types.conf +0 -0
  491. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/powerpc-openbsd/types.conf +0 -0
  492. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/powerpc64-linux/types.conf +0 -0
  493. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/powerpc64le-linux/types.conf +0 -0
  494. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/riscv64-linux/types.conf +0 -0
  495. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/s390-linux/types.conf +0 -0
  496. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/s390x-linux/types.conf +0 -0
  497. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/sparc-linux/types.conf +0 -0
  498. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/sparc-solaris/types.conf +0 -0
  499. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/sparcv9-linux/types.conf +0 -0
  500. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/sparcv9-openbsd/types.conf +0 -0
  501. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/sparcv9-solaris/types.conf +0 -0
  502. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/sw_64-linux/types.conf +0 -0
  503. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-cygwin/types.conf +0 -0
  504. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-darwin/types.conf +0 -0
  505. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-dragonflybsd/types.conf +0 -0
  506. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-freebsd/types.conf +0 -0
  507. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-freebsd12/types.conf +0 -0
  508. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-haiku/types.conf +0 -0
  509. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-linux/types.conf +0 -0
  510. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-msys/types.conf +0 -0
  511. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-netbsd/types.conf +0 -0
  512. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-openbsd/types.conf +0 -0
  513. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-solaris/types.conf +0 -0
  514. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform/x86_64-windows/types.conf +0 -0
  515. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/platform.rb +0 -0
  516. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/pointer.rb +0 -0
  517. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/struct.rb +0 -0
  518. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/struct_by_reference.rb +0 -0
  519. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/struct_layout.rb +0 -0
  520. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/struct_layout_builder.rb +0 -0
  521. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/tools/const_generator.rb +0 -0
  522. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/tools/generator.rb +0 -0
  523. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/tools/generator_task.rb +0 -0
  524. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/tools/struct_generator.rb +0 -0
  525. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/types.rb +0 -0
  526. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/union.rb +0 -0
  527. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi/variadic.rb +0 -0
  528. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/lib/ffi.rb +0 -0
  529. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/samples/getlogin.rb +0 -0
  530. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/samples/getpid.rb +0 -0
  531. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/samples/gettimeofday.rb +0 -0
  532. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/samples/hello.rb +0 -0
  533. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/samples/hello_ractor.rb +0 -0
  534. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/samples/inotify.rb +0 -0
  535. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/samples/pty.rb +0 -0
  536. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/samples/qsort.rb +0 -0
  537. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/samples/qsort_ractor.rb +0 -0
  538. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/abstract_memory.rbs +0 -0
  539. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/auto_pointer.rbs +0 -0
  540. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/buffer.rbs +0 -0
  541. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/data_converter.rbs +0 -0
  542. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/dynamic_library.rbs +0 -0
  543. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/enum.rbs +0 -0
  544. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/errno.rbs +0 -0
  545. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/function.rbs +0 -0
  546. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/library.rbs +0 -0
  547. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/native_type.rbs +0 -0
  548. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/platform.rbs +0 -0
  549. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/pointer.rbs +0 -0
  550. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/struct.rbs +0 -0
  551. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/struct_by_reference.rbs +0 -0
  552. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/struct_by_value.rbs +0 -0
  553. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/struct_layout.rbs +0 -0
  554. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/struct_layout_builder.rbs +0 -0
  555. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi/type.rbs +0 -0
  556. /data/vendor/bundle/ruby/3.3.0/gems/{ffi-1.17.3-x86_64-linux-gnu → ffi-1.17.4-x86_64-linux-gnu}/sig/ffi.rbs +0 -0
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 9b88cec918f51d4988d3ad8dd8385f949075e35f0e1dc0913f90ae73cef49335
4
- data.tar.gz: a6a1dfc628af995d09dbd4bf5b7657b39cd41bee9dfcf78c073c3b44f4fcc095
3
+ metadata.gz: d5e42d4c1180ade1b7d2fca4de3a8c8afaa871f920eff09ae07a91116cc4b65f
4
+ data.tar.gz: 4aea22914d665e6c7873ce385bbfdd129fda2d3fd50b4c99122691d053c3db39
5
5
  SHA512:
6
- metadata.gz: 390ecda09803f29624c897c2da772872aa1ba938e33dd2ddcf4bb9adfc182d5a57c6ac5489524b4855b2bbef68de7eb3d3d62a39b42849a32d9b778bb6db5062
7
- data.tar.gz: a7e20e9af5b4e43c82450557ba00d6ba782f888662a5daf20613f94701b8e87f9ad498aa73df7cbd2bd89606878048a7a4179b085bfab7dbb4aa8e72429373dd
6
+ metadata.gz: 1f9be4e085dc9b924af01f77d1ac62e805003b54c6a323671f87acc95dca374d483146d0e03765d9a12af03f60f5aa9f3899ecb38c225512809b8ce2c86c1bd4
7
+ data.tar.gz: 4e35f6cb874168f8b0ee4ac26bbf775c5f627f59cf9fad4c2ac1ee693079ddb16196e7dbaba25bae59ded9d818d4fa5af4e0c7e727fcd0f1949879ea4ff9d14c
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- cybrid_api_bank_ruby (0.128.60)
4
+ cybrid_api_bank_ruby (0.128.61)
5
5
  typhoeus (~> 1.0, >= 1.0.1)
6
6
 
7
7
  GEM
@@ -16,17 +16,17 @@ GEM
16
16
  ethon (0.18.0)
17
17
  ffi (>= 1.15.0)
18
18
  logger
19
- ffi (1.17.3)
20
- ffi (1.17.3-aarch64-linux-gnu)
21
- ffi (1.17.3-aarch64-linux-musl)
22
- ffi (1.17.3-arm-linux-gnu)
23
- ffi (1.17.3-arm-linux-musl)
24
- ffi (1.17.3-arm64-darwin)
25
- ffi (1.17.3-x86-linux-gnu)
26
- ffi (1.17.3-x86-linux-musl)
27
- ffi (1.17.3-x86_64-darwin)
28
- ffi (1.17.3-x86_64-linux-gnu)
29
- ffi (1.17.3-x86_64-linux-musl)
19
+ ffi (1.17.4)
20
+ ffi (1.17.4-aarch64-linux-gnu)
21
+ ffi (1.17.4-aarch64-linux-musl)
22
+ ffi (1.17.4-arm-linux-gnu)
23
+ ffi (1.17.4-arm-linux-musl)
24
+ ffi (1.17.4-arm64-darwin)
25
+ ffi (1.17.4-x86-linux-gnu)
26
+ ffi (1.17.4-x86-linux-musl)
27
+ ffi (1.17.4-x86_64-darwin)
28
+ ffi (1.17.4-x86_64-linux-gnu)
29
+ ffi (1.17.4-x86_64-linux-musl)
30
30
  io-console (0.8.2)
31
31
  jaro_winkler (1.5.6)
32
32
  logger (1.7.0)
@@ -101,21 +101,21 @@ CHECKSUMS
101
101
  ast (2.4.3) sha256=954615157c1d6a382bc27d690d973195e79db7f55e9765ac7c481c60bdb4d383
102
102
  byebug (13.0.0) sha256=d2263efe751941ca520fa29744b71972d39cbc41839496706f5d9b22e92ae05d
103
103
  coderay (1.1.3) sha256=dc530018a4684512f8f38143cd2a096c9f02a1fc2459edcfe534787a7fc77d4b
104
- cybrid_api_bank_ruby (0.128.60)
104
+ cybrid_api_bank_ruby (0.128.61)
105
105
  date (3.5.1) sha256=750d06384d7b9c15d562c76291407d89e368dda4d4fff957eb94962d325a0dc0
106
106
  diff-lcs (1.6.2) sha256=9ae0d2cba7d4df3075fe8cd8602a8604993efc0dfa934cff568969efb1909962
107
107
  ethon (0.18.0) sha256=b598afc9f30448cb068b850714b7d6948e941476095d04f90a4ac65b8d6efcb2
108
- ffi (1.17.3) sha256=0e9f39f7bb3934f77ad6feab49662be77e87eedcdeb2a3f5c0234c2938563d4c
109
- ffi (1.17.3-aarch64-linux-gnu) sha256=28ad573df26560f0aedd8a90c3371279a0b2bd0b4e834b16a2baa10bd7a97068
110
- ffi (1.17.3-aarch64-linux-musl) sha256=020b33b76775b1abacc3b7d86b287cef3251f66d747092deec592c7f5df764b2
111
- ffi (1.17.3-arm-linux-gnu) sha256=5bd4cea83b68b5ec0037f99c57d5ce2dd5aa438f35decc5ef68a7d085c785668
112
- ffi (1.17.3-arm-linux-musl) sha256=0d7626bb96265f9af78afa33e267d71cfef9d9a8eb8f5525344f8da6c7d76053
113
- ffi (1.17.3-arm64-darwin) sha256=0c690555d4cee17a7f07c04d59df39b2fba74ec440b19da1f685c6579bb0717f
114
- ffi (1.17.3-x86-linux-gnu) sha256=868a88fcaf5186c3a46b7c7c2b2c34550e1e61a405670ab23f5b6c9971529089
115
- ffi (1.17.3-x86-linux-musl) sha256=f0286aa6ef40605cf586e61406c446de34397b85dbb08cc99fdaddaef8343945
116
- ffi (1.17.3-x86_64-darwin) sha256=1f211811eb5cfaa25998322cdd92ab104bfbd26d1c4c08471599c511f2c00bb5
117
- ffi (1.17.3-x86_64-linux-gnu) sha256=3746b01f677aae7b16dc1acb7cb3cc17b3e35bdae7676a3f568153fb0e2c887f
118
- ffi (1.17.3-x86_64-linux-musl) sha256=086b221c3a68320b7564066f46fed23449a44f7a1935f1fe5a245bd89d9aea56
108
+ ffi (1.17.4) sha256=bcd1642e06f0d16fc9e09ac6d49c3a7298b9789bcb58127302f934e437d60acf
109
+ ffi (1.17.4-aarch64-linux-gnu) sha256=b208f06f91ffd8f5e1193da3cae3d2ccfc27fc36fba577baf698d26d91c080df
110
+ ffi (1.17.4-aarch64-linux-musl) sha256=9286b7a615f2676245283aef0a0a3b475ae3aae2bb5448baace630bb77b91f39
111
+ ffi (1.17.4-arm-linux-gnu) sha256=d6dbddf7cb77bf955411af5f187a65b8cd378cb003c15c05697f5feee1cb1564
112
+ ffi (1.17.4-arm-linux-musl) sha256=9d4838ded0465bef6e2426935f6bcc93134b6616785a84ffd2a3d82bc3cf6f95
113
+ ffi (1.17.4-arm64-darwin) sha256=19071aaf1419251b0a46852abf960e77330a3b334d13a4ab51d58b31a937001b
114
+ ffi (1.17.4-x86-linux-gnu) sha256=38e150df5f4ca555e25beca4090823ae09657bceded154e3c52f8631c1ed72cf
115
+ ffi (1.17.4-x86-linux-musl) sha256=fbeec0fc7c795bcf86f623bb18d31ea1820f7bd580e1703a3d3740d527437809
116
+ ffi (1.17.4-x86_64-darwin) sha256=aa70390523cf3235096cf64962b709b4cfbd5c082a2cb2ae714eb0fe2ccda496
117
+ ffi (1.17.4-x86_64-linux-gnu) sha256=9d3db14c2eae074b382fa9c083fe95aec6e0a1451da249eab096c34002bc752d
118
+ ffi (1.17.4-x86_64-linux-musl) sha256=3fdf9888483de005f8ef8d1cf2d3b20d86626af206cbf780f6a6a12439a9c49e
119
119
  io-console (0.8.2) sha256=d6e3ae7a7cc7574f4b8893b4fca2162e57a825b223a177b7afa236c5ef9814cc
120
120
  jaro_winkler (1.5.6) sha256=007db7805527ada1cc12f2547676181d63b0a504ec4dd7a9a2eb2424521ccd81
121
121
  logger (1.7.0) sha256=196edec7cc44b66cfb40f9755ce11b392f21f7967696af15d274dde7edff0203
data/README.md CHANGED
@@ -151,8 +151,8 @@ An `Organization` can have multiple `banks`, in either `Sandbox` or `Production`
151
151
 
152
152
  This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
153
153
 
154
- - API version: v0.128.60
155
- - Package version: 0.128.60
154
+ - API version: v0.128.61
155
+ - Package version: 0.128.61
156
156
  - Build package: org.openapitools.codegen.languages.RubyClientCodegen
157
157
 
158
158
  ## Installation
@@ -168,16 +168,16 @@ gem build cybrid_api_bank_ruby.gemspec
168
168
  Then either install the gem locally:
169
169
 
170
170
  ```shell
171
- gem install ./cybrid_api_bank_ruby-0.128.60.gem
171
+ gem install ./cybrid_api_bank_ruby-0.128.61.gem
172
172
  ```
173
173
 
174
- (for development, run `gem install --dev ./cybrid_api_bank_ruby-0.128.60.gem` to install the development dependencies)
174
+ (for development, run `gem install --dev ./cybrid_api_bank_ruby-0.128.61.gem` to install the development dependencies)
175
175
 
176
176
  or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
177
177
 
178
178
  Finally add this to the Gemfile:
179
179
 
180
- gem 'cybrid_api_bank_ruby', '~> 0.128.60'
180
+ gem 'cybrid_api_bank_ruby', '~> 0.128.61'
181
181
 
182
182
  ### Install from Git
183
183
 
data/cybrid_api_bank_ruby.gemspec CHANGED
@@ -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.production.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. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), 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://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## 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.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.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.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.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.production.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.production.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 counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # 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:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <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) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.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 | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `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.128.60
8
+ The version of the OpenAPI document: v0.128.61
9
9
  Contact: support@cybrid.app
10
10
  Generated by: https://openapi-generator.tech
11
11
  OpenAPI Generator version: 6.0.0
data/lib/cybrid_api_bank_ruby/api/accounts_bank_api.rb CHANGED
@@ -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.production.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. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), 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://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## 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.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.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.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.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.production.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.production.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 counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # 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:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <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) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.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 | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `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.128.60
6
+ The version of the OpenAPI document: v0.128.61
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
data/lib/cybrid_api_bank_ruby/api/assets_bank_api.rb CHANGED
@@ -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.production.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. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), 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://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## 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.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.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.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.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.production.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.production.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 counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # 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:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <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) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.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 | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `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.128.60
6
+ The version of the OpenAPI document: v0.128.61
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
data/lib/cybrid_api_bank_ruby/api/banks_bank_api.rb CHANGED
@@ -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.production.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. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), 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://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## 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.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.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.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.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.production.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.production.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 counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # 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:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <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) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.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 | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `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.128.60
6
+ The version of the OpenAPI document: v0.128.61
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
data/lib/cybrid_api_bank_ruby/api/counterparties_bank_api.rb CHANGED
@@ -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.production.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. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), 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://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## 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.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.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.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.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.production.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.production.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 counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # 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:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <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) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.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 | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `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.128.60
6
+ The version of the OpenAPI document: v0.128.61
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
data/lib/cybrid_api_bank_ruby/api/customers_bank_api.rb CHANGED
@@ -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.production.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. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), 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://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## 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.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.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.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.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.production.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.production.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 counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # 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:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <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) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.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 | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `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.128.60
6
+ The version of the OpenAPI document: v0.128.61
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
data/lib/cybrid_api_bank_ruby/api/deposit_addresses_bank_api.rb CHANGED
@@ -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.production.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. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), 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://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## 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.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.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.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.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.production.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.production.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 counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # 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:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <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) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.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 | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `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.128.60
6
+ The version of the OpenAPI document: v0.128.61
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
data/lib/cybrid_api_bank_ruby/api/deposit_bank_accounts_bank_api.rb CHANGED
@@ -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.production.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. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), 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://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## 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.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.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.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.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.production.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.production.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 counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # 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:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <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) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.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 | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `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.128.60
6
+ The version of the OpenAPI document: v0.128.61
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
data/lib/cybrid_api_bank_ruby/api/executions_bank_api.rb CHANGED
@@ -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.production.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. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), 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://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## 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.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.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.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.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.production.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.production.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 counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # 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:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <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) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.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 | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `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.128.60
6
+ The version of the OpenAPI document: v0.128.61
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0