cybrid_api_bank_ruby 0.113.154 → 0.114.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (271) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +1 -1
  3. data/README.md +25 -7
  4. data/cybrid_api_bank_ruby.gemspec +2 -2
  5. data/docs/InvoiceBankModel.md +40 -0
  6. data/docs/InvoiceListBankModel.md +24 -0
  7. data/docs/InvoicesBankApi.md +240 -0
  8. data/docs/PaymentInstructionBankModel.md +36 -0
  9. data/docs/PaymentInstructionListBankModel.md +24 -0
  10. data/docs/PaymentInstructionsBankApi.md +238 -0
  11. data/docs/PostInvoiceBankModel.md +26 -0
  12. data/docs/PostPaymentInstructionBankModel.md +20 -0
  13. data/lib/cybrid_api_bank_ruby/api/accounts_bank_api.rb +2 -2
  14. data/lib/cybrid_api_bank_ruby/api/assets_bank_api.rb +2 -2
  15. data/lib/cybrid_api_bank_ruby/api/banks_bank_api.rb +2 -2
  16. data/lib/cybrid_api_bank_ruby/api/customers_bank_api.rb +2 -2
  17. data/lib/cybrid_api_bank_ruby/api/deposit_addresses_bank_api.rb +2 -2
  18. data/lib/cybrid_api_bank_ruby/api/deposit_bank_accounts_bank_api.rb +2 -2
  19. data/lib/cybrid_api_bank_ruby/api/external_bank_accounts_bank_api.rb +2 -2
  20. data/lib/cybrid_api_bank_ruby/api/external_wallets_bank_api.rb +2 -2
  21. data/lib/cybrid_api_bank_ruby/api/identity_verifications_bank_api.rb +2 -2
  22. data/lib/cybrid_api_bank_ruby/api/invoices_bank_api.rb +243 -0
  23. data/lib/cybrid_api_bank_ruby/api/payment_instructions_bank_api.rb +240 -0
  24. data/lib/cybrid_api_bank_ruby/api/prices_bank_api.rb +2 -2
  25. data/lib/cybrid_api_bank_ruby/api/quotes_bank_api.rb +2 -2
  26. data/lib/cybrid_api_bank_ruby/api/symbols_bank_api.rb +2 -2
  27. data/lib/cybrid_api_bank_ruby/api/trades_bank_api.rb +2 -2
  28. data/lib/cybrid_api_bank_ruby/api/transfers_bank_api.rb +2 -2
  29. data/lib/cybrid_api_bank_ruby/api/workflows_bank_api.rb +2 -2
  30. data/lib/cybrid_api_bank_ruby/api_client.rb +2 -2
  31. data/lib/cybrid_api_bank_ruby/api_error.rb +2 -2
  32. data/lib/cybrid_api_bank_ruby/configuration.rb +2 -2
  33. data/lib/cybrid_api_bank_ruby/models/account_bank_model.rb +2 -2
  34. data/lib/cybrid_api_bank_ruby/models/account_list_bank_model.rb +2 -2
  35. data/lib/cybrid_api_bank_ruby/models/account_state_bank_model.rb +2 -2
  36. data/lib/cybrid_api_bank_ruby/models/account_type_bank_model.rb +2 -2
  37. data/lib/cybrid_api_bank_ruby/models/asset_bank_model.rb +2 -2
  38. data/lib/cybrid_api_bank_ruby/models/asset_list_bank_model.rb +2 -2
  39. data/lib/cybrid_api_bank_ruby/models/asset_types_bank_model.rb +2 -2
  40. data/lib/cybrid_api_bank_ruby/models/bank_bank_model.rb +2 -2
  41. data/lib/cybrid_api_bank_ruby/models/bank_feature_bank_model.rb +2 -2
  42. data/lib/cybrid_api_bank_ruby/models/bank_list_bank_model.rb +2 -2
  43. data/lib/cybrid_api_bank_ruby/models/bank_type_bank_model.rb +2 -2
  44. data/lib/cybrid_api_bank_ruby/models/customer_address_bank_model.rb +2 -2
  45. data/lib/cybrid_api_bank_ruby/models/customer_bank_model.rb +2 -2
  46. data/lib/cybrid_api_bank_ruby/models/customer_list_bank_model.rb +2 -2
  47. data/lib/cybrid_api_bank_ruby/models/customer_name_bank_model.rb +2 -2
  48. data/lib/cybrid_api_bank_ruby/models/customer_state_bank_model.rb +2 -2
  49. data/lib/cybrid_api_bank_ruby/models/customer_type_bank_model.rb +2 -2
  50. data/lib/cybrid_api_bank_ruby/models/deposit_address_bank_model.rb +2 -2
  51. data/lib/cybrid_api_bank_ruby/models/deposit_address_format_bank_model.rb +2 -2
  52. data/lib/cybrid_api_bank_ruby/models/deposit_address_list_bank_model.rb +2 -2
  53. data/lib/cybrid_api_bank_ruby/models/deposit_address_state_bank_model.rb +2 -2
  54. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_account_details_inner_bank_model.rb +2 -2
  55. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_bank_model.rb +2 -2
  56. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_counterparty_address_bank_model.rb +2 -2
  57. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_list_bank_model.rb +2 -2
  58. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_routing_details_inner_bank_model.rb +2 -2
  59. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_routing_number_type_bank_model.rb +2 -2
  60. data/lib/cybrid_api_bank_ruby/models/deposit_bank_account_state_bank_model.rb +2 -2
  61. data/lib/cybrid_api_bank_ruby/models/error_response_bank_model.rb +2 -2
  62. data/lib/cybrid_api_bank_ruby/models/external_bank_account_balances_bank_model.rb +2 -2
  63. data/lib/cybrid_api_bank_ruby/models/external_bank_account_bank_model.rb +2 -2
  64. data/lib/cybrid_api_bank_ruby/models/external_bank_account_kind_bank_model.rb +2 -2
  65. data/lib/cybrid_api_bank_ruby/models/external_bank_account_list_bank_model.rb +2 -2
  66. data/lib/cybrid_api_bank_ruby/models/external_bank_account_pii_inner_addresses_inner_bank_model.rb +2 -2
  67. data/lib/cybrid_api_bank_ruby/models/external_bank_account_pii_inner_bank_model.rb +2 -2
  68. data/lib/cybrid_api_bank_ruby/models/external_bank_account_state_bank_model.rb +2 -2
  69. data/lib/cybrid_api_bank_ruby/models/external_wallet_bank_model.rb +2 -2
  70. data/lib/cybrid_api_bank_ruby/models/external_wallet_environment_bank_model.rb +2 -2
  71. data/lib/cybrid_api_bank_ruby/models/external_wallet_list_bank_model.rb +2 -2
  72. data/lib/cybrid_api_bank_ruby/models/external_wallet_state_bank_model.rb +2 -2
  73. data/lib/cybrid_api_bank_ruby/models/identity_verification_bank_model.rb +2 -2
  74. data/lib/cybrid_api_bank_ruby/models/identity_verification_list_bank_model.rb +2 -2
  75. data/lib/cybrid_api_bank_ruby/models/identity_verification_method_bank_model.rb +2 -2
  76. data/lib/cybrid_api_bank_ruby/models/identity_verification_outcome_bank_model.rb +2 -2
  77. data/lib/cybrid_api_bank_ruby/models/identity_verification_persona_state_bank_model.rb +2 -2
  78. data/lib/cybrid_api_bank_ruby/models/identity_verification_state_bank_model.rb +2 -2
  79. data/lib/cybrid_api_bank_ruby/models/identity_verification_type_bank_model.rb +2 -2
  80. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_all_of_bank_model.rb +2 -2
  81. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_bank_model.rb +2 -2
  82. data/lib/cybrid_api_bank_ruby/models/invoice_bank_model.rb +433 -0
  83. data/lib/cybrid_api_bank_ruby/models/invoice_list_bank_model.rb +328 -0
  84. data/lib/cybrid_api_bank_ruby/models/patch_bank_bank_model.rb +2 -2
  85. data/lib/cybrid_api_bank_ruby/models/patch_customer_bank_model.rb +2 -2
  86. data/lib/cybrid_api_bank_ruby/models/patch_external_bank_account_bank_model.rb +2 -2
  87. data/lib/cybrid_api_bank_ruby/models/payment_instruction_bank_model.rb +387 -0
  88. data/lib/cybrid_api_bank_ruby/models/payment_instruction_list_bank_model.rb +328 -0
  89. data/lib/cybrid_api_bank_ruby/models/post_account_bank_model.rb +2 -2
  90. data/lib/cybrid_api_bank_ruby/models/post_bank_bank_model.rb +2 -2
  91. data/lib/cybrid_api_bank_ruby/models/post_customer_address_bank_model.rb +2 -2
  92. data/lib/cybrid_api_bank_ruby/models/post_customer_bank_model.rb +2 -2
  93. data/lib/cybrid_api_bank_ruby/models/post_customer_name_bank_model.rb +2 -2
  94. data/lib/cybrid_api_bank_ruby/models/post_deposit_address_bank_model.rb +2 -2
  95. data/lib/cybrid_api_bank_ruby/models/post_deposit_bank_account_bank_model.rb +2 -2
  96. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_bank_model.rb +2 -2
  97. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_address_bank_model.rb +2 -2
  98. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_bank_account_bank_model.rb +2 -2
  99. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_counterparty_name_bank_model.rb +2 -2
  100. data/lib/cybrid_api_bank_ruby/models/post_external_wallet_bank_model.rb +2 -2
  101. data/lib/cybrid_api_bank_ruby/models/post_identification_number_bank_model.rb +2 -2
  102. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_address_bank_model.rb +2 -2
  103. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_bank_model.rb +2 -2
  104. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_name_bank_model.rb +2 -2
  105. data/lib/cybrid_api_bank_ruby/models/post_invoice_bank_model.rb +323 -0
  106. data/lib/cybrid_api_bank_ruby/models/post_payment_instruction_bank_model.rb +288 -0
  107. data/lib/cybrid_api_bank_ruby/models/post_quote_bank_model.rb +2 -2
  108. data/lib/cybrid_api_bank_ruby/models/post_trade_bank_model.rb +2 -2
  109. data/lib/cybrid_api_bank_ruby/models/post_transfer_bank_model.rb +2 -2
  110. data/lib/cybrid_api_bank_ruby/models/post_workflow_bank_model.rb +2 -2
  111. data/lib/cybrid_api_bank_ruby/models/quote_bank_model.rb +2 -2
  112. data/lib/cybrid_api_bank_ruby/models/quote_list_bank_model.rb +2 -2
  113. data/lib/cybrid_api_bank_ruby/models/quote_side_bank_model.rb +2 -2
  114. data/lib/cybrid_api_bank_ruby/models/quote_type_bank_model.rb +2 -2
  115. data/lib/cybrid_api_bank_ruby/models/symbol_price_bank_model.rb +2 -2
  116. data/lib/cybrid_api_bank_ruby/models/trade_bank_model.rb +2 -2
  117. data/lib/cybrid_api_bank_ruby/models/trade_list_bank_model.rb +2 -2
  118. data/lib/cybrid_api_bank_ruby/models/trade_side_bank_model.rb +2 -2
  119. data/lib/cybrid_api_bank_ruby/models/trade_state_bank_model.rb +2 -2
  120. data/lib/cybrid_api_bank_ruby/models/trade_type_bank_model.rb +2 -2
  121. data/lib/cybrid_api_bank_ruby/models/transfer_account_type_bank_model.rb +2 -2
  122. data/lib/cybrid_api_bank_ruby/models/transfer_bank_model.rb +2 -2
  123. data/lib/cybrid_api_bank_ruby/models/transfer_destination_account_bank_model.rb +2 -2
  124. data/lib/cybrid_api_bank_ruby/models/transfer_list_bank_model.rb +2 -2
  125. data/lib/cybrid_api_bank_ruby/models/transfer_side_bank_model.rb +2 -2
  126. data/lib/cybrid_api_bank_ruby/models/transfer_source_account_bank_model.rb +2 -2
  127. data/lib/cybrid_api_bank_ruby/models/transfer_state_bank_model.rb +2 -2
  128. data/lib/cybrid_api_bank_ruby/models/transfer_type_bank_model.rb +2 -2
  129. data/lib/cybrid_api_bank_ruby/models/verification_check_bank_model.rb +2 -2
  130. data/lib/cybrid_api_bank_ruby/models/verification_check_state_bank_model.rb +2 -2
  131. data/lib/cybrid_api_bank_ruby/models/verification_check_type_bank_model.rb +2 -2
  132. data/lib/cybrid_api_bank_ruby/models/workflow_bank_model.rb +2 -2
  133. data/lib/cybrid_api_bank_ruby/models/workflow_state_bank_model.rb +2 -2
  134. data/lib/cybrid_api_bank_ruby/models/workflow_type_bank_model.rb +2 -2
  135. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_all_of_bank_model.rb +2 -2
  136. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_bank_model.rb +2 -2
  137. data/lib/cybrid_api_bank_ruby/models/workflows_list_bank_model.rb +2 -2
  138. data/lib/cybrid_api_bank_ruby/version.rb +3 -3
  139. data/lib/cybrid_api_bank_ruby.rb +10 -2
  140. data/spec/api/accounts_bank_api_spec.rb +2 -2
  141. data/spec/api/assets_bank_api_spec.rb +2 -2
  142. data/spec/api/banks_bank_api_spec.rb +2 -2
  143. data/spec/api/customers_bank_api_spec.rb +2 -2
  144. data/spec/api/deposit_addresses_bank_api_spec.rb +2 -2
  145. data/spec/api/deposit_bank_accounts_bank_api_spec.rb +2 -2
  146. data/spec/api/external_bank_accounts_bank_api_spec.rb +2 -2
  147. data/spec/api/external_wallets_bank_api_spec.rb +2 -2
  148. data/spec/api/identity_verifications_bank_api_spec.rb +2 -2
  149. data/spec/api/invoices_bank_api_spec.rb +77 -0
  150. data/spec/api/payment_instructions_bank_api_spec.rb +76 -0
  151. data/spec/api/prices_bank_api_spec.rb +2 -2
  152. data/spec/api/quotes_bank_api_spec.rb +2 -2
  153. data/spec/api/symbols_bank_api_spec.rb +2 -2
  154. data/spec/api/trades_bank_api_spec.rb +2 -2
  155. data/spec/api/transfers_bank_api_spec.rb +2 -2
  156. data/spec/api/workflows_bank_api_spec.rb +2 -2
  157. data/spec/api_client_spec.rb +2 -2
  158. data/spec/configuration_spec.rb +2 -2
  159. data/spec/models/account_bank_model_spec.rb +2 -2
  160. data/spec/models/account_list_bank_model_spec.rb +2 -2
  161. data/spec/models/account_state_bank_model_spec.rb +2 -2
  162. data/spec/models/account_type_bank_model_spec.rb +2 -2
  163. data/spec/models/asset_bank_model_spec.rb +2 -2
  164. data/spec/models/asset_list_bank_model_spec.rb +2 -2
  165. data/spec/models/asset_types_bank_model_spec.rb +2 -2
  166. data/spec/models/bank_bank_model_spec.rb +2 -2
  167. data/spec/models/bank_feature_bank_model_spec.rb +2 -2
  168. data/spec/models/bank_list_bank_model_spec.rb +2 -2
  169. data/spec/models/bank_type_bank_model_spec.rb +2 -2
  170. data/spec/models/customer_address_bank_model_spec.rb +2 -2
  171. data/spec/models/customer_bank_model_spec.rb +2 -2
  172. data/spec/models/customer_list_bank_model_spec.rb +2 -2
  173. data/spec/models/customer_name_bank_model_spec.rb +2 -2
  174. data/spec/models/customer_state_bank_model_spec.rb +2 -2
  175. data/spec/models/customer_type_bank_model_spec.rb +2 -2
  176. data/spec/models/deposit_address_bank_model_spec.rb +2 -2
  177. data/spec/models/deposit_address_format_bank_model_spec.rb +2 -2
  178. data/spec/models/deposit_address_list_bank_model_spec.rb +2 -2
  179. data/spec/models/deposit_address_state_bank_model_spec.rb +2 -2
  180. data/spec/models/deposit_bank_account_account_details_inner_bank_model_spec.rb +2 -2
  181. data/spec/models/deposit_bank_account_bank_model_spec.rb +2 -2
  182. data/spec/models/deposit_bank_account_counterparty_address_bank_model_spec.rb +2 -2
  183. data/spec/models/deposit_bank_account_list_bank_model_spec.rb +2 -2
  184. data/spec/models/deposit_bank_account_routing_details_inner_bank_model_spec.rb +2 -2
  185. data/spec/models/deposit_bank_account_routing_number_type_bank_model_spec.rb +2 -2
  186. data/spec/models/deposit_bank_account_state_bank_model_spec.rb +2 -2
  187. data/spec/models/error_response_bank_model_spec.rb +2 -2
  188. data/spec/models/external_bank_account_balances_bank_model_spec.rb +2 -2
  189. data/spec/models/external_bank_account_bank_model_spec.rb +2 -2
  190. data/spec/models/external_bank_account_kind_bank_model_spec.rb +2 -2
  191. data/spec/models/external_bank_account_list_bank_model_spec.rb +2 -2
  192. data/spec/models/external_bank_account_pii_inner_addresses_inner_bank_model_spec.rb +2 -2
  193. data/spec/models/external_bank_account_pii_inner_bank_model_spec.rb +2 -2
  194. data/spec/models/external_bank_account_state_bank_model_spec.rb +2 -2
  195. data/spec/models/external_wallet_bank_model_spec.rb +2 -2
  196. data/spec/models/external_wallet_environment_bank_model_spec.rb +2 -2
  197. data/spec/models/external_wallet_list_bank_model_spec.rb +2 -2
  198. data/spec/models/external_wallet_state_bank_model_spec.rb +2 -2
  199. data/spec/models/identity_verification_bank_model_spec.rb +2 -2
  200. data/spec/models/identity_verification_list_bank_model_spec.rb +2 -2
  201. data/spec/models/identity_verification_method_bank_model_spec.rb +2 -2
  202. data/spec/models/identity_verification_outcome_bank_model_spec.rb +2 -2
  203. data/spec/models/identity_verification_persona_state_bank_model_spec.rb +2 -2
  204. data/spec/models/identity_verification_state_bank_model_spec.rb +2 -2
  205. data/spec/models/identity_verification_type_bank_model_spec.rb +2 -2
  206. data/spec/models/identity_verification_with_details_all_of_bank_model_spec.rb +2 -2
  207. data/spec/models/identity_verification_with_details_bank_model_spec.rb +2 -2
  208. data/spec/models/invoice_bank_model_spec.rb +100 -0
  209. data/spec/models/invoice_list_bank_model_spec.rb +52 -0
  210. data/spec/models/patch_bank_bank_model_spec.rb +2 -2
  211. data/spec/models/patch_customer_bank_model_spec.rb +2 -2
  212. data/spec/models/patch_external_bank_account_bank_model_spec.rb +2 -2
  213. data/spec/models/payment_instruction_bank_model_spec.rb +88 -0
  214. data/spec/models/payment_instruction_list_bank_model_spec.rb +52 -0
  215. data/spec/models/post_account_bank_model_spec.rb +2 -2
  216. data/spec/models/post_bank_bank_model_spec.rb +2 -2
  217. data/spec/models/post_customer_address_bank_model_spec.rb +2 -2
  218. data/spec/models/post_customer_bank_model_spec.rb +2 -2
  219. data/spec/models/post_customer_name_bank_model_spec.rb +2 -2
  220. data/spec/models/post_deposit_address_bank_model_spec.rb +2 -2
  221. data/spec/models/post_deposit_bank_account_bank_model_spec.rb +2 -2
  222. data/spec/models/post_external_bank_account_bank_model_spec.rb +2 -2
  223. data/spec/models/post_external_bank_account_counterparty_address_bank_model_spec.rb +2 -2
  224. data/spec/models/post_external_bank_account_counterparty_bank_account_bank_model_spec.rb +2 -2
  225. data/spec/models/post_external_bank_account_counterparty_name_bank_model_spec.rb +2 -2
  226. data/spec/models/post_external_wallet_bank_model_spec.rb +2 -2
  227. data/spec/models/post_identification_number_bank_model_spec.rb +2 -2
  228. data/spec/models/post_identity_verification_address_bank_model_spec.rb +2 -2
  229. data/spec/models/post_identity_verification_bank_model_spec.rb +2 -2
  230. data/spec/models/post_identity_verification_name_bank_model_spec.rb +2 -2
  231. data/spec/models/post_invoice_bank_model_spec.rb +58 -0
  232. data/spec/models/post_payment_instruction_bank_model_spec.rb +40 -0
  233. data/spec/models/post_quote_bank_model_spec.rb +2 -2
  234. data/spec/models/post_trade_bank_model_spec.rb +2 -2
  235. data/spec/models/post_transfer_bank_model_spec.rb +2 -2
  236. data/spec/models/post_workflow_bank_model_spec.rb +2 -2
  237. data/spec/models/quote_bank_model_spec.rb +2 -2
  238. data/spec/models/quote_list_bank_model_spec.rb +2 -2
  239. data/spec/models/quote_side_bank_model_spec.rb +2 -2
  240. data/spec/models/quote_type_bank_model_spec.rb +2 -2
  241. data/spec/models/symbol_price_bank_model_spec.rb +2 -2
  242. data/spec/models/trade_bank_model_spec.rb +2 -2
  243. data/spec/models/trade_list_bank_model_spec.rb +2 -2
  244. data/spec/models/trade_side_bank_model_spec.rb +2 -2
  245. data/spec/models/trade_state_bank_model_spec.rb +2 -2
  246. data/spec/models/trade_type_bank_model_spec.rb +2 -2
  247. data/spec/models/transfer_account_type_bank_model_spec.rb +2 -2
  248. data/spec/models/transfer_bank_model_spec.rb +2 -2
  249. data/spec/models/transfer_destination_account_bank_model_spec.rb +2 -2
  250. data/spec/models/transfer_list_bank_model_spec.rb +2 -2
  251. data/spec/models/transfer_side_bank_model_spec.rb +2 -2
  252. data/spec/models/transfer_source_account_bank_model_spec.rb +2 -2
  253. data/spec/models/transfer_state_bank_model_spec.rb +2 -2
  254. data/spec/models/transfer_type_bank_model_spec.rb +2 -2
  255. data/spec/models/verification_check_bank_model_spec.rb +2 -2
  256. data/spec/models/verification_check_state_bank_model_spec.rb +2 -2
  257. data/spec/models/verification_check_type_bank_model_spec.rb +2 -2
  258. data/spec/models/workflow_bank_model_spec.rb +2 -2
  259. data/spec/models/workflow_state_bank_model_spec.rb +2 -2
  260. data/spec/models/workflow_type_bank_model_spec.rb +2 -2
  261. data/spec/models/workflow_with_details_all_of_bank_model_spec.rb +2 -2
  262. data/spec/models/workflow_with_details_bank_model_spec.rb +2 -2
  263. data/spec/models/workflows_list_bank_model_spec.rb +2 -2
  264. data/spec/spec_helper.rb +2 -2
  265. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/byebug-11.1.3/gem_make.out +5 -5
  266. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/ffi-1.16.3/gem_make.out +5 -5
  267. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/jaro_winkler-1.5.6/gem_make.out +5 -5
  268. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/psych-5.1.2/gem_make.out +5 -5
  269. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/racc-1.7.3/gem_make.out +5 -5
  270. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/stringio-3.1.0/gem_make.out +5 -5
  271. metadata +34 -2
@@ -0,0 +1,243 @@
1
+ =begin
2
+ #Cybrid Bank API
3
+
4
+ ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get 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
+
6
+ The version of the OpenAPI document: v0.114.0
7
+ Contact: support@cybrid.app
8
+ Generated by: https://openapi-generator.tech
9
+ OpenAPI Generator version: 6.0.0
10
+
11
+ =end
12
+
13
+ require 'cgi'
14
+
15
+ module CybridApiBank
16
+ class InvoicesBankApi
17
+ attr_accessor :api_client
18
+
19
+ def initialize(api_client = ApiClient.default)
20
+ @api_client = api_client
21
+ end
22
+ # Create Invoice
23
+ # Creates a invoice. ## State | State | Description | |-------|-------------| | storing | The Platform is storing the invoice details in our private store | | unpaid | The invoice is unpaid. Payment instructions can be generated for an invoice in this state | | cancelling | The invocie is in the process of being cancelled | | cancelled | The invoice has been cancelled | | settling | The invoice has been paid and the funds associated with this invoice are in the process of being settled | | paid | The invoice has been paid and the funds associated with this invoice have been settled | Required scope: **invoices:execute**
24
+ # @param post_invoice_bank_model [PostInvoiceBankModel]
25
+ # @param [Hash] opts the optional parameters
26
+ # @return [InvoiceBankModel]
27
+ def create_invoice(post_invoice_bank_model, opts = {})
28
+ data, _status_code, _headers = create_invoice_with_http_info(post_invoice_bank_model, opts)
29
+ data
30
+ end
31
+
32
+ # Create Invoice
33
+ # Creates a invoice. ## State | State | Description | |-------|-------------| | storing | The Platform is storing the invoice details in our private store | | unpaid | The invoice is unpaid. Payment instructions can be generated for an invoice in this state | | cancelling | The invocie is in the process of being cancelled | | cancelled | The invoice has been cancelled | | settling | The invoice has been paid and the funds associated with this invoice are in the process of being settled | | paid | The invoice has been paid and the funds associated with this invoice have been settled | Required scope: **invoices:execute**
34
+ # @param post_invoice_bank_model [PostInvoiceBankModel]
35
+ # @param [Hash] opts the optional parameters
36
+ # @return [Array<(InvoiceBankModel, Integer, Hash)>] InvoiceBankModel data, response status code and response headers
37
+ def create_invoice_with_http_info(post_invoice_bank_model, opts = {})
38
+ if @api_client.config.debugging
39
+ @api_client.config.logger.debug 'Calling API: InvoicesBankApi.create_invoice ...'
40
+ end
41
+ # verify the required parameter 'post_invoice_bank_model' is set
42
+ if @api_client.config.client_side_validation && post_invoice_bank_model.nil?
43
+ fail ArgumentError, "Missing the required parameter 'post_invoice_bank_model' when calling InvoicesBankApi.create_invoice"
44
+ end
45
+ # resource path
46
+ local_var_path = '/api/invoices'
47
+
48
+ # query parameters
49
+ query_params = opts[:query_params] || {}
50
+
51
+ # header parameters
52
+ header_params = opts[:header_params] || {}
53
+ # HTTP header 'Accept' (if needed)
54
+ header_params['Accept'] = @api_client.select_header_accept(['application/json'])
55
+ # HTTP header 'Content-Type'
56
+ content_type = @api_client.select_header_content_type(['application/json'])
57
+ if !content_type.nil?
58
+ header_params['Content-Type'] = content_type
59
+ end
60
+
61
+ # form parameters
62
+ form_params = opts[:form_params] || {}
63
+
64
+ # http body (model)
65
+ post_body = opts[:debug_body] || @api_client.object_to_http_body(post_invoice_bank_model)
66
+
67
+ # return_type
68
+ return_type = opts[:debug_return_type] || 'InvoiceBankModel'
69
+
70
+ # auth_names
71
+ auth_names = opts[:debug_auth_names] || ['BearerAuth', 'oauth2']
72
+
73
+ new_options = opts.merge(
74
+ :operation => :"InvoicesBankApi.create_invoice",
75
+ :header_params => header_params,
76
+ :query_params => query_params,
77
+ :form_params => form_params,
78
+ :body => post_body,
79
+ :auth_names => auth_names,
80
+ :return_type => return_type
81
+ )
82
+
83
+ data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
84
+ if @api_client.config.debugging
85
+ @api_client.config.logger.debug "API called: InvoicesBankApi#create_invoice\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
86
+ end
87
+ return data, status_code, headers
88
+ end
89
+
90
+ # Get Invoice
91
+ # Retrieves a invoice. Required scope: **invoices:read**
92
+ # @param invoice_guid [String] Identifier for the payment instruction.
93
+ # @param [Hash] opts the optional parameters
94
+ # @return [InvoiceBankModel]
95
+ def get_invoice(invoice_guid, opts = {})
96
+ data, _status_code, _headers = get_invoice_with_http_info(invoice_guid, opts)
97
+ data
98
+ end
99
+
100
+ # Get Invoice
101
+ # Retrieves a invoice. Required scope: **invoices:read**
102
+ # @param invoice_guid [String] Identifier for the payment instruction.
103
+ # @param [Hash] opts the optional parameters
104
+ # @return [Array<(InvoiceBankModel, Integer, Hash)>] InvoiceBankModel data, response status code and response headers
105
+ def get_invoice_with_http_info(invoice_guid, opts = {})
106
+ if @api_client.config.debugging
107
+ @api_client.config.logger.debug 'Calling API: InvoicesBankApi.get_invoice ...'
108
+ end
109
+ # verify the required parameter 'invoice_guid' is set
110
+ if @api_client.config.client_side_validation && invoice_guid.nil?
111
+ fail ArgumentError, "Missing the required parameter 'invoice_guid' when calling InvoicesBankApi.get_invoice"
112
+ end
113
+ # resource path
114
+ local_var_path = '/api/invoices/{invoice_guid}'.sub('{' + 'invoice_guid' + '}', CGI.escape(invoice_guid.to_s))
115
+
116
+ # query parameters
117
+ query_params = opts[:query_params] || {}
118
+
119
+ # header parameters
120
+ header_params = opts[:header_params] || {}
121
+ # HTTP header 'Accept' (if needed)
122
+ header_params['Accept'] = @api_client.select_header_accept(['application/json'])
123
+
124
+ # form parameters
125
+ form_params = opts[:form_params] || {}
126
+
127
+ # http body (model)
128
+ post_body = opts[:debug_body]
129
+
130
+ # return_type
131
+ return_type = opts[:debug_return_type] || 'InvoiceBankModel'
132
+
133
+ # auth_names
134
+ auth_names = opts[:debug_auth_names] || ['BearerAuth', 'oauth2']
135
+
136
+ new_options = opts.merge(
137
+ :operation => :"InvoicesBankApi.get_invoice",
138
+ :header_params => header_params,
139
+ :query_params => query_params,
140
+ :form_params => form_params,
141
+ :body => post_body,
142
+ :auth_names => auth_names,
143
+ :return_type => return_type
144
+ )
145
+
146
+ data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options)
147
+ if @api_client.config.debugging
148
+ @api_client.config.logger.debug "API called: InvoicesBankApi#get_invoice\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
149
+ end
150
+ return data, status_code, headers
151
+ end
152
+
153
+ # List Invoices
154
+ # Retrieves a list of invoices. Required scope: **invoices:read**
155
+ # @param [Hash] opts the optional parameters
156
+ # @option opts [Integer] :page The page index to retrieve.
157
+ # @option opts [Integer] :per_page The number of entities per page to return.
158
+ # @option opts [String] :guid Comma separated guids to list invoices for.
159
+ # @option opts [String] :bank_guid Comma separated bank_guids to list invoices for.
160
+ # @option opts [String] :customer_guid Comma separated customer_guids to list invoices for.
161
+ # @option opts [String] :account_guid Comma separated account_guids to list invoices for.
162
+ # @option opts [String] :label Comma separated labels to list invoices for.
163
+ # @return [InvoiceListBankModel]
164
+ def list_invoices(opts = {})
165
+ data, _status_code, _headers = list_invoices_with_http_info(opts)
166
+ data
167
+ end
168
+
169
+ # List Invoices
170
+ # Retrieves a list of invoices. Required scope: **invoices:read**
171
+ # @param [Hash] opts the optional parameters
172
+ # @option opts [Integer] :page The page index to retrieve.
173
+ # @option opts [Integer] :per_page The number of entities per page to return.
174
+ # @option opts [String] :guid Comma separated guids to list invoices for.
175
+ # @option opts [String] :bank_guid Comma separated bank_guids to list invoices for.
176
+ # @option opts [String] :customer_guid Comma separated customer_guids to list invoices for.
177
+ # @option opts [String] :account_guid Comma separated account_guids to list invoices for.
178
+ # @option opts [String] :label Comma separated labels to list invoices for.
179
+ # @return [Array<(InvoiceListBankModel, Integer, Hash)>] InvoiceListBankModel data, response status code and response headers
180
+ def list_invoices_with_http_info(opts = {})
181
+ if @api_client.config.debugging
182
+ @api_client.config.logger.debug 'Calling API: InvoicesBankApi.list_invoices ...'
183
+ end
184
+ if @api_client.config.client_side_validation && !opts[:'page'].nil? && opts[:'page'] < 0
185
+ fail ArgumentError, 'invalid value for "opts[:"page"]" when calling InvoicesBankApi.list_invoices, must be greater than or equal to 0.'
186
+ end
187
+
188
+ if @api_client.config.client_side_validation && !opts[:'per_page'].nil? && opts[:'per_page'] > 100
189
+ fail ArgumentError, 'invalid value for "opts[:"per_page"]" when calling InvoicesBankApi.list_invoices, must be smaller than or equal to 100.'
190
+ end
191
+
192
+ if @api_client.config.client_side_validation && !opts[:'per_page'].nil? && opts[:'per_page'] < 1
193
+ fail ArgumentError, 'invalid value for "opts[:"per_page"]" when calling InvoicesBankApi.list_invoices, must be greater than or equal to 1.'
194
+ end
195
+
196
+ # resource path
197
+ local_var_path = '/api/invoices'
198
+
199
+ # query parameters
200
+ query_params = opts[:query_params] || {}
201
+ query_params[:'page'] = opts[:'page'] if !opts[:'page'].nil?
202
+ query_params[:'per_page'] = opts[:'per_page'] if !opts[:'per_page'].nil?
203
+ query_params[:'guid'] = opts[:'guid'] if !opts[:'guid'].nil?
204
+ query_params[:'bank_guid'] = opts[:'bank_guid'] if !opts[:'bank_guid'].nil?
205
+ query_params[:'customer_guid'] = opts[:'customer_guid'] if !opts[:'customer_guid'].nil?
206
+ query_params[:'account_guid'] = opts[:'account_guid'] if !opts[:'account_guid'].nil?
207
+ query_params[:'label'] = opts[:'label'] if !opts[:'label'].nil?
208
+
209
+ # header parameters
210
+ header_params = opts[:header_params] || {}
211
+ # HTTP header 'Accept' (if needed)
212
+ header_params['Accept'] = @api_client.select_header_accept(['application/json'])
213
+
214
+ # form parameters
215
+ form_params = opts[:form_params] || {}
216
+
217
+ # http body (model)
218
+ post_body = opts[:debug_body]
219
+
220
+ # return_type
221
+ return_type = opts[:debug_return_type] || 'InvoiceListBankModel'
222
+
223
+ # auth_names
224
+ auth_names = opts[:debug_auth_names] || ['BearerAuth', 'oauth2']
225
+
226
+ new_options = opts.merge(
227
+ :operation => :"InvoicesBankApi.list_invoices",
228
+ :header_params => header_params,
229
+ :query_params => query_params,
230
+ :form_params => form_params,
231
+ :body => post_body,
232
+ :auth_names => auth_names,
233
+ :return_type => return_type
234
+ )
235
+
236
+ data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options)
237
+ if @api_client.config.debugging
238
+ @api_client.config.logger.debug "API called: InvoicesBankApi#list_invoices\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
239
+ end
240
+ return data, status_code, headers
241
+ end
242
+ end
243
+ end
@@ -0,0 +1,240 @@
1
+ =begin
2
+ #Cybrid Bank API
3
+
4
+ ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get 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
+
6
+ The version of the OpenAPI document: v0.114.0
7
+ Contact: support@cybrid.app
8
+ Generated by: https://openapi-generator.tech
9
+ OpenAPI Generator version: 6.0.0
10
+
11
+ =end
12
+
13
+ require 'cgi'
14
+
15
+ module CybridApiBank
16
+ class PaymentInstructionsBankApi
17
+ attr_accessor :api_client
18
+
19
+ def initialize(api_client = ApiClient.default)
20
+ @api_client = api_client
21
+ end
22
+ # Create Payment Instruction
23
+ # Creates a payment instruction. ## State | State | Description | |-------|-------------| | storing | The Platform is storing the payment instruction details in our private store | | created | The Platform has created the payment instruction | | expired | The PaymentInstruction is no longer valid | Required scope: **invoices:write**
24
+ # @param post_payment_instruction_bank_model [PostPaymentInstructionBankModel]
25
+ # @param [Hash] opts the optional parameters
26
+ # @return [PaymentInstructionBankModel]
27
+ def create_payment_instruction(post_payment_instruction_bank_model, opts = {})
28
+ data, _status_code, _headers = create_payment_instruction_with_http_info(post_payment_instruction_bank_model, opts)
29
+ data
30
+ end
31
+
32
+ # Create Payment Instruction
33
+ # Creates a payment instruction. ## State | State | Description | |-------|-------------| | storing | The Platform is storing the payment instruction details in our private store | | created | The Platform has created the payment instruction | | expired | The PaymentInstruction is no longer valid | Required scope: **invoices:write**
34
+ # @param post_payment_instruction_bank_model [PostPaymentInstructionBankModel]
35
+ # @param [Hash] opts the optional parameters
36
+ # @return [Array<(PaymentInstructionBankModel, Integer, Hash)>] PaymentInstructionBankModel data, response status code and response headers
37
+ def create_payment_instruction_with_http_info(post_payment_instruction_bank_model, opts = {})
38
+ if @api_client.config.debugging
39
+ @api_client.config.logger.debug 'Calling API: PaymentInstructionsBankApi.create_payment_instruction ...'
40
+ end
41
+ # verify the required parameter 'post_payment_instruction_bank_model' is set
42
+ if @api_client.config.client_side_validation && post_payment_instruction_bank_model.nil?
43
+ fail ArgumentError, "Missing the required parameter 'post_payment_instruction_bank_model' when calling PaymentInstructionsBankApi.create_payment_instruction"
44
+ end
45
+ # resource path
46
+ local_var_path = '/api/payment_instructions'
47
+
48
+ # query parameters
49
+ query_params = opts[:query_params] || {}
50
+
51
+ # header parameters
52
+ header_params = opts[:header_params] || {}
53
+ # HTTP header 'Accept' (if needed)
54
+ header_params['Accept'] = @api_client.select_header_accept(['application/json'])
55
+ # HTTP header 'Content-Type'
56
+ content_type = @api_client.select_header_content_type(['application/json'])
57
+ if !content_type.nil?
58
+ header_params['Content-Type'] = content_type
59
+ end
60
+
61
+ # form parameters
62
+ form_params = opts[:form_params] || {}
63
+
64
+ # http body (model)
65
+ post_body = opts[:debug_body] || @api_client.object_to_http_body(post_payment_instruction_bank_model)
66
+
67
+ # return_type
68
+ return_type = opts[:debug_return_type] || 'PaymentInstructionBankModel'
69
+
70
+ # auth_names
71
+ auth_names = opts[:debug_auth_names] || ['BearerAuth', 'oauth2']
72
+
73
+ new_options = opts.merge(
74
+ :operation => :"PaymentInstructionsBankApi.create_payment_instruction",
75
+ :header_params => header_params,
76
+ :query_params => query_params,
77
+ :form_params => form_params,
78
+ :body => post_body,
79
+ :auth_names => auth_names,
80
+ :return_type => return_type
81
+ )
82
+
83
+ data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
84
+ if @api_client.config.debugging
85
+ @api_client.config.logger.debug "API called: PaymentInstructionsBankApi#create_payment_instruction\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
86
+ end
87
+ return data, status_code, headers
88
+ end
89
+
90
+ # Get Payment Instruction
91
+ # Retrieves a payment_instruction. Required scope: **invoices:read**
92
+ # @param payment_instruction_guid [String] Identifier for the payment instruction.
93
+ # @param [Hash] opts the optional parameters
94
+ # @return [PaymentInstructionBankModel]
95
+ def get_payment_instruction(payment_instruction_guid, opts = {})
96
+ data, _status_code, _headers = get_payment_instruction_with_http_info(payment_instruction_guid, opts)
97
+ data
98
+ end
99
+
100
+ # Get Payment Instruction
101
+ # Retrieves a payment_instruction. Required scope: **invoices:read**
102
+ # @param payment_instruction_guid [String] Identifier for the payment instruction.
103
+ # @param [Hash] opts the optional parameters
104
+ # @return [Array<(PaymentInstructionBankModel, Integer, Hash)>] PaymentInstructionBankModel data, response status code and response headers
105
+ def get_payment_instruction_with_http_info(payment_instruction_guid, opts = {})
106
+ if @api_client.config.debugging
107
+ @api_client.config.logger.debug 'Calling API: PaymentInstructionsBankApi.get_payment_instruction ...'
108
+ end
109
+ # verify the required parameter 'payment_instruction_guid' is set
110
+ if @api_client.config.client_side_validation && payment_instruction_guid.nil?
111
+ fail ArgumentError, "Missing the required parameter 'payment_instruction_guid' when calling PaymentInstructionsBankApi.get_payment_instruction"
112
+ end
113
+ # resource path
114
+ local_var_path = '/api/payment_instructions/{payment_instruction_guid}'.sub('{' + 'payment_instruction_guid' + '}', CGI.escape(payment_instruction_guid.to_s))
115
+
116
+ # query parameters
117
+ query_params = opts[:query_params] || {}
118
+
119
+ # header parameters
120
+ header_params = opts[:header_params] || {}
121
+ # HTTP header 'Accept' (if needed)
122
+ header_params['Accept'] = @api_client.select_header_accept(['application/json'])
123
+
124
+ # form parameters
125
+ form_params = opts[:form_params] || {}
126
+
127
+ # http body (model)
128
+ post_body = opts[:debug_body]
129
+
130
+ # return_type
131
+ return_type = opts[:debug_return_type] || 'PaymentInstructionBankModel'
132
+
133
+ # auth_names
134
+ auth_names = opts[:debug_auth_names] || ['BearerAuth', 'oauth2']
135
+
136
+ new_options = opts.merge(
137
+ :operation => :"PaymentInstructionsBankApi.get_payment_instruction",
138
+ :header_params => header_params,
139
+ :query_params => query_params,
140
+ :form_params => form_params,
141
+ :body => post_body,
142
+ :auth_names => auth_names,
143
+ :return_type => return_type
144
+ )
145
+
146
+ data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options)
147
+ if @api_client.config.debugging
148
+ @api_client.config.logger.debug "API called: PaymentInstructionsBankApi#get_payment_instruction\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
149
+ end
150
+ return data, status_code, headers
151
+ end
152
+
153
+ # List Payment Instructions
154
+ # Retrieves a list of payment instructions. Required scope: **invoices:read**
155
+ # @param [Hash] opts the optional parameters
156
+ # @option opts [Integer] :page The page index to retrieve.
157
+ # @option opts [Integer] :per_page The number of entities per page to return.
158
+ # @option opts [String] :guid Comma separated guids to list payment instructions for.
159
+ # @option opts [String] :bank_guid Comma separated bank_guids to list payment instructions for.
160
+ # @option opts [String] :customer_guid Comma separated customer_guids to list payment instructions for.
161
+ # @option opts [String] :invoice_guid Comma separated invoice_guids to list payment instructions for.
162
+ # @return [PaymentInstructionListBankModel]
163
+ def list_payment_instructions(opts = {})
164
+ data, _status_code, _headers = list_payment_instructions_with_http_info(opts)
165
+ data
166
+ end
167
+
168
+ # List Payment Instructions
169
+ # Retrieves a list of payment instructions. Required scope: **invoices:read**
170
+ # @param [Hash] opts the optional parameters
171
+ # @option opts [Integer] :page The page index to retrieve.
172
+ # @option opts [Integer] :per_page The number of entities per page to return.
173
+ # @option opts [String] :guid Comma separated guids to list payment instructions for.
174
+ # @option opts [String] :bank_guid Comma separated bank_guids to list payment instructions for.
175
+ # @option opts [String] :customer_guid Comma separated customer_guids to list payment instructions for.
176
+ # @option opts [String] :invoice_guid Comma separated invoice_guids to list payment instructions for.
177
+ # @return [Array<(PaymentInstructionListBankModel, Integer, Hash)>] PaymentInstructionListBankModel data, response status code and response headers
178
+ def list_payment_instructions_with_http_info(opts = {})
179
+ if @api_client.config.debugging
180
+ @api_client.config.logger.debug 'Calling API: PaymentInstructionsBankApi.list_payment_instructions ...'
181
+ end
182
+ if @api_client.config.client_side_validation && !opts[:'page'].nil? && opts[:'page'] < 0
183
+ fail ArgumentError, 'invalid value for "opts[:"page"]" when calling PaymentInstructionsBankApi.list_payment_instructions, must be greater than or equal to 0.'
184
+ end
185
+
186
+ if @api_client.config.client_side_validation && !opts[:'per_page'].nil? && opts[:'per_page'] > 100
187
+ fail ArgumentError, 'invalid value for "opts[:"per_page"]" when calling PaymentInstructionsBankApi.list_payment_instructions, must be smaller than or equal to 100.'
188
+ end
189
+
190
+ if @api_client.config.client_side_validation && !opts[:'per_page'].nil? && opts[:'per_page'] < 1
191
+ fail ArgumentError, 'invalid value for "opts[:"per_page"]" when calling PaymentInstructionsBankApi.list_payment_instructions, must be greater than or equal to 1.'
192
+ end
193
+
194
+ # resource path
195
+ local_var_path = '/api/payment_instructions'
196
+
197
+ # query parameters
198
+ query_params = opts[:query_params] || {}
199
+ query_params[:'page'] = opts[:'page'] if !opts[:'page'].nil?
200
+ query_params[:'per_page'] = opts[:'per_page'] if !opts[:'per_page'].nil?
201
+ query_params[:'guid'] = opts[:'guid'] if !opts[:'guid'].nil?
202
+ query_params[:'bank_guid'] = opts[:'bank_guid'] if !opts[:'bank_guid'].nil?
203
+ query_params[:'customer_guid'] = opts[:'customer_guid'] if !opts[:'customer_guid'].nil?
204
+ query_params[:'invoice_guid'] = opts[:'invoice_guid'] if !opts[:'invoice_guid'].nil?
205
+
206
+ # header parameters
207
+ header_params = opts[:header_params] || {}
208
+ # HTTP header 'Accept' (if needed)
209
+ header_params['Accept'] = @api_client.select_header_accept(['application/json'])
210
+
211
+ # form parameters
212
+ form_params = opts[:form_params] || {}
213
+
214
+ # http body (model)
215
+ post_body = opts[:debug_body]
216
+
217
+ # return_type
218
+ return_type = opts[:debug_return_type] || 'PaymentInstructionListBankModel'
219
+
220
+ # auth_names
221
+ auth_names = opts[:debug_auth_names] || ['BearerAuth', 'oauth2']
222
+
223
+ new_options = opts.merge(
224
+ :operation => :"PaymentInstructionsBankApi.list_payment_instructions",
225
+ :header_params => header_params,
226
+ :query_params => query_params,
227
+ :form_params => form_params,
228
+ :body => post_body,
229
+ :auth_names => auth_names,
230
+ :return_type => return_type
231
+ )
232
+
233
+ data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options)
234
+ if @api_client.config.debugging
235
+ @api_client.config.logger.debug "API called: PaymentInstructionsBankApi#list_payment_instructions\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
236
+ end
237
+ return data, status_code, headers
238
+ end
239
+ end
240
+ end
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #Cybrid Bank API
3
3
 
4
- ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
4
+ ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get 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.113.154
6
+ The version of the OpenAPI document: v0.114.0
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0