cybrid_api_bank_ruby 0.56.10 → 0.56.11

Sign up to get free protection for your applications and to get access to all the features.
Files changed (245) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +3 -3
  3. data/README.md +5 -5
  4. data/cybrid_api_bank_ruby.gemspec +1 -1
  5. data/lib/cybrid_api_bank_ruby/api/accounts_bank_api.rb +1 -1
  6. data/lib/cybrid_api_bank_ruby/api/assets_bank_api.rb +1 -1
  7. data/lib/cybrid_api_bank_ruby/api/banks_bank_api.rb +1 -1
  8. data/lib/cybrid_api_bank_ruby/api/customers_bank_api.rb +1 -1
  9. data/lib/cybrid_api_bank_ruby/api/external_bank_accounts_bank_api.rb +1 -1
  10. data/lib/cybrid_api_bank_ruby/api/fee_configurations_bank_api.rb +1 -1
  11. data/lib/cybrid_api_bank_ruby/api/identity_records_bank_api.rb +1 -1
  12. data/lib/cybrid_api_bank_ruby/api/identity_verifications_bank_api.rb +1 -1
  13. data/lib/cybrid_api_bank_ruby/api/prices_bank_api.rb +1 -1
  14. data/lib/cybrid_api_bank_ruby/api/quotes_bank_api.rb +1 -1
  15. data/lib/cybrid_api_bank_ruby/api/rewards_bank_api.rb +1 -1
  16. data/lib/cybrid_api_bank_ruby/api/symbols_bank_api.rb +1 -1
  17. data/lib/cybrid_api_bank_ruby/api/trades_bank_api.rb +1 -1
  18. data/lib/cybrid_api_bank_ruby/api/transfers_bank_api.rb +1 -1
  19. data/lib/cybrid_api_bank_ruby/api/verification_keys_bank_api.rb +1 -1
  20. data/lib/cybrid_api_bank_ruby/api/workflows_bank_api.rb +1 -1
  21. data/lib/cybrid_api_bank_ruby/api_client.rb +1 -1
  22. data/lib/cybrid_api_bank_ruby/api_error.rb +1 -1
  23. data/lib/cybrid_api_bank_ruby/configuration.rb +1 -1
  24. data/lib/cybrid_api_bank_ruby/models/account_bank_model.rb +1 -1
  25. data/lib/cybrid_api_bank_ruby/models/account_list_bank_model.rb +1 -1
  26. data/lib/cybrid_api_bank_ruby/models/asset_bank_model.rb +1 -1
  27. data/lib/cybrid_api_bank_ruby/models/asset_list_bank_model.rb +1 -1
  28. data/lib/cybrid_api_bank_ruby/models/attestation_details_bank_model.rb +1 -1
  29. data/lib/cybrid_api_bank_ruby/models/bank_bank_model.rb +1 -1
  30. data/lib/cybrid_api_bank_ruby/models/bank_list_bank_model.rb +1 -1
  31. data/lib/cybrid_api_bank_ruby/models/customer_bank_model.rb +1 -1
  32. data/lib/cybrid_api_bank_ruby/models/customer_list_bank_model.rb +1 -1
  33. data/lib/cybrid_api_bank_ruby/models/error_response_bank_model.rb +1 -1
  34. data/lib/cybrid_api_bank_ruby/models/external_bank_account_bank_model.rb +1 -1
  35. data/lib/cybrid_api_bank_ruby/models/external_bank_account_list_bank_model.rb +1 -1
  36. data/lib/cybrid_api_bank_ruby/models/fee_bank_model.rb +1 -1
  37. data/lib/cybrid_api_bank_ruby/models/fee_configuration_bank_model.rb +1 -1
  38. data/lib/cybrid_api_bank_ruby/models/fee_configuration_list_bank_model.rb +1 -1
  39. data/lib/cybrid_api_bank_ruby/models/identity_record_bank_model.rb +1 -1
  40. data/lib/cybrid_api_bank_ruby/models/identity_record_list_bank_model.rb +1 -1
  41. data/lib/cybrid_api_bank_ruby/models/identity_verification_bank_model.rb +1 -1
  42. data/lib/cybrid_api_bank_ruby/models/identity_verification_list_bank_model.rb +1 -1
  43. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_all_of_bank_model.rb +1 -1
  44. data/lib/cybrid_api_bank_ruby/models/identity_verification_with_details_bank_model.rb +1 -1
  45. data/lib/cybrid_api_bank_ruby/models/patch_bank_bank_model.rb +1 -1
  46. data/lib/cybrid_api_bank_ruby/models/post_account_bank_model.rb +1 -1
  47. data/lib/cybrid_api_bank_ruby/models/post_bank_bank_model.rb +1 -1
  48. data/lib/cybrid_api_bank_ruby/models/post_customer_bank_model.rb +1 -1
  49. data/lib/cybrid_api_bank_ruby/models/post_external_bank_account_bank_model.rb +1 -1
  50. data/lib/cybrid_api_bank_ruby/models/post_fee_bank_model.rb +1 -1
  51. data/lib/cybrid_api_bank_ruby/models/post_fee_configuration_bank_model.rb +1 -1
  52. data/lib/cybrid_api_bank_ruby/models/post_identity_record_attestation_details_bank_model.rb +1 -1
  53. data/lib/cybrid_api_bank_ruby/models/post_identity_record_bank_model.rb +1 -1
  54. data/lib/cybrid_api_bank_ruby/models/post_identity_verification_bank_model.rb +1 -1
  55. data/lib/cybrid_api_bank_ruby/models/post_quote_bank_model.rb +1 -1
  56. data/lib/cybrid_api_bank_ruby/models/post_reward_bank_model.rb +1 -1
  57. data/lib/cybrid_api_bank_ruby/models/post_trade_bank_model.rb +1 -1
  58. data/lib/cybrid_api_bank_ruby/models/post_transfer_bank_model.rb +1 -1
  59. data/lib/cybrid_api_bank_ruby/models/post_verification_key_bank_model.rb +1 -1
  60. data/lib/cybrid_api_bank_ruby/models/post_workflow_bank_model.rb +1 -1
  61. data/lib/cybrid_api_bank_ruby/models/quote_bank_model.rb +1 -1
  62. data/lib/cybrid_api_bank_ruby/models/quote_list_bank_model.rb +1 -1
  63. data/lib/cybrid_api_bank_ruby/models/reward_bank_model.rb +1 -1
  64. data/lib/cybrid_api_bank_ruby/models/reward_list_bank_model.rb +1 -1
  65. data/lib/cybrid_api_bank_ruby/models/symbol_price_bank_model.rb +1 -1
  66. data/lib/cybrid_api_bank_ruby/models/trade_bank_model.rb +1 -1
  67. data/lib/cybrid_api_bank_ruby/models/trade_list_bank_model.rb +1 -1
  68. data/lib/cybrid_api_bank_ruby/models/transfer_bank_model.rb +1 -1
  69. data/lib/cybrid_api_bank_ruby/models/transfer_list_bank_model.rb +1 -1
  70. data/lib/cybrid_api_bank_ruby/models/verification_key_bank_model.rb +1 -1
  71. data/lib/cybrid_api_bank_ruby/models/verification_key_list_bank_model.rb +1 -1
  72. data/lib/cybrid_api_bank_ruby/models/workflow_bank_model.rb +1 -1
  73. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_all_of_bank_model.rb +1 -1
  74. data/lib/cybrid_api_bank_ruby/models/workflow_with_details_bank_model.rb +1 -1
  75. data/lib/cybrid_api_bank_ruby/models/workflows_list_bank_model.rb +1 -1
  76. data/lib/cybrid_api_bank_ruby/version.rb +2 -2
  77. data/lib/cybrid_api_bank_ruby.rb +1 -1
  78. data/spec/api/accounts_bank_api_spec.rb +1 -1
  79. data/spec/api/assets_bank_api_spec.rb +1 -1
  80. data/spec/api/banks_bank_api_spec.rb +1 -1
  81. data/spec/api/customers_bank_api_spec.rb +1 -1
  82. data/spec/api/external_bank_accounts_bank_api_spec.rb +1 -1
  83. data/spec/api/fee_configurations_bank_api_spec.rb +1 -1
  84. data/spec/api/identity_records_bank_api_spec.rb +1 -1
  85. data/spec/api/identity_verifications_bank_api_spec.rb +1 -1
  86. data/spec/api/prices_bank_api_spec.rb +1 -1
  87. data/spec/api/quotes_bank_api_spec.rb +1 -1
  88. data/spec/api/rewards_bank_api_spec.rb +1 -1
  89. data/spec/api/symbols_bank_api_spec.rb +1 -1
  90. data/spec/api/trades_bank_api_spec.rb +1 -1
  91. data/spec/api/transfers_bank_api_spec.rb +1 -1
  92. data/spec/api/verification_keys_bank_api_spec.rb +1 -1
  93. data/spec/api/workflows_bank_api_spec.rb +1 -1
  94. data/spec/api_client_spec.rb +1 -1
  95. data/spec/configuration_spec.rb +1 -1
  96. data/spec/models/account_bank_model_spec.rb +1 -1
  97. data/spec/models/account_list_bank_model_spec.rb +1 -1
  98. data/spec/models/asset_bank_model_spec.rb +1 -1
  99. data/spec/models/asset_list_bank_model_spec.rb +1 -1
  100. data/spec/models/attestation_details_bank_model_spec.rb +1 -1
  101. data/spec/models/bank_bank_model_spec.rb +1 -1
  102. data/spec/models/bank_list_bank_model_spec.rb +1 -1
  103. data/spec/models/customer_bank_model_spec.rb +1 -1
  104. data/spec/models/customer_list_bank_model_spec.rb +1 -1
  105. data/spec/models/error_response_bank_model_spec.rb +1 -1
  106. data/spec/models/external_bank_account_bank_model_spec.rb +1 -1
  107. data/spec/models/external_bank_account_list_bank_model_spec.rb +1 -1
  108. data/spec/models/fee_bank_model_spec.rb +1 -1
  109. data/spec/models/fee_configuration_bank_model_spec.rb +1 -1
  110. data/spec/models/fee_configuration_list_bank_model_spec.rb +1 -1
  111. data/spec/models/identity_record_bank_model_spec.rb +1 -1
  112. data/spec/models/identity_record_list_bank_model_spec.rb +1 -1
  113. data/spec/models/identity_verification_bank_model_spec.rb +1 -1
  114. data/spec/models/identity_verification_list_bank_model_spec.rb +1 -1
  115. data/spec/models/identity_verification_with_details_all_of_bank_model_spec.rb +1 -1
  116. data/spec/models/identity_verification_with_details_bank_model_spec.rb +1 -1
  117. data/spec/models/patch_bank_bank_model_spec.rb +1 -1
  118. data/spec/models/post_account_bank_model_spec.rb +1 -1
  119. data/spec/models/post_bank_bank_model_spec.rb +1 -1
  120. data/spec/models/post_customer_bank_model_spec.rb +1 -1
  121. data/spec/models/post_external_bank_account_bank_model_spec.rb +1 -1
  122. data/spec/models/post_fee_bank_model_spec.rb +1 -1
  123. data/spec/models/post_fee_configuration_bank_model_spec.rb +1 -1
  124. data/spec/models/post_identity_record_attestation_details_bank_model_spec.rb +1 -1
  125. data/spec/models/post_identity_record_bank_model_spec.rb +1 -1
  126. data/spec/models/post_identity_verification_bank_model_spec.rb +1 -1
  127. data/spec/models/post_quote_bank_model_spec.rb +1 -1
  128. data/spec/models/post_reward_bank_model_spec.rb +1 -1
  129. data/spec/models/post_trade_bank_model_spec.rb +1 -1
  130. data/spec/models/post_transfer_bank_model_spec.rb +1 -1
  131. data/spec/models/post_verification_key_bank_model_spec.rb +1 -1
  132. data/spec/models/post_workflow_bank_model_spec.rb +1 -1
  133. data/spec/models/quote_bank_model_spec.rb +1 -1
  134. data/spec/models/quote_list_bank_model_spec.rb +1 -1
  135. data/spec/models/reward_bank_model_spec.rb +1 -1
  136. data/spec/models/reward_list_bank_model_spec.rb +1 -1
  137. data/spec/models/symbol_price_bank_model_spec.rb +1 -1
  138. data/spec/models/trade_bank_model_spec.rb +1 -1
  139. data/spec/models/trade_list_bank_model_spec.rb +1 -1
  140. data/spec/models/transfer_bank_model_spec.rb +1 -1
  141. data/spec/models/transfer_list_bank_model_spec.rb +1 -1
  142. data/spec/models/verification_key_bank_model_spec.rb +1 -1
  143. data/spec/models/verification_key_list_bank_model_spec.rb +1 -1
  144. data/spec/models/workflow_bank_model_spec.rb +1 -1
  145. data/spec/models/workflow_with_details_all_of_bank_model_spec.rb +1 -1
  146. data/spec/models/workflow_with_details_bank_model_spec.rb +1 -1
  147. data/spec/models/workflows_list_bank_model_spec.rb +1 -1
  148. data/spec/spec_helper.rb +1 -1
  149. data/vendor/bundle/ruby/3.1.0/cache/psych-5.0.1.gem +0 -0
  150. data/vendor/bundle/ruby/3.1.0/cache/stringio-3.0.3.gem +0 -0
  151. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/byebug-11.1.3/gem_make.out +4 -4
  152. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/ffi-1.15.5/gem_make.out +4 -4
  153. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/jaro_winkler-1.5.4/gem_make.out +4 -4
  154. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/{psych-5.0.0 → psych-5.0.1}/gem.build_complete +0 -0
  155. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/{psych-5.0.0 → psych-5.0.1}/gem_make.out +14 -14
  156. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/{psych-5.0.0 → psych-5.0.1}/mkmf.log +0 -0
  157. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/{psych-5.0.0 → psych-5.0.1}/psych.so +0 -0
  158. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/{stringio-3.0.2 → stringio-3.0.3}/gem.build_complete +0 -0
  159. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/{stringio-3.0.2 → stringio-3.0.3}/gem_make.out +14 -14
  160. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/{stringio-3.0.2 → stringio-3.0.3}/mkmf.log +0 -0
  161. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/stringio-3.0.3/stringio.so +0 -0
  162. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/.gitignore +0 -0
  163. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/Gemfile +0 -0
  164. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/LICENSE +0 -0
  165. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/Mavenfile +0 -0
  166. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/README.md +6 -5
  167. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/Rakefile +0 -0
  168. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/bin/console +0 -0
  169. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/bin/setup +0 -0
  170. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/.sitearchdir.time +0 -0
  171. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/Makefile +0 -0
  172. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/depend +0 -0
  173. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/extconf.rb +0 -0
  174. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych.c +0 -0
  175. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych.h +0 -0
  176. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych.o +0 -0
  177. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych.so +0 -0
  178. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_emitter.c +0 -0
  179. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_emitter.h +0 -0
  180. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_emitter.o +0 -0
  181. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_parser.c +0 -0
  182. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_parser.h +0 -0
  183. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_parser.o +0 -0
  184. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_to_ruby.c +0 -0
  185. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_to_ruby.h +0 -0
  186. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_to_ruby.o +0 -0
  187. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_yaml_tree.c +0 -0
  188. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_yaml_tree.h +0 -0
  189. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/ext/psych/psych_yaml_tree.o +0 -0
  190. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/class_loader.rb +0 -0
  191. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/coder.rb +0 -0
  192. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/core_ext.rb +0 -0
  193. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/exception.rb +0 -0
  194. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/handler.rb +0 -0
  195. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/handlers/document_stream.rb +0 -0
  196. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/handlers/recorder.rb +0 -0
  197. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/json/ruby_events.rb +0 -0
  198. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/json/stream.rb +0 -0
  199. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/json/tree_builder.rb +0 -0
  200. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/json/yaml_events.rb +0 -0
  201. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/nodes/alias.rb +0 -0
  202. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/nodes/document.rb +0 -0
  203. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/nodes/mapping.rb +0 -0
  204. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/nodes/node.rb +0 -0
  205. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/nodes/scalar.rb +0 -0
  206. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/nodes/sequence.rb +0 -0
  207. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/nodes/stream.rb +0 -0
  208. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/nodes.rb +0 -0
  209. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/omap.rb +0 -0
  210. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/parser.rb +0 -0
  211. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/scalar_scanner.rb +0 -0
  212. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/set.rb +0 -0
  213. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/stream.rb +0 -0
  214. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/streaming.rb +0 -0
  215. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/syntax_error.rb +0 -0
  216. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/tree_builder.rb +0 -0
  217. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/versions.rb +1 -1
  218. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/visitors/depth_first.rb +0 -0
  219. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/visitors/emitter.rb +0 -0
  220. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/visitors/json_tree.rb +0 -0
  221. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/visitors/to_ruby.rb +0 -0
  222. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/visitors/visitor.rb +0 -0
  223. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/visitors/yaml_tree.rb +0 -0
  224. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/visitors.rb +0 -0
  225. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych/y.rb +0 -0
  226. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych.rb +0 -0
  227. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/lib/psych.so +0 -0
  228. data/vendor/bundle/ruby/3.1.0/gems/{psych-5.0.0 → psych-5.0.1}/psych.gemspec +0 -0
  229. data/vendor/bundle/ruby/3.1.0/gems/{stringio-3.0.2 → stringio-3.0.3}/README.md +0 -0
  230. data/vendor/bundle/ruby/3.1.0/gems/{stringio-3.0.2 → stringio-3.0.3}/ext/stringio/.sitearchdir.time +0 -0
  231. data/vendor/bundle/ruby/3.1.0/gems/{stringio-3.0.2 → stringio-3.0.3}/ext/stringio/Makefile +0 -0
  232. data/vendor/bundle/ruby/3.1.0/gems/{stringio-3.0.2 → stringio-3.0.3}/ext/stringio/extconf.rb +0 -0
  233. data/vendor/bundle/ruby/3.1.0/gems/{stringio-3.0.2 → stringio-3.0.3}/ext/stringio/stringio.c +241 -132
  234. data/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio/stringio.o +0 -0
  235. data/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio/stringio.so +0 -0
  236. data/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/lib/stringio.so +0 -0
  237. data/vendor/bundle/ruby/3.1.0/specifications/{psych-5.0.0.gemspec → psych-5.0.1.gemspec} +3 -3
  238. data/vendor/bundle/ruby/3.1.0/specifications/{stringio-3.0.2.gemspec → stringio-3.0.3.gemspec} +3 -3
  239. metadata +89 -89
  240. data/vendor/bundle/ruby/3.1.0/cache/psych-5.0.0.gem +0 -0
  241. data/vendor/bundle/ruby/3.1.0/cache/stringio-3.0.2.gem +0 -0
  242. data/vendor/bundle/ruby/3.1.0/extensions/x86_64-linux/3.1.0/stringio-3.0.2/stringio.so +0 -0
  243. data/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio/stringio.o +0 -0
  244. data/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio/stringio.so +0 -0
  245. data/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/lib/stringio.so +0 -0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.demo.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started) 2. [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading) 3. [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) (or, alternatively, [Testing with Hosted Web Demo App](https://www.cybrid.xyz/guides/testing-with-the-web-demo-crypo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), we walk you through how to use the [Cybrid Sandbox](https://id.demo.cybrid.app/) to create a test bank, generate API keys, and set banks fees. In [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [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.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.demo.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.demo.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.demo.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. ``` curl -X POST https://id.demo.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute trades:execute trades:read\" }' -H \"Content-Type: application/json\" ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, 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) | |------------------------|------------------------------------------------------------|------------------------------------|-------------------------------------------------| | Organizations | organizations:read (Organization) | organizations:write (Organization) | | | Banks | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customers | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Accounts | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Prices | prices:read (Bank, Customer) | | | | Quotes | quotes:read (Organization, Bank, Customer) | | quotes:execute (Bank, Customer) | | Trades | trades:read (Organization, Bank, Customer) | | trades:execute (Bank, Customer) | | Rewards | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | External bank accounts | external_bank_accounts:read (Organization, Bank, Customer) | | external_bank_accounts:execute (Bank, Customer) | | Workflows | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Transfers | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.demo.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.demo.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.demo.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | VerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | Bank | Banks | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | FeeConfiguration | /api/fee_configurations | Create and list bank fees (spread or fixed) | | Bank | Customers | /api/customers | Create and list customers | | Bank | IdentityRecord | /api/identity_records | Create and list identity records, which are attached to customers for KYC | | Bank | Accounts | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Symbols | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Prices | /api/prices | Get the current prices for assets on the platform | | Bank | Quotes | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Trades | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Rewards | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | Bank | ExternalBankAccounts | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | Workflows | /api/workflows | Create, get and list workflows | | Bank | Transfers | /api/transfers | Create, get and list transfers (e.g., funding, book) | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to 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 valid `Identity Record`. See the Identity Records section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.56.10
6
+ The version of the OpenAPI document: v0.56.11
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.demo.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started) 2. [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading) 3. [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) (or, alternatively, [Testing with Hosted Web Demo App](https://www.cybrid.xyz/guides/testing-with-the-web-demo-crypo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), we walk you through how to use the [Cybrid Sandbox](https://id.demo.cybrid.app/) to create a test bank, generate API keys, and set banks fees. In [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [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.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.demo.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.demo.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.demo.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. ``` curl -X POST https://id.demo.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute trades:execute trades:read\" }' -H \"Content-Type: application/json\" ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, 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) | |------------------------|------------------------------------------------------------|------------------------------------|-------------------------------------------------| | Organizations | organizations:read (Organization) | organizations:write (Organization) | | | Banks | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customers | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Accounts | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Prices | prices:read (Bank, Customer) | | | | Quotes | quotes:read (Organization, Bank, Customer) | | quotes:execute (Bank, Customer) | | Trades | trades:read (Organization, Bank, Customer) | | trades:execute (Bank, Customer) | | Rewards | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | External bank accounts | external_bank_accounts:read (Organization, Bank, Customer) | | external_bank_accounts:execute (Bank, Customer) | | Workflows | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Transfers | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.demo.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.demo.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.demo.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | VerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | Bank | Banks | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | FeeConfiguration | /api/fee_configurations | Create and list bank fees (spread or fixed) | | Bank | Customers | /api/customers | Create and list customers | | Bank | IdentityRecord | /api/identity_records | Create and list identity records, which are attached to customers for KYC | | Bank | Accounts | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Symbols | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Prices | /api/prices | Get the current prices for assets on the platform | | Bank | Quotes | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Trades | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Rewards | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | Bank | ExternalBankAccounts | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | Workflows | /api/workflows | Create, get and list workflows | | Bank | Transfers | /api/transfers | Create, get and list transfers (e.g., funding, book) | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to 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 valid `Identity Record`. See the Identity Records section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.56.10
6
+ The version of the OpenAPI document: v0.56.11
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.demo.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started) 2. [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading) 3. [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) (or, alternatively, [Testing with Hosted Web Demo App](https://www.cybrid.xyz/guides/testing-with-the-web-demo-crypo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), we walk you through how to use the [Cybrid Sandbox](https://id.demo.cybrid.app/) to create a test bank, generate API keys, and set banks fees. In [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [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.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.demo.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.demo.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.demo.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. ``` curl -X POST https://id.demo.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute trades:execute trades:read\" }' -H \"Content-Type: application/json\" ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, 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) | |------------------------|------------------------------------------------------------|------------------------------------|-------------------------------------------------| | Organizations | organizations:read (Organization) | organizations:write (Organization) | | | Banks | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customers | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Accounts | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Prices | prices:read (Bank, Customer) | | | | Quotes | quotes:read (Organization, Bank, Customer) | | quotes:execute (Bank, Customer) | | Trades | trades:read (Organization, Bank, Customer) | | trades:execute (Bank, Customer) | | Rewards | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | External bank accounts | external_bank_accounts:read (Organization, Bank, Customer) | | external_bank_accounts:execute (Bank, Customer) | | Workflows | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Transfers | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.demo.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.demo.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.demo.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | VerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | Bank | Banks | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | FeeConfiguration | /api/fee_configurations | Create and list bank fees (spread or fixed) | | Bank | Customers | /api/customers | Create and list customers | | Bank | IdentityRecord | /api/identity_records | Create and list identity records, which are attached to customers for KYC | | Bank | Accounts | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Symbols | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Prices | /api/prices | Get the current prices for assets on the platform | | Bank | Quotes | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Trades | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Rewards | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | Bank | ExternalBankAccounts | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | Workflows | /api/workflows | Create, get and list workflows | | Bank | Transfers | /api/transfers | Create, get and list transfers (e.g., funding, book) | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to 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 valid `Identity Record`. See the Identity Records section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.56.10
6
+ The version of the OpenAPI document: v0.56.11
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
data/spec/spec_helper.rb CHANGED
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.demo.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started) 2. [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading) 3. [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) (or, alternatively, [Testing with Hosted Web Demo App](https://www.cybrid.xyz/guides/testing-with-the-web-demo-crypo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), we walk you through how to use the [Cybrid Sandbox](https://id.demo.cybrid.app/) to create a test bank, generate API keys, and set banks fees. In [Getting Ready for Trading](https://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [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.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.demo.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.demo.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.demo.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.demo.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. ``` curl -X POST https://id.demo.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute trades:execute trades:read\" }' -H \"Content-Type: application/json\" ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, 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) | |------------------------|------------------------------------------------------------|------------------------------------|-------------------------------------------------| | Organizations | organizations:read (Organization) | organizations:write (Organization) | | | Banks | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customers | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Accounts | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Prices | prices:read (Bank, Customer) | | | | Quotes | quotes:read (Organization, Bank, Customer) | | quotes:execute (Bank, Customer) | | Trades | trades:read (Organization, Bank, Customer) | | trades:execute (Bank, Customer) | | Rewards | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | External bank accounts | external_bank_accounts:read (Organization, Bank, Customer) | | external_bank_accounts:execute (Bank, Customer) | | Workflows | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Transfers | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.demo.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.demo.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.demo.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | VerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | Bank | Banks | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | FeeConfiguration | /api/fee_configurations | Create and list bank fees (spread or fixed) | | Bank | Customers | /api/customers | Create and list customers | | Bank | IdentityRecord | /api/identity_records | Create and list identity records, which are attached to customers for KYC | | Bank | Accounts | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Symbols | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Prices | /api/prices | Get the current prices for assets on the platform | | Bank | Quotes | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Trades | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Rewards | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | Bank | ExternalBankAccounts | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | Workflows | /api/workflows | Create, get and list workflows | | Bank | Transfers | /api/transfers | Create, get and list transfers (e.g., funding, book) | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to 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 valid `Identity Record`. See the Identity Records section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.56.10
6
+ The version of the OpenAPI document: v0.56.11
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,12 +3,12 @@ current directory: /home/circleci/project/api-service-clients/api-platform-bank/
3
3
  creating Makefile
4
4
 
5
5
  current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/byebug-11.1.3/ext/byebug
6
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-fd4ex2 sitelibdir\=./.gem.20221207-3909-fd4ex2 clean
6
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-68tk4q sitelibdir\=./.gem.20221208-3903-68tk4q clean
7
7
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/byebug-11.1.3/ext/byebug'
8
8
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/byebug-11.1.3/ext/byebug'
9
9
 
10
10
  current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/byebug-11.1.3/ext/byebug
11
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-fd4ex2 sitelibdir\=./.gem.20221207-3909-fd4ex2
11
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-68tk4q sitelibdir\=./.gem.20221208-3903-68tk4q
12
12
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/byebug-11.1.3/ext/byebug'
13
13
  compiling breakpoint.c
14
14
  compiling byebug.c
@@ -39,7 +39,7 @@ linking shared-object byebug/byebug.so
39
39
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/byebug-11.1.3/ext/byebug'
40
40
 
41
41
  current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/byebug-11.1.3/ext/byebug
42
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-fd4ex2 sitelibdir\=./.gem.20221207-3909-fd4ex2 install
42
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-68tk4q sitelibdir\=./.gem.20221208-3903-68tk4q install
43
43
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/byebug-11.1.3/ext/byebug'
44
- /usr/bin/install -c -m 0755 byebug.so ./.gem.20221207-3909-fd4ex2/byebug
44
+ /usr/bin/install -c -m 0755 byebug.so ./.gem.20221208-3903-68tk4q/byebug
45
45
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/byebug-11.1.3/ext/byebug'
@@ -9,12 +9,12 @@ creating extconf.h
9
9
  creating Makefile
10
10
 
11
11
  current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/ffi-1.15.5/ext/ffi_c
12
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-2uvps5 sitelibdir\=./.gem.20221207-3909-2uvps5 clean
12
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-hzyinv sitelibdir\=./.gem.20221208-3903-hzyinv clean
13
13
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/ffi-1.15.5/ext/ffi_c'
14
14
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/ffi-1.15.5/ext/ffi_c'
15
15
 
16
16
  current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/ffi-1.15.5/ext/ffi_c
17
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-2uvps5 sitelibdir\=./.gem.20221207-3909-2uvps5
17
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-hzyinv sitelibdir\=./.gem.20221208-3903-hzyinv
18
18
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/ffi-1.15.5/ext/ffi_c'
19
19
  compiling AbstractMemory.c
20
20
  compiling ArrayType.c
@@ -43,7 +43,7 @@ linking shared-object ffi_c.so
43
43
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/ffi-1.15.5/ext/ffi_c'
44
44
 
45
45
  current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/ffi-1.15.5/ext/ffi_c
46
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-2uvps5 sitelibdir\=./.gem.20221207-3909-2uvps5 install
46
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-hzyinv sitelibdir\=./.gem.20221208-3903-hzyinv install
47
47
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/ffi-1.15.5/ext/ffi_c'
48
- /usr/bin/install -c -m 0755 ffi_c.so ./.gem.20221207-3909-2uvps5
48
+ /usr/bin/install -c -m 0755 ffi_c.so ./.gem.20221208-3903-hzyinv
49
49
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/ffi-1.15.5/ext/ffi_c'
@@ -3,12 +3,12 @@ current directory: /home/circleci/project/api-service-clients/api-platform-bank/
3
3
  creating Makefile
4
4
 
5
5
  current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
6
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-a39ky3 sitelibdir\=./.gem.20221207-3909-a39ky3 clean
6
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-qg63jc sitelibdir\=./.gem.20221208-3903-qg63jc clean
7
7
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
8
8
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
9
9
 
10
10
  current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
11
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-a39ky3 sitelibdir\=./.gem.20221207-3909-a39ky3
11
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-qg63jc sitelibdir\=./.gem.20221208-3903-qg63jc
12
12
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
13
13
  compiling adj_matrix.c
14
14
  adj_matrix.c: In function ‘adj_matrix_default’:
@@ -63,7 +63,7 @@ linking shared-object jaro_winkler/jaro_winkler_ext.so
63
63
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
64
64
 
65
65
  current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
66
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-a39ky3 sitelibdir\=./.gem.20221207-3909-a39ky3 install
66
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-qg63jc sitelibdir\=./.gem.20221208-3903-qg63jc install
67
67
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
68
- /usr/bin/install -c -m 0755 jaro_winkler_ext.so ./.gem.20221207-3909-a39ky3/jaro_winkler
68
+ /usr/bin/install -c -m 0755 jaro_winkler_ext.so ./.gem.20221208-3903-qg63jc/jaro_winkler
69
69
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
@@ -1,30 +1,30 @@
1
- current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.0/ext/psych
1
+ current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.1/ext/psych
2
2
  /usr/local/bin/ruby -I /usr/local/lib/ruby/3.1.0 extconf.rb
3
3
  checking for yaml.h... yes
4
4
  checking for yaml_get_version() in -lyaml... yes
5
5
  creating Makefile
6
6
 
7
- current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.0/ext/psych
8
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-tbpgm4 sitelibdir\=./.gem.20221207-3909-tbpgm4 clean
9
- make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.0/ext/psych'
7
+ current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.1/ext/psych
8
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-jgcf7z sitelibdir\=./.gem.20221208-3903-jgcf7z clean
9
+ make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.1/ext/psych'
10
10
  cd libyaml && make clean
11
11
  /bin/sh: 1: cd: can't cd to libyaml
12
12
  make[1]: [Makefile:282: clean-so] Error 2 (ignored)
13
- make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.0/ext/psych'
13
+ make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.1/ext/psych'
14
14
 
15
- current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.0/ext/psych
16
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-tbpgm4 sitelibdir\=./.gem.20221207-3909-tbpgm4
17
- make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.0/ext/psych'
15
+ current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.1/ext/psych
16
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-jgcf7z sitelibdir\=./.gem.20221208-3903-jgcf7z
17
+ make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.1/ext/psych'
18
18
  compiling psych.c
19
19
  compiling psych_emitter.c
20
20
  compiling psych_parser.c
21
21
  compiling psych_to_ruby.c
22
22
  compiling psych_yaml_tree.c
23
23
  linking shared-object psych.so
24
- make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.0/ext/psych'
24
+ make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.1/ext/psych'
25
25
 
26
- current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.0/ext/psych
27
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-tbpgm4 sitelibdir\=./.gem.20221207-3909-tbpgm4 install
28
- make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.0/ext/psych'
29
- /usr/bin/install -c -m 0755 psych.so ./.gem.20221207-3909-tbpgm4
30
- make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.0/ext/psych'
26
+ current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.1/ext/psych
27
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-jgcf7z sitelibdir\=./.gem.20221208-3903-jgcf7z install
28
+ make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.1/ext/psych'
29
+ /usr/bin/install -c -m 0755 psych.so ./.gem.20221208-3903-jgcf7z
30
+ make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/psych-5.0.1/ext/psych'
@@ -1,22 +1,22 @@
1
- current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio
1
+ current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio
2
2
  /usr/local/bin/ruby -I /usr/local/lib/ruby/3.1.0 extconf.rb
3
3
  checking for rb_io_extract_modeenc() in ruby/io.h... yes
4
4
  creating Makefile
5
5
 
6
- current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio
7
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-zgfxbv sitelibdir\=./.gem.20221207-3909-zgfxbv clean
8
- make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio'
9
- make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio'
6
+ current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio
7
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-swj30r sitelibdir\=./.gem.20221208-3903-swj30r clean
8
+ make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio'
9
+ make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio'
10
10
 
11
- current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio
12
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-zgfxbv sitelibdir\=./.gem.20221207-3909-zgfxbv
13
- make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio'
11
+ current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio
12
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-swj30r sitelibdir\=./.gem.20221208-3903-swj30r
13
+ make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio'
14
14
  compiling stringio.c
15
15
  linking shared-object stringio.so
16
- make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio'
16
+ make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio'
17
17
 
18
- current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio
19
- make DESTDIR\= sitearchdir\=./.gem.20221207-3909-zgfxbv sitelibdir\=./.gem.20221207-3909-zgfxbv install
20
- make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio'
21
- /usr/bin/install -c -m 0755 stringio.so ./.gem.20221207-3909-zgfxbv
22
- make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.2/ext/stringio'
18
+ current directory: /home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio
19
+ make DESTDIR\= sitearchdir\=./.gem.20221208-3903-swj30r sitelibdir\=./.gem.20221208-3903-swj30r install
20
+ make[1]: Entering directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio'
21
+ /usr/bin/install -c -m 0755 stringio.so ./.gem.20221208-3903-swj30r
22
+ make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-platform-bank/ruby/vendor/bundle/ruby/3.1.0/gems/stringio-3.0.3/ext/stringio'
@@ -1,6 +1,7 @@
1
1
  # Psych
2
2
 
3
3
  * https://github.com/ruby/psych
4
+ * https://docs.ruby-lang.org/en/master/Psych.html
4
5
 
5
6
  ## Description
6
7
 
@@ -32,6 +33,11 @@ If you want a newer gem release of Psych, you can use rubygems:
32
33
 
33
34
  gem install psych
34
35
 
36
+
37
+ Psych supported the static build with specific version of libyaml sources. You can build psych with libyaml-0.2.5 like this.
38
+
39
+ gem install psych -- --with-libyaml-source-dir=/path/to/libyaml-0.2.5
40
+
35
41
  In order to use the gem release in your app, and not the stdlib version,
36
42
  you'll need the following:
37
43
 
@@ -44,11 +50,6 @@ Or if you use Bundler add this to your `Gemfile`:
44
50
 
45
51
  JRuby ships with a pure Java implementation of Psych.
46
52
 
47
- If you're on Rubinius, Psych is available in 1.9 mode, please refer to the
48
- Language Modes section of the [Rubinius
49
- README](https://github.com/rubinius/rubinius#readme) for more information on
50
- building and 1.9 mode.
51
-
52
53
  ## License
53
54
 
54
55
  Copyright 2009 Aaron Patterson, et al.
@@ -2,7 +2,7 @@
2
2
 
3
3
  module Psych
4
4
  # The version of Psych you are using
5
- VERSION = '5.0.0'
5
+ VERSION = '5.0.1'
6
6
 
7
7
  if RUBY_ENGINE == 'jruby'
8
8
  DEFAULT_SNAKEYAML_VERSION = '1.33'.freeze