cybrid_api_id_ruby 0.126.55 → 0.126.56

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (408) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +17 -10
  3. data/README.md +5 -5
  4. data/cybrid_api_id_ruby.gemspec +1 -1
  5. data/lib/cybrid_api_id_ruby/api/bank_applications_idp_api.rb +1 -1
  6. data/lib/cybrid_api_id_ruby/api/customer_tokens_idp_api.rb +1 -1
  7. data/lib/cybrid_api_id_ruby/api/organization_applications_idp_api.rb +1 -1
  8. data/lib/cybrid_api_id_ruby/api/users_idp_api.rb +1 -1
  9. data/lib/cybrid_api_id_ruby/api_client.rb +1 -1
  10. data/lib/cybrid_api_id_ruby/api_error.rb +1 -1
  11. data/lib/cybrid_api_id_ruby/configuration.rb +1 -1
  12. data/lib/cybrid_api_id_ruby/models/application_idp_model.rb +1 -1
  13. data/lib/cybrid_api_id_ruby/models/application_list_idp_model.rb +1 -1
  14. data/lib/cybrid_api_id_ruby/models/application_with_secret_all_of_idp_model.rb +1 -1
  15. data/lib/cybrid_api_id_ruby/models/application_with_secret_idp_model.rb +1 -1
  16. data/lib/cybrid_api_id_ruby/models/customer_token_idp_model.rb +1 -1
  17. data/lib/cybrid_api_id_ruby/models/error_response_idp_model.rb +1 -1
  18. data/lib/cybrid_api_id_ruby/models/patch_user_idp_model.rb +1 -1
  19. data/lib/cybrid_api_id_ruby/models/post_bank_application_idp_model.rb +1 -1
  20. data/lib/cybrid_api_id_ruby/models/post_customer_token_idp_model.rb +1 -1
  21. data/lib/cybrid_api_id_ruby/models/post_organization_application_idp_model.rb +1 -1
  22. data/lib/cybrid_api_id_ruby/models/post_user_idp_model.rb +1 -1
  23. data/lib/cybrid_api_id_ruby/models/user_idp_model.rb +1 -1
  24. data/lib/cybrid_api_id_ruby/models/user_list_idp_model.rb +1 -1
  25. data/lib/cybrid_api_id_ruby/version.rb +2 -2
  26. data/lib/cybrid_api_id_ruby.rb +1 -1
  27. data/spec/api/bank_applications_idp_api_spec.rb +1 -1
  28. data/spec/api/customer_tokens_idp_api_spec.rb +1 -1
  29. data/spec/api/organization_applications_idp_api_spec.rb +1 -1
  30. data/spec/api/users_idp_api_spec.rb +1 -1
  31. data/spec/api_client_spec.rb +1 -1
  32. data/spec/configuration_spec.rb +1 -1
  33. data/spec/models/application_idp_model_spec.rb +1 -1
  34. data/spec/models/application_list_idp_model_spec.rb +1 -1
  35. data/spec/models/application_with_secret_all_of_idp_model_spec.rb +1 -1
  36. data/spec/models/application_with_secret_idp_model_spec.rb +1 -1
  37. data/spec/models/customer_token_idp_model_spec.rb +1 -1
  38. data/spec/models/error_response_idp_model_spec.rb +1 -1
  39. data/spec/models/patch_user_idp_model_spec.rb +1 -1
  40. data/spec/models/post_bank_application_idp_model_spec.rb +1 -1
  41. data/spec/models/post_customer_token_idp_model_spec.rb +1 -1
  42. data/spec/models/post_organization_application_idp_model_spec.rb +1 -1
  43. data/spec/models/post_user_idp_model_spec.rb +1 -1
  44. data/spec/models/user_idp_model_spec.rb +1 -1
  45. data/spec/models/user_list_idp_model_spec.rb +1 -1
  46. data/spec/spec_helper.rb +1 -1
  47. data/vendor/bundle/ruby/3.3.0/cache/byebug-13.0.0.gem +0 -0
  48. data/vendor/bundle/ruby/3.3.0/cache/io-console-0.8.2.gem +0 -0
  49. data/vendor/bundle/ruby/3.3.0/cache/pry-0.16.0.gem +0 -0
  50. data/vendor/bundle/ruby/3.3.0/cache/pry-byebug-3.12.0.gem +0 -0
  51. data/vendor/bundle/ruby/3.3.0/cache/reline-0.6.3.gem +0 -0
  52. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/byebug-13.0.0/byebug/byebug.so +0 -0
  53. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/{byebug-12.0.0 → byebug-13.0.0}/gem_make.out +18 -18
  54. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/date-3.5.1/gem_make.out +5 -5
  55. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/io-console-0.8.2/gem.build_complete +0 -0
  56. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/io-console-0.8.2/gem_make.out +39 -0
  57. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/io-console-0.8.2/io/console.so +0 -0
  58. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/io-console-0.8.2/mkmf.log +352 -0
  59. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/jaro_winkler-1.5.6/gem_make.out +5 -5
  60. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/psych-5.3.1/gem_make.out +5 -5
  61. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/racc-1.8.1/gem_make.out +5 -5
  62. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/stringio-3.2.0/gem_make.out +5 -5
  63. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/CHANGELOG.md +22 -1
  64. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/CONTRIBUTING.md +9 -9
  65. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/GUIDE.md +1 -1
  66. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/README.md +2 -2
  67. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/ext/byebug/breakpoint.c +42 -41
  68. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/ext/byebug/byebug.c +6 -6
  69. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/ext/byebug/byebug.h +2 -0
  70. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/ext/byebug/context.c +47 -52
  71. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/ext/byebug/threads.c +23 -10
  72. data/vendor/bundle/ruby/3.3.0/gems/byebug-13.0.0/lib/byebug/byebug.so +0 -0
  73. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/irb.rb +2 -1
  74. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/where.rb +1 -1
  75. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/context.rb +1 -1
  76. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/parse.rb +2 -0
  77. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/history.rb +8 -18
  78. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/interfaces/local_interface.rb +8 -8
  79. data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/version.rb +1 -1
  80. data/vendor/bundle/ruby/3.3.0/gems/io-console-0.8.2/.document +5 -0
  81. data/vendor/bundle/ruby/3.3.0/gems/io-console-0.8.2/BSDL +22 -0
  82. data/vendor/bundle/ruby/3.3.0/gems/io-console-0.8.2/COPYING +56 -0
  83. data/vendor/bundle/ruby/3.3.0/gems/io-console-0.8.2/README.md +46 -0
  84. data/vendor/bundle/ruby/3.3.0/gems/io-console-0.8.2/ext/io/console/Makefile +271 -0
  85. data/vendor/bundle/ruby/3.3.0/gems/io-console-0.8.2/ext/io/console/console.c +2022 -0
  86. data/vendor/bundle/ruby/3.3.0/gems/io-console-0.8.2/ext/io/console/extconf.rb +61 -0
  87. data/vendor/bundle/ruby/3.3.0/gems/io-console-0.8.2/ext/io/console/win32_vk.inc +1390 -0
  88. data/vendor/bundle/ruby/3.3.0/gems/io-console-0.8.2/lib/io/console/size.rb +23 -0
  89. data/vendor/bundle/ruby/3.3.0/gems/io-console-0.8.2/lib/io/console.so +0 -0
  90. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/CHANGELOG.md +19 -0
  91. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/LICENSE +1 -1
  92. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/README.md +2 -2
  93. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/cli.rb +1 -1
  94. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/show_doc.rb +1 -10
  95. data/vendor/bundle/ruby/3.3.0/gems/pry-0.16.0/lib/pry/commands/show_source.rb +57 -0
  96. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/config.rb +15 -8
  97. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/method/weird_method_locator.rb +3 -3
  98. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/method.rb +1 -1
  99. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/pry_class.rb +1 -28
  100. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/version.rb +1 -1
  101. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/wrapped_module/candidate.rb +7 -1
  102. data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry.rb +1 -1
  103. data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/CHANGELOG.md +11 -0
  104. data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/README.md +1 -1
  105. data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/version.rb +1 -1
  106. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/BSDL +22 -0
  107. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/COPYING +56 -0
  108. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/README.md +94 -0
  109. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/config.rb +378 -0
  110. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/face.rb +199 -0
  111. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/history.rb +76 -0
  112. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/io/ansi.rb +310 -0
  113. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/io/dumb.rb +120 -0
  114. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/io/windows.rb +530 -0
  115. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/io.rb +55 -0
  116. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/key_actor/base.rb +37 -0
  117. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/key_actor/composite.rb +17 -0
  118. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/key_actor/emacs.rb +517 -0
  119. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/key_actor/vi_command.rb +518 -0
  120. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/key_actor/vi_insert.rb +517 -0
  121. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/key_actor.rb +8 -0
  122. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/key_stroke.rb +119 -0
  123. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/kill_ring.rb +125 -0
  124. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/line_editor.rb +2356 -0
  125. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/unicode/east_asian_width.rb +1292 -0
  126. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/unicode.rb +421 -0
  127. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline/version.rb +3 -0
  128. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/lib/reline.rb +527 -0
  129. data/vendor/bundle/ruby/3.3.0/gems/reline-0.6.3/license_of_rb-readline +25 -0
  130. data/vendor/bundle/ruby/3.3.0/specifications/{byebug-12.0.0.gemspec → byebug-13.0.0.gemspec} +5 -4
  131. data/vendor/bundle/ruby/3.3.0/specifications/io-console-0.8.2.gemspec +25 -0
  132. data/vendor/bundle/ruby/3.3.0/specifications/{pry-0.15.2.gemspec → pry-0.16.0.gemspec} +6 -5
  133. data/vendor/bundle/ruby/3.3.0/specifications/{pry-byebug-3.11.0.gemspec → pry-byebug-3.12.0.gemspec} +8 -7
  134. data/vendor/bundle/ruby/3.3.0/specifications/reline-0.6.3.gemspec +26 -0
  135. metadata +351 -309
  136. data/vendor/bundle/ruby/3.3.0/cache/byebug-12.0.0.gem +0 -0
  137. data/vendor/bundle/ruby/3.3.0/cache/pry-0.15.2.gem +0 -0
  138. data/vendor/bundle/ruby/3.3.0/cache/pry-byebug-3.11.0.gem +0 -0
  139. data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/byebug-12.0.0/byebug/byebug.so +0 -0
  140. data/vendor/bundle/ruby/3.3.0/gems/byebug-12.0.0/lib/byebug/byebug.so +0 -0
  141. data/vendor/bundle/ruby/3.3.0/gems/pry-0.15.2/lib/pry/commands/show_source.rb +0 -118
  142. /data/vendor/bundle/ruby/3.3.0/extensions/x86_64-linux/3.3.0/{byebug-12.0.0 → byebug-13.0.0}/gem.build_complete +0 -0
  143. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/LICENSE +0 -0
  144. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/exe/byebug +0 -0
  145. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/ext/byebug/Makefile +0 -0
  146. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/ext/byebug/extconf.rb +0 -0
  147. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/ext/byebug/locker.c +0 -0
  148. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/attacher.rb +0 -0
  149. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/breakpoint.rb +0 -0
  150. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/command.rb +0 -0
  151. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/command_list.rb +0 -0
  152. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/break.rb +0 -0
  153. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/catch.rb +0 -0
  154. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/condition.rb +0 -0
  155. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/continue.rb +0 -0
  156. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/debug.rb +0 -0
  157. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/delete.rb +0 -0
  158. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/disable/breakpoints.rb +0 -0
  159. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/disable/display.rb +0 -0
  160. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/disable.rb +0 -0
  161. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/display.rb +0 -0
  162. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/down.rb +0 -0
  163. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/edit.rb +0 -0
  164. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/enable/breakpoints.rb +0 -0
  165. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/enable/display.rb +0 -0
  166. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/enable.rb +0 -0
  167. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/finish.rb +0 -0
  168. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/frame.rb +0 -0
  169. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/help.rb +0 -0
  170. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/history.rb +0 -0
  171. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/info/breakpoints.rb +0 -0
  172. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/info/display.rb +0 -0
  173. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/info/file.rb +0 -0
  174. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/info/line.rb +0 -0
  175. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/info/program.rb +0 -0
  176. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/info.rb +0 -0
  177. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/interrupt.rb +0 -0
  178. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/kill.rb +0 -0
  179. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/list.rb +0 -0
  180. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/method.rb +0 -0
  181. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/next.rb +0 -0
  182. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/pry.rb +0 -0
  183. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/quit.rb +0 -0
  184. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/restart.rb +0 -0
  185. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/save.rb +0 -0
  186. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/set.rb +0 -0
  187. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/show.rb +0 -0
  188. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/skip.rb +0 -0
  189. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/source.rb +0 -0
  190. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/step.rb +0 -0
  191. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/thread/current.rb +0 -0
  192. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/thread/list.rb +0 -0
  193. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/thread/resume.rb +0 -0
  194. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/thread/stop.rb +0 -0
  195. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/thread/switch.rb +0 -0
  196. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/thread.rb +0 -0
  197. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/tracevar.rb +0 -0
  198. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/undisplay.rb +0 -0
  199. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/untracevar.rb +0 -0
  200. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/up.rb +0 -0
  201. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/var/all.rb +0 -0
  202. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/var/args.rb +0 -0
  203. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/var/const.rb +0 -0
  204. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/var/global.rb +0 -0
  205. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/var/instance.rb +0 -0
  206. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/var/local.rb +0 -0
  207. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands/var.rb +0 -0
  208. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/commands.rb +0 -0
  209. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/core.rb +0 -0
  210. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/errors.rb +0 -0
  211. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/frame.rb +0 -0
  212. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/bin.rb +0 -0
  213. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/eval.rb +0 -0
  214. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/file.rb +0 -0
  215. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/frame.rb +0 -0
  216. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/path.rb +0 -0
  217. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/reflection.rb +0 -0
  218. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/string.rb +0 -0
  219. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/thread.rb +0 -0
  220. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/toggle.rb +0 -0
  221. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/helpers/var.rb +0 -0
  222. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/interface.rb +0 -0
  223. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/interfaces/remote_interface.rb +0 -0
  224. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/interfaces/script_interface.rb +0 -0
  225. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/interfaces/test_interface.rb +0 -0
  226. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/option_setter.rb +0 -0
  227. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/printers/base.rb +0 -0
  228. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/printers/plain.rb +0 -0
  229. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/printers/texts/base.yml +0 -0
  230. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/printers/texts/plain.yml +0 -0
  231. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/processors/command_processor.rb +0 -0
  232. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/processors/control_processor.rb +0 -0
  233. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/processors/post_mortem_processor.rb +0 -0
  234. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/processors/script_processor.rb +0 -0
  235. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/remote/client.rb +0 -0
  236. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/remote/server.rb +0 -0
  237. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/remote.rb +0 -0
  238. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/runner.rb +0 -0
  239. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/setting.rb +0 -0
  240. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/autoirb.rb +0 -0
  241. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/autolist.rb +0 -0
  242. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/autopry.rb +0 -0
  243. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/autosave.rb +0 -0
  244. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/basename.rb +0 -0
  245. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/callstyle.rb +0 -0
  246. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/fullpath.rb +0 -0
  247. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/histfile.rb +0 -0
  248. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/histsize.rb +0 -0
  249. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/linetrace.rb +0 -0
  250. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/listsize.rb +0 -0
  251. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/post_mortem.rb +0 -0
  252. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/savefile.rb +0 -0
  253. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/stack_on_error.rb +0 -0
  254. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/settings/width.rb +0 -0
  255. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/source_file_formatter.rb +0 -0
  256. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug/subcommands.rb +0 -0
  257. /data/vendor/bundle/ruby/3.3.0/gems/{byebug-12.0.0 → byebug-13.0.0}/lib/byebug.rb +0 -0
  258. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/bin/pry +0 -0
  259. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/basic_object.rb +0 -0
  260. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/block_command.rb +0 -0
  261. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/class_command.rb +0 -0
  262. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/code/code_file.rb +0 -0
  263. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/code/code_range.rb +0 -0
  264. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/code/loc.rb +0 -0
  265. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/code.rb +0 -0
  266. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/code_object.rb +0 -0
  267. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/color_printer.rb +0 -0
  268. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/command.rb +0 -0
  269. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/command_set.rb +0 -0
  270. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/command_state.rb +0 -0
  271. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/amend_line.rb +0 -0
  272. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/bang.rb +0 -0
  273. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/bang_pry.rb +0 -0
  274. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/cat/abstract_formatter.rb +0 -0
  275. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/cat/exception_formatter.rb +0 -0
  276. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/cat/file_formatter.rb +0 -0
  277. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/cat/input_expression_formatter.rb +0 -0
  278. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/cat.rb +0 -0
  279. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/cd.rb +0 -0
  280. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/change_inspector.rb +0 -0
  281. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/change_prompt.rb +0 -0
  282. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/clear_screen.rb +0 -0
  283. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/code_collector.rb +0 -0
  284. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/disable_pry.rb +0 -0
  285. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/easter_eggs.rb +0 -0
  286. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/edit/exception_patcher.rb +0 -0
  287. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/edit/file_and_line_locator.rb +0 -0
  288. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/edit.rb +0 -0
  289. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/exit.rb +0 -0
  290. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/exit_all.rb +0 -0
  291. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/exit_program.rb +0 -0
  292. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/find_method.rb +0 -0
  293. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/fix_indent.rb +0 -0
  294. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/help.rb +0 -0
  295. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/hist.rb +0 -0
  296. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/import_set.rb +0 -0
  297. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/jump_to.rb +0 -0
  298. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/list_inspectors.rb +0 -0
  299. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/config.rb +0 -0
  300. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/constants.rb +0 -0
  301. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/formatter.rb +0 -0
  302. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/globals.rb +0 -0
  303. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/grep.rb +0 -0
  304. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/instance_vars.rb +0 -0
  305. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/interrogatable.rb +0 -0
  306. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/jruby_hacks.rb +0 -0
  307. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/local_names.rb +0 -0
  308. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/local_vars.rb +0 -0
  309. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/ls_entity.rb +0 -0
  310. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/methods.rb +0 -0
  311. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/methods_helper.rb +0 -0
  312. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls/self_methods.rb +0 -0
  313. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ls.rb +0 -0
  314. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/nesting.rb +0 -0
  315. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/play.rb +0 -0
  316. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/pry_backtrace.rb +0 -0
  317. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/pry_version.rb +0 -0
  318. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/raise_up.rb +0 -0
  319. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/reload_code.rb +0 -0
  320. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/reset.rb +0 -0
  321. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/ri.rb +0 -0
  322. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/save_file.rb +0 -0
  323. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/shell_command.rb +0 -0
  324. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/shell_mode.rb +0 -0
  325. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/show_info.rb +0 -0
  326. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/show_input.rb +0 -0
  327. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/stat.rb +0 -0
  328. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/switch_to.rb +0 -0
  329. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/toggle_color.rb +0 -0
  330. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/watch_expression/expression.rb +0 -0
  331. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/watch_expression.rb +0 -0
  332. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/whereami.rb +0 -0
  333. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/commands/wtf.rb +0 -0
  334. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/config/attributable.rb +0 -0
  335. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/config/lazy_value.rb +0 -0
  336. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/config/memoized_value.rb +0 -0
  337. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/config/value.rb +0 -0
  338. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/control_d_handler.rb +0 -0
  339. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/core_extensions.rb +0 -0
  340. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/editor.rb +0 -0
  341. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/env.rb +0 -0
  342. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/exception_handler.rb +0 -0
  343. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/exceptions.rb +0 -0
  344. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/forwardable.rb +0 -0
  345. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/helpers/base_helpers.rb +0 -0
  346. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/helpers/command_helpers.rb +0 -0
  347. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/helpers/documentation_helpers.rb +0 -0
  348. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/helpers/options_helpers.rb +0 -0
  349. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/helpers/platform.rb +0 -0
  350. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/helpers/table.rb +0 -0
  351. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/helpers/text.rb +0 -0
  352. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/helpers.rb +0 -0
  353. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/history.rb +0 -0
  354. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/hooks.rb +0 -0
  355. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/indent.rb +0 -0
  356. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/input/simple_stdio.rb +0 -0
  357. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/input_completer.rb +0 -0
  358. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/input_lock.rb +0 -0
  359. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/inspector.rb +0 -0
  360. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/last_exception.rb +0 -0
  361. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/method/disowned.rb +0 -0
  362. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/method/patcher.rb +0 -0
  363. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/object_path.rb +0 -0
  364. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/output.rb +0 -0
  365. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/pager.rb +0 -0
  366. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/prompt.rb +0 -0
  367. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/pry_instance.rb +0 -0
  368. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/repl.rb +0 -0
  369. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/repl_file_loader.rb +0 -0
  370. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/ring.rb +0 -0
  371. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/slop/LICENSE +0 -0
  372. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/slop/commands.rb +0 -0
  373. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/slop/option.rb +0 -0
  374. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/slop.rb +0 -0
  375. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/syntax_highlighter.rb +0 -0
  376. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/system_command_handler.rb +0 -0
  377. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/testable/evalable.rb +0 -0
  378. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/testable/mockable.rb +0 -0
  379. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/testable/pry_tester.rb +0 -0
  380. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/testable/utility.rb +0 -0
  381. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/testable/variables.rb +0 -0
  382. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/testable.rb +0 -0
  383. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/warning.rb +0 -0
  384. /data/vendor/bundle/ruby/3.3.0/gems/{pry-0.15.2 → pry-0.16.0}/lib/pry/wrapped_module.rb +0 -0
  385. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/LICENSE +0 -0
  386. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/byebug/processors/pry_processor.rb +0 -0
  387. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry/byebug/breakpoints.rb +0 -0
  388. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/base.rb +0 -0
  389. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/cli.rb +0 -0
  390. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands/backtrace.rb +0 -0
  391. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands/breakpoint.rb +0 -0
  392. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands/continue.rb +0 -0
  393. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands/down.rb +0 -0
  394. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands/exit_all.rb +0 -0
  395. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands/finish.rb +0 -0
  396. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands/frame.rb +0 -0
  397. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands/next.rb +0 -0
  398. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands/step.rb +0 -0
  399. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands/up.rb +0 -0
  400. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/commands.rb +0 -0
  401. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/control_d_handler.rb +0 -0
  402. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/helpers/breakpoints.rb +0 -0
  403. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/helpers/location.rb +0 -0
  404. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/helpers/multiline.rb +0 -0
  405. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/helpers/navigation.rb +0 -0
  406. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/pry_ext.rb +0 -0
  407. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug/pry_remote_ext.rb +0 -0
  408. /data/vendor/bundle/ruby/3.3.0/gems/{pry-byebug-3.11.0 → pry-byebug-3.12.0}/lib/pry-byebug.rb +0 -0
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 5f177d80d481cf65876b1569517ea61ea6418235d6cb500aec0016661bf2bd8a
4
- data.tar.gz: 9e52c4f9067bd36b4d9a206a0e309ec4ec821654973a0fc3851b5991bd89fda8
3
+ metadata.gz: 1966c56176888d7aa28427bd7795263b037268238798cc7eb076c16dfc120cbb
4
+ data.tar.gz: d56692c2a9d293409c894d3f894c954fae5d0db0373dea1b59e90ea34c76b591
5
5
  SHA512:
6
- metadata.gz: 2c39ac1b542b5d89cfb83ad50ba3a0aa2a0442d0b9c14470e80c4ef45b834c11ae1d7f0f5b1c19d01242f174da237fb73ea6691c2a9b54cdd0d0e3caabd0da7e
7
- data.tar.gz: b1e8ff47628ca77d2b8a3df708a71b5d49ce6877f3cdb456329ce35050cf7af2b971053769ade398035de4ba2865d54c92fe999e2f693f15406e340919175d15
6
+ metadata.gz: f63a2673aba46a3ae9650128f92f777041e7018401368a24758a696defc041d6b96518885630d310214613ecdbca5c3b0289e7e5e6d5db3130b2f74b2ea1e427
7
+ data.tar.gz: 1fa25844f27b3c6a80d235aeb8423a9056ffb7b94dab01840971d7ef13c959c0fbbd5606b63ed7ba67dad1795c5d8034486880068a942c1c35dd977005347f6b
data/Gemfile.lock CHANGED
@@ -1,14 +1,15 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- cybrid_api_id_ruby (0.126.55)
4
+ cybrid_api_id_ruby (0.126.56)
5
5
  typhoeus (~> 1.0, >= 1.0.1)
6
6
 
7
7
  GEM
8
8
  remote: https://rubygems.org/
9
9
  specs:
10
10
  ast (2.4.3)
11
- byebug (12.0.0)
11
+ byebug (13.0.0)
12
+ reline (>= 0.6.0)
12
13
  coderay (1.1.3)
13
14
  date (3.5.1)
14
15
  diff-lcs (1.6.2)
@@ -25,24 +26,28 @@ GEM
25
26
  ffi (1.17.3-x86_64-darwin)
26
27
  ffi (1.17.3-x86_64-linux-gnu)
27
28
  ffi (1.17.3-x86_64-linux-musl)
29
+ io-console (0.8.2)
28
30
  jaro_winkler (1.5.6)
29
31
  method_source (1.1.0)
30
32
  parallel (1.27.0)
31
33
  parser (3.3.10.1)
32
34
  ast (~> 2.4.1)
33
35
  racc
34
- pry (0.15.2)
36
+ pry (0.16.0)
35
37
  coderay (~> 1.1)
36
38
  method_source (~> 1.0)
37
- pry-byebug (3.11.0)
38
- byebug (~> 12.0)
39
- pry (>= 0.13, < 0.16)
39
+ reline (>= 0.6.0)
40
+ pry-byebug (3.12.0)
41
+ byebug (~> 13.0)
42
+ pry (>= 0.13, < 0.17)
40
43
  psych (5.3.1)
41
44
  date
42
45
  stringio
43
46
  racc (1.8.1)
44
47
  rainbow (3.1.1)
45
48
  rake (13.0.6)
49
+ reline (0.6.3)
50
+ io-console (~> 0.5)
46
51
  rspec (3.13.2)
47
52
  rspec-core (~> 3.13.0)
48
53
  rspec-expectations (~> 3.13.0)
@@ -92,9 +97,9 @@ DEPENDENCIES
92
97
 
93
98
  CHECKSUMS
94
99
  ast (2.4.3) sha256=954615157c1d6a382bc27d690d973195e79db7f55e9765ac7c481c60bdb4d383
95
- byebug (12.0.0) sha256=d4a150d291cca40b66ec9ca31f754e93fed8aa266a17335f71bb0afa7fca1a1e
100
+ byebug (13.0.0) sha256=d2263efe751941ca520fa29744b71972d39cbc41839496706f5d9b22e92ae05d
96
101
  coderay (1.1.3) sha256=dc530018a4684512f8f38143cd2a096c9f02a1fc2459edcfe534787a7fc77d4b
97
- cybrid_api_id_ruby (0.126.55)
102
+ cybrid_api_id_ruby (0.126.56)
98
103
  date (3.5.1) sha256=750d06384d7b9c15d562c76291407d89e368dda4d4fff957eb94962d325a0dc0
99
104
  diff-lcs (1.6.2) sha256=9ae0d2cba7d4df3075fe8cd8602a8604993efc0dfa934cff568969efb1909962
100
105
  ethon (0.15.0) sha256=0809805a035bc10f54162ca99f15ded49e428e0488bcfe1c08c821e18261a74d
@@ -109,16 +114,18 @@ CHECKSUMS
109
114
  ffi (1.17.3-x86_64-darwin) sha256=1f211811eb5cfaa25998322cdd92ab104bfbd26d1c4c08471599c511f2c00bb5
110
115
  ffi (1.17.3-x86_64-linux-gnu) sha256=3746b01f677aae7b16dc1acb7cb3cc17b3e35bdae7676a3f568153fb0e2c887f
111
116
  ffi (1.17.3-x86_64-linux-musl) sha256=086b221c3a68320b7564066f46fed23449a44f7a1935f1fe5a245bd89d9aea56
117
+ io-console (0.8.2) sha256=d6e3ae7a7cc7574f4b8893b4fca2162e57a825b223a177b7afa236c5ef9814cc
112
118
  jaro_winkler (1.5.6) sha256=007db7805527ada1cc12f2547676181d63b0a504ec4dd7a9a2eb2424521ccd81
113
119
  method_source (1.1.0) sha256=181301c9c45b731b4769bc81e8860e72f9161ad7d66dd99103c9ab84f560f5c5
114
120
  parallel (1.27.0) sha256=4ac151e1806b755fb4e2dc2332cbf0e54f2e24ba821ff2d3dcf86bf6dc4ae130
115
121
  parser (3.3.10.1) sha256=06f6a725d2cd91e5e7f2b7c32ba143631e1f7c8ae2fb918fc4cebec187e6a688
116
- pry (0.15.2) sha256=12d54b8640d3fa29c9211dd4ffb08f3fd8bf7a4fd9b5a73ce5b59c8709385b6b
117
- pry-byebug (3.11.0) sha256=0b0abb7d309bc7f00044d512a3c8567274f7012b944b38becc8440439a1cea72
122
+ pry (0.16.0) sha256=d76c69065698ed1f85e717bd33d7942c38a50868f6b0673c636192b3d1b6054e
123
+ pry-byebug (3.12.0) sha256=594e094ae8a8390a7ad4c7b36ae36e13304ed02664c67417d108dc5f7213d1b7
118
124
  psych (5.3.1) sha256=eb7a57cef10c9d70173ff74e739d843ac3b2c019a003de48447b2963d81b1974
119
125
  racc (1.8.1) sha256=4a7f6929691dbec8b5209a0b373bc2614882b55fc5d2e447a21aaa691303d62f
120
126
  rainbow (3.1.1) sha256=039491aa3a89f42efa1d6dec2fc4e62ede96eb6acd95e52f1ad581182b79bc6a
121
127
  rake (13.0.6) sha256=5ce4bf5037b4196c24ac62834d8db1ce175470391026bd9e557d669beeb19097
128
+ reline (0.6.3) sha256=1198b04973565b36ec0f11542ab3f5cfeeec34823f4e54cebde90968092b1835
122
129
  rspec (3.13.2) sha256=206284a08ad798e61f86d7ca3e376718d52c0bc944626b2349266f239f820587
123
130
  rspec-core (3.13.6) sha256=a8823c6411667b60a8bca135364351dda34cd55e44ff94c4be4633b37d828b2d
124
131
  rspec-expectations (3.13.5) sha256=33a4d3a1d95060aea4c94e9f237030a8f9eae5615e9bd85718fe3a09e4b58836
data/README.md CHANGED
@@ -151,8 +151,8 @@ An `Organization` can have multiple `banks`, in either `Sandbox` or `Production`
151
151
 
152
152
  This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
153
153
 
154
- - API version: v0.126.55
155
- - Package version: 0.126.55
154
+ - API version: v0.126.56
155
+ - Package version: 0.126.56
156
156
  - Build package: org.openapitools.codegen.languages.RubyClientCodegen
157
157
 
158
158
  ## Installation
@@ -168,16 +168,16 @@ gem build cybrid_api_id_ruby.gemspec
168
168
  Then either install the gem locally:
169
169
 
170
170
  ```shell
171
- gem install ./cybrid_api_id_ruby-0.126.55.gem
171
+ gem install ./cybrid_api_id_ruby-0.126.56.gem
172
172
  ```
173
173
 
174
- (for development, run `gem install --dev ./cybrid_api_id_ruby-0.126.55.gem` to install the development dependencies)
174
+ (for development, run `gem install --dev ./cybrid_api_id_ruby-0.126.56.gem` to install the development dependencies)
175
175
 
176
176
  or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
177
177
 
178
178
  Finally add this to the Gemfile:
179
179
 
180
- gem 'cybrid_api_id_ruby', '~> 0.126.55'
180
+ gem 'cybrid_api_id_ruby', '~> 0.126.56'
181
181
 
182
182
  ### Install from Git
183
183
 
@@ -5,7 +5,7 @@
5
5
 
6
6
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
7
7
 
8
- The version of the OpenAPI document: v0.126.55
8
+ The version of the OpenAPI document: v0.126.56
9
9
  Contact: support@cybrid.app
10
10
  Generated by: https://openapi-generator.tech
11
11
  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.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.126.55
6
+ The version of the OpenAPI document: v0.126.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.126.55
6
+ The version of the OpenAPI document: v0.126.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.126.55
6
+ The version of the OpenAPI document: v0.126.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.126.55
6
+ The version of the OpenAPI document: v0.126.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.126.55
6
+ The version of the OpenAPI document: v0.126.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.126.55
6
+ The version of the OpenAPI document: v0.126.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.126.55
6
+ The version of the OpenAPI document: v0.126.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.126.55
6
+ The version of the OpenAPI document: v0.126.56
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0