cybrid_api_id_ruby 0.94.30 → 0.94.33

Sign up to get free protection for your applications and to get access to all the features.
Files changed (922) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +2 -2
  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/post_bank_application_idp_model.rb +1 -1
  18. data/lib/cybrid_api_id_ruby/models/post_customer_token_idp_model.rb +1 -1
  19. data/lib/cybrid_api_id_ruby/models/post_organization_application_idp_model.rb +1 -1
  20. data/lib/cybrid_api_id_ruby/models/post_user_idp_model.rb +1 -1
  21. data/lib/cybrid_api_id_ruby/models/user_idp_model.rb +1 -1
  22. data/lib/cybrid_api_id_ruby/models/user_list_idp_model.rb +1 -1
  23. data/lib/cybrid_api_id_ruby/version.rb +2 -2
  24. data/lib/cybrid_api_id_ruby.rb +1 -1
  25. data/spec/api/bank_applications_idp_api_spec.rb +1 -1
  26. data/spec/api/customer_tokens_idp_api_spec.rb +1 -1
  27. data/spec/api/organization_applications_idp_api_spec.rb +1 -1
  28. data/spec/api/users_idp_api_spec.rb +1 -1
  29. data/spec/api_client_spec.rb +1 -1
  30. data/spec/configuration_spec.rb +1 -1
  31. data/spec/models/application_idp_model_spec.rb +1 -1
  32. data/spec/models/application_list_idp_model_spec.rb +1 -1
  33. data/spec/models/application_with_secret_all_of_idp_model_spec.rb +1 -1
  34. data/spec/models/application_with_secret_idp_model_spec.rb +1 -1
  35. data/spec/models/customer_token_idp_model_spec.rb +1 -1
  36. data/spec/models/post_bank_application_idp_model_spec.rb +1 -1
  37. data/spec/models/post_customer_token_idp_model_spec.rb +1 -1
  38. data/spec/models/post_organization_application_idp_model_spec.rb +1 -1
  39. data/spec/models/post_user_idp_model_spec.rb +1 -1
  40. data/spec/models/user_idp_model_spec.rb +1 -1
  41. data/spec/models/user_list_idp_model_spec.rb +1 -1
  42. data/spec/spec_helper.rb +1 -1
  43. data/vendor/bundle/ruby/3.2.0/cache/ffi-1.16.1.gem +0 -0
  44. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/byebug-11.1.3/gem_make.out +5 -5
  45. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/ffi-1.16.1/ffi_c.so +0 -0
  46. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/ffi-1.16.1/gem_make.out +55 -0
  47. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/ffi-1.16.1/mkmf.log +268 -0
  48. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/jaro_winkler-1.5.6/gem_make.out +5 -5
  49. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/psych-5.1.0/gem_make.out +5 -5
  50. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/racc-1.7.1/gem_make.out +5 -5
  51. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/stringio-3.0.8/gem_make.out +5 -5
  52. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/CHANGELOG.md +399 -0
  53. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/Gemfile +14 -0
  54. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/README.md +137 -0
  55. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/Rakefile +194 -0
  56. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/AbstractMemory.c +1126 -0
  57. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/AbstractMemory.h +176 -0
  58. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/ArrayType.c +198 -0
  59. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/ArrayType.h +60 -0
  60. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Buffer.c +417 -0
  61. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Call.c +495 -0
  62. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/DynamicLibrary.c +397 -0
  63. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Function.c +1057 -0
  64. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Function.h +84 -0
  65. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/FunctionInfo.c +320 -0
  66. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/LastError.c +243 -0
  67. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/MappedType.c +211 -0
  68. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/MappedType.h +57 -0
  69. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/MemoryPointer.c +219 -0
  70. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/MethodHandle.c +350 -0
  71. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Pointer.c +546 -0
  72. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Pointer.h +60 -0
  73. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Struct.c +893 -0
  74. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Struct.h +115 -0
  75. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/StructByValue.c +177 -0
  76. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/StructLayout.c +769 -0
  77. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Type.c +447 -0
  78. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Type.h +63 -0
  79. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Types.c +138 -0
  80. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/Variadic.c +345 -0
  81. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/compat.h +82 -0
  82. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/extconf.h +8 -0
  83. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/extconf.rb +115 -0
  84. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/ffi.c +97 -0
  85. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.appveyor/site.exp +16 -0
  86. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.appveyor/unix-noexec.exp +7 -0
  87. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.appveyor.yml +84 -0
  88. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.ci/build-cross-in-container.sh +18 -0
  89. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.ci/build-in-container.sh +10 -0
  90. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.ci/build.sh +124 -0
  91. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.ci/install.sh +78 -0
  92. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.ci/msvs-detect +1103 -0
  93. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.ci/site.exp +29 -0
  94. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.circleci/config.yml +156 -0
  95. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.github/workflows/build.yml +460 -0
  96. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.github/workflows/emscripten.yml +171 -0
  97. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/.gitignore +46 -0
  98. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/LICENSE +21 -0
  99. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/Makefile.am +157 -0
  100. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/Makefile.in +2127 -0
  101. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/README.md +526 -0
  102. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/acinclude.m4 +377 -0
  103. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/compile +347 -0
  104. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/config.guess +1754 -0
  105. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/config.sub +1892 -0
  106. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/configure +22791 -0
  107. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/configure.ac +451 -0
  108. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/configure.host +337 -0
  109. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/doc/Makefile.in +818 -0
  110. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/doc/libffi.texi +1046 -0
  111. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/doc/version.texi +4 -0
  112. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/fficonfig.h.in +188 -0
  113. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/generate-darwin-source-and-headers.py +312 -0
  114. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/include/Makefile.am +9 -0
  115. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/include/Makefile.in +609 -0
  116. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/include/ffi.h.in +527 -0
  117. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/include/ffi_cfi.h +76 -0
  118. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/include/ffi_common.h +182 -0
  119. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/include/tramp.h +45 -0
  120. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/install-sh +541 -0
  121. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/libtool-version +29 -0
  122. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/ltmain.sh +11448 -0
  123. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/m4/ax_cc_maxopt.m4 +198 -0
  124. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/m4/ax_cflags_warn_all.m4 +158 -0
  125. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/m4/ax_compiler_vendor.m4 +119 -0
  126. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/m4/ax_prepend_flag.m4 +51 -0
  127. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/man/Makefile.in +565 -0
  128. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/missing +215 -0
  129. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/msvc_build/aarch64/aarch64_include/ffi.h +511 -0
  130. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/msvcc.sh +353 -0
  131. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/aarch64/ffi.c +1129 -0
  132. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/aarch64/internal.h +100 -0
  133. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/aarch64/sysv.S +543 -0
  134. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/arc/arcompact.S +210 -0
  135. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/arc/ffi.c +443 -0
  136. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/arc/ffitarget.h +67 -0
  137. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/arm/ffi.c +921 -0
  138. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/arm/ffitarget.h +89 -0
  139. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/arm/internal.h +17 -0
  140. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/arm/sysv.S +456 -0
  141. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/closures.c +1107 -0
  142. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/dlmalloc.c +5171 -0
  143. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/ia64/ffi.c +616 -0
  144. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/ia64/unix.S +585 -0
  145. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/loongarch64/ffi.c +621 -0
  146. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/loongarch64/ffitarget.h +82 -0
  147. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/loongarch64/sysv.S +327 -0
  148. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/m32r/ffi.c +249 -0
  149. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/mips/ffi.c +1309 -0
  150. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/mips/ffitarget.h +251 -0
  151. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/mips/n32.S +772 -0
  152. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/mips/o32.S +561 -0
  153. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/moxie/ffi.c +310 -0
  154. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/or1k/ffi.c +341 -0
  155. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/pa/ffi.c +673 -0
  156. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/pa/ffi64.c +614 -0
  157. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/pa/ffitarget.h +94 -0
  158. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/pa/hpux32.S +417 -0
  159. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/pa/hpux64.S +681 -0
  160. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/pa/linux.S +427 -0
  161. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/powerpc/ffi_linux64.c +1153 -0
  162. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/powerpc/linux64.S +293 -0
  163. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/powerpc/linux64_closure.S +566 -0
  164. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/powerpc/t-aix +5 -0
  165. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/prep_cif.c +283 -0
  166. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/riscv/ffi.c +514 -0
  167. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/sparc/ffi64.c +624 -0
  168. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/tramp.c +716 -0
  169. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/wasm32/ffi.c +934 -0
  170. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/wasm32/ffitarget.h +62 -0
  171. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/x86/ffi.c +832 -0
  172. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/x86/ffi64.c +950 -0
  173. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/x86/ffitarget.h +164 -0
  174. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/x86/ffiw64.c +361 -0
  175. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/x86/internal.h +43 -0
  176. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/x86/internal64.h +36 -0
  177. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/x86/sysv.S +1272 -0
  178. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/x86/sysv_intel.S +998 -0
  179. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/x86/unix64.S +711 -0
  180. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/x86/win64.S +254 -0
  181. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/xtensa/ffi.c +306 -0
  182. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/xtensa/ffitarget.h +57 -0
  183. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/src/xtensa/sysv.S +268 -0
  184. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/Makefile.am +135 -0
  185. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/Makefile.in +664 -0
  186. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/emscripten/build-tests.sh +54 -0
  187. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/emscripten/build.sh +63 -0
  188. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/emscripten/conftest.py +80 -0
  189. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/emscripten/node-tests.sh +48 -0
  190. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/emscripten/test.html +7 -0
  191. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/emscripten/test_libffi.py +51 -0
  192. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/lib/libffi.exp +682 -0
  193. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/lib/target-libpath.exp +283 -0
  194. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.bhaible/test-call.c +1746 -0
  195. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.bhaible/testcases.c +747 -0
  196. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/bpo_38748.c +41 -0
  197. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/ffitest.h +163 -0
  198. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/float_va.c +110 -0
  199. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/return_ll1.c +48 -0
  200. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/return_sl.c +42 -0
  201. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/return_ul.c +42 -0
  202. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/s55.c +60 -0
  203. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/strlen.c +43 -0
  204. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/strlen2.c +49 -0
  205. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/strlen3.c +49 -0
  206. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/strlen4.c +55 -0
  207. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/struct10.c +57 -0
  208. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/struct_by_value_2.c +63 -0
  209. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/struct_by_value_3.c +65 -0
  210. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/struct_by_value_3f.c +65 -0
  211. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/struct_by_value_4.c +67 -0
  212. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/struct_by_value_4f.c +67 -0
  213. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/struct_by_value_big.c +93 -0
  214. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/struct_by_value_small.c +61 -0
  215. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/struct_return_2H.c +63 -0
  216. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/struct_return_8H.c +90 -0
  217. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/va_1.c +78 -0
  218. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/va_2.c +220 -0
  219. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/va_3.c +154 -0
  220. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/va_struct1.c +134 -0
  221. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/va_struct2.c +134 -0
  222. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/va_struct3.c +140 -0
  223. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn0.c +90 -0
  224. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn1.c +83 -0
  225. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn2.c +83 -0
  226. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn3.c +102 -0
  227. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn4.c +91 -0
  228. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn5.c +94 -0
  229. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn6.c +92 -0
  230. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/closure_loc_fn0.c +96 -0
  231. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/closure_simple.c +61 -0
  232. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_12byte.c +112 -0
  233. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_16byte.c +117 -0
  234. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_18byte.c +120 -0
  235. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_19byte.c +131 -0
  236. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_1_1byte.c +93 -0
  237. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_20byte.c +109 -0
  238. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_20byte1.c +113 -0
  239. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_24byte.c +145 -0
  240. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_2byte.c +103 -0
  241. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_3_1byte.c +114 -0
  242. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_3byte1.c +103 -0
  243. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_3byte2.c +103 -0
  244. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_3float.c +113 -0
  245. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_4_1byte.c +120 -0
  246. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_4byte.c +103 -0
  247. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_5_1_byte.c +137 -0
  248. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_5byte.c +116 -0
  249. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_64byte.c +148 -0
  250. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_6_1_byte.c +140 -0
  251. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_6byte.c +121 -0
  252. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_7_1_byte.c +155 -0
  253. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_7byte.c +121 -0
  254. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_8byte.c +102 -0
  255. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_9byte1.c +103 -0
  256. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_9byte2.c +103 -0
  257. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_double.c +111 -0
  258. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_float.c +109 -0
  259. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_longdouble.c +111 -0
  260. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_longdouble_split.c +147 -0
  261. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_longdouble_split2.c +152 -0
  262. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_pointer.c +113 -0
  263. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_sint16.c +108 -0
  264. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_sint32.c +106 -0
  265. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_sint64.c +109 -0
  266. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_uint16.c +108 -0
  267. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_uint32.c +109 -0
  268. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_uint64.c +111 -0
  269. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_dbls_struct.c +68 -0
  270. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_double_va.c +69 -0
  271. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_float.c +46 -0
  272. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_longdouble.c +115 -0
  273. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_longdouble_va.c +80 -0
  274. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_schar.c +78 -0
  275. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_sshort.c +79 -0
  276. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_sshortchar.c +94 -0
  277. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_uchar.c +99 -0
  278. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_ushort.c +78 -0
  279. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_ushortchar.c +94 -0
  280. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_pointer.c +79 -0
  281. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_pointer_stack.c +152 -0
  282. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_schar.c +47 -0
  283. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_sint.c +44 -0
  284. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_sshort.c +45 -0
  285. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_struct_va1.c +125 -0
  286. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_uchar.c +45 -0
  287. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_uint.c +47 -0
  288. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_uint_va.c +49 -0
  289. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_ulong_va.c +49 -0
  290. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_ulonglong.c +49 -0
  291. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/cls_ushort.c +46 -0
  292. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/huge_struct.c +343 -0
  293. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct.c +175 -0
  294. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct1.c +161 -0
  295. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct10.c +146 -0
  296. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct11.c +137 -0
  297. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct12.c +86 -0
  298. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct13.c +115 -0
  299. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct2.c +119 -0
  300. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct3.c +120 -0
  301. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct4.c +120 -0
  302. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct5.c +121 -0
  303. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct6.c +142 -0
  304. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct7.c +120 -0
  305. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct8.c +142 -0
  306. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct9.c +142 -0
  307. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/single_entry_structs1.c +86 -0
  308. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/single_entry_structs2.c +102 -0
  309. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/single_entry_structs3.c +101 -0
  310. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/stret_medium.c +124 -0
  311. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/stret_medium2.c +125 -0
  312. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/testclosure.c +75 -0
  313. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/unwindtest.cc +118 -0
  314. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures/unwindtest_ffi_call.cc +55 -0
  315. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.go/ffitest.h +1 -0
  316. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi.bsd.mk +40 -0
  317. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/libffi.gnu.mk +32 -0
  318. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ext/ffi_c/rbffi.h +55 -0
  319. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/ffi.gemspec +42 -0
  320. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/autopointer.rb +188 -0
  321. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/compat.rb +43 -0
  322. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/data_converter.rb +67 -0
  323. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/dynamic_library.rb +89 -0
  324. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/enum.rb +303 -0
  325. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/ffi.rb +50 -0
  326. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/function.rb +71 -0
  327. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/library.rb +576 -0
  328. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/library_path.rb +109 -0
  329. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/managedstruct.rb +84 -0
  330. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/platform/hppa1.1-linux/types.conf +178 -0
  331. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/platform/hppa2.0-linux/types.conf +178 -0
  332. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/platform/loongarch64-linux/types.conf +141 -0
  333. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/platform/sw_64-linux/types.conf +141 -0
  334. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/platform/x86_64-windows/types.conf +52 -0
  335. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/platform.rb +187 -0
  336. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/struct.rb +317 -0
  337. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/struct_layout.rb +96 -0
  338. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/struct_layout_builder.rb +227 -0
  339. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/types.rb +219 -0
  340. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/variadic.rb +80 -0
  341. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi/version.rb +3 -0
  342. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.16.1/lib/ffi_c.so +0 -0
  343. data/vendor/bundle/ruby/3.2.0/specifications/ffi-1.16.1.gemspec +34 -0
  344. metadata +628 -580
  345. data/vendor/bundle/ruby/3.2.0/cache/ffi-1.15.5.gem +0 -0
  346. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/ffi-1.15.5/ffi_c.so +0 -0
  347. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/ffi-1.15.5/gem_make.out +0 -54
  348. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/ffi-1.15.5/mkmf.log +0 -244
  349. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/CHANGELOG.md +0 -338
  350. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/Gemfile +0 -14
  351. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/README.md +0 -136
  352. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/Rakefile +0 -191
  353. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/AbstractMemory.c +0 -1104
  354. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/AbstractMemory.h +0 -175
  355. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/ArrayType.c +0 -162
  356. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/ArrayType.h +0 -59
  357. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Buffer.c +0 -360
  358. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Call.c +0 -487
  359. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/DynamicLibrary.c +0 -334
  360. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Function.c +0 -917
  361. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Function.h +0 -83
  362. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/FunctionInfo.c +0 -266
  363. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/LastError.c +0 -225
  364. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/MappedType.c +0 -168
  365. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/MappedType.h +0 -59
  366. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/MemoryPointer.c +0 -192
  367. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/MethodHandle.c +0 -348
  368. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Pointer.c +0 -507
  369. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Pointer.h +0 -59
  370. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Struct.c +0 -822
  371. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Struct.h +0 -112
  372. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/StructByValue.c +0 -145
  373. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/StructLayout.c +0 -700
  374. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Type.c +0 -379
  375. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Type.h +0 -61
  376. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Types.c +0 -138
  377. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/Variadic.c +0 -303
  378. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/compat.h +0 -82
  379. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/extconf.h +0 -7
  380. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/extconf.rb +0 -98
  381. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/ffi.c +0 -93
  382. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/.appveyor.yml +0 -66
  383. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/.gitignore +0 -38
  384. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/.travis/build-cross-in-container.sh +0 -14
  385. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/.travis/build-in-container.sh +0 -12
  386. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/.travis/build.sh +0 -142
  387. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/.travis/install.sh +0 -71
  388. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/.travis/site.exp +0 -27
  389. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/.travis.yml +0 -83
  390. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/LICENSE +0 -21
  391. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/Makefile.am +0 -150
  392. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/Makefile.in +0 -2060
  393. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/README.md +0 -486
  394. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/acinclude.m4 +0 -479
  395. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/config.guess +0 -1687
  396. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/config.sub +0 -1851
  397. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/configure +0 -22050
  398. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/configure.ac +0 -415
  399. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/configure.host +0 -318
  400. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/doc/Makefile.in +0 -815
  401. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/doc/libffi.texi +0 -997
  402. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/doc/version.texi +0 -4
  403. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/fficonfig.h.in +0 -223
  404. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/generate-darwin-source-and-headers.py +0 -201
  405. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/include/Makefile.am +0 -9
  406. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/include/Makefile.in +0 -608
  407. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/include/ffi.h.in +0 -523
  408. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/include/ffi_cfi.h +0 -55
  409. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/include/ffi_common.h +0 -153
  410. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/install-sh +0 -518
  411. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/libtool-version +0 -29
  412. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/ltmain.sh +0 -11251
  413. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/m4/ax_cc_maxopt.m4 +0 -194
  414. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/m4/ax_cflags_warn_all.m4 +0 -122
  415. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/m4/ax_compiler_vendor.m4 +0 -88
  416. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/man/Makefile.in +0 -562
  417. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/missing +0 -215
  418. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/msvc_build/aarch64/aarch64_include/ffi.h +0 -511
  419. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/msvcc.sh +0 -353
  420. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/aarch64/ffi.c +0 -1025
  421. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/aarch64/internal.h +0 -68
  422. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/aarch64/sysv.S +0 -451
  423. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/arc/arcompact.S +0 -135
  424. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/arc/ffi.c +0 -266
  425. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/arc/ffitarget.h +0 -53
  426. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/arm/ffi.c +0 -876
  427. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/arm/ffitarget.h +0 -89
  428. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/arm/internal.h +0 -7
  429. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/arm/sysv.S +0 -385
  430. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/closures.c +0 -1021
  431. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/dlmalloc.c +0 -5166
  432. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/ia64/ffi.c +0 -604
  433. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/ia64/unix.S +0 -567
  434. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/m32r/ffi.c +0 -232
  435. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/mips/ffi.c +0 -1134
  436. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/mips/ffitarget.h +0 -244
  437. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/mips/n32.S +0 -663
  438. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/mips/o32.S +0 -504
  439. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/moxie/ffi.c +0 -285
  440. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/or1k/ffi.c +0 -328
  441. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/pa/ffi.c +0 -674
  442. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/pa/ffitarget.h +0 -80
  443. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/pa/hpux32.S +0 -370
  444. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/pa/linux.S +0 -380
  445. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/powerpc/ffi_linux64.c +0 -1153
  446. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/powerpc/linux64.S +0 -291
  447. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/powerpc/linux64_closure.S +0 -564
  448. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/prep_cif.c +0 -263
  449. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/riscv/ffi.c +0 -481
  450. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/sparc/ffi64.c +0 -608
  451. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/x86/ffi.c +0 -770
  452. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/x86/ffi64.c +0 -895
  453. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/x86/ffitarget.h +0 -160
  454. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/x86/ffiw64.c +0 -318
  455. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/x86/internal.h +0 -29
  456. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/x86/internal64.h +0 -22
  457. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/x86/sysv.S +0 -1138
  458. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/x86/sysv_intel.S +0 -995
  459. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/x86/unix64.S +0 -621
  460. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/x86/win64.S +0 -241
  461. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/xtensa/ffi.c +0 -298
  462. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/xtensa/ffitarget.h +0 -53
  463. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/src/xtensa/sysv.S +0 -258
  464. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/Makefile.am +0 -122
  465. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/Makefile.in +0 -648
  466. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/lib/libffi.exp +0 -660
  467. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/lib/target-libpath.exp +0 -283
  468. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.bhaible/test-call.c +0 -1745
  469. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.bhaible/testcases.c +0 -743
  470. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/ffitest.h +0 -138
  471. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/float_va.c +0 -107
  472. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/return_ll1.c +0 -43
  473. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/return_sl.c +0 -38
  474. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/return_ul.c +0 -38
  475. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/strlen.c +0 -44
  476. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/strlen2.c +0 -49
  477. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/strlen3.c +0 -49
  478. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/strlen4.c +0 -55
  479. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/struct10.c +0 -57
  480. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/va_1.c +0 -196
  481. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/va_struct1.c +0 -121
  482. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/va_struct2.c +0 -123
  483. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/va_struct3.c +0 -125
  484. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn0.c +0 -89
  485. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn1.c +0 -81
  486. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn2.c +0 -81
  487. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn3.c +0 -82
  488. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn4.c +0 -89
  489. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn5.c +0 -92
  490. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/closure_fn6.c +0 -90
  491. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/closure_loc_fn0.c +0 -95
  492. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/closure_simple.c +0 -55
  493. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_12byte.c +0 -94
  494. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_16byte.c +0 -95
  495. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_18byte.c +0 -96
  496. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_19byte.c +0 -102
  497. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_1_1byte.c +0 -89
  498. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_20byte.c +0 -91
  499. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_20byte1.c +0 -93
  500. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_24byte.c +0 -113
  501. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_2byte.c +0 -90
  502. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_3_1byte.c +0 -95
  503. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_3byte1.c +0 -90
  504. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_3byte2.c +0 -90
  505. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_3float.c +0 -95
  506. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_4_1byte.c +0 -98
  507. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_4byte.c +0 -90
  508. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_5_1_byte.c +0 -109
  509. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_5byte.c +0 -98
  510. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_64byte.c +0 -124
  511. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_6_1_byte.c +0 -113
  512. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_6byte.c +0 -99
  513. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_7_1_byte.c +0 -117
  514. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_7byte.c +0 -97
  515. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_8byte.c +0 -88
  516. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_9byte1.c +0 -90
  517. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_9byte2.c +0 -91
  518. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_double.c +0 -93
  519. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_float.c +0 -91
  520. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_longdouble.c +0 -92
  521. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_longdouble_split.c +0 -132
  522. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_longdouble_split2.c +0 -115
  523. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_pointer.c +0 -95
  524. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_sint16.c +0 -91
  525. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_sint32.c +0 -91
  526. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_sint64.c +0 -92
  527. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_uint16.c +0 -91
  528. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_uint32.c +0 -91
  529. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_align_uint64.c +0 -93
  530. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_dbls_struct.c +0 -66
  531. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_double_va.c +0 -61
  532. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_float.c +0 -42
  533. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_longdouble.c +0 -105
  534. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_longdouble_va.c +0 -61
  535. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_schar.c +0 -74
  536. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_sshort.c +0 -74
  537. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_sshortchar.c +0 -86
  538. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_uchar.c +0 -91
  539. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_ushort.c +0 -74
  540. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_multi_ushortchar.c +0 -86
  541. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_pointer.c +0 -74
  542. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_pointer_stack.c +0 -142
  543. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_schar.c +0 -44
  544. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_sint.c +0 -42
  545. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_sshort.c +0 -42
  546. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_struct_va1.c +0 -114
  547. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_uchar.c +0 -42
  548. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_uchar_va.c +0 -44
  549. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_uint.c +0 -43
  550. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_uint_va.c +0 -45
  551. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_ulong_va.c +0 -45
  552. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_ulonglong.c +0 -47
  553. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_ushort.c +0 -43
  554. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/cls_ushort_va.c +0 -44
  555. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/ffitest.h +0 -138
  556. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/huge_struct.c +0 -343
  557. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct.c +0 -152
  558. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct1.c +0 -161
  559. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct10.c +0 -134
  560. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct11.c +0 -121
  561. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct2.c +0 -110
  562. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct3.c +0 -111
  563. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct4.c +0 -111
  564. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct5.c +0 -112
  565. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct6.c +0 -131
  566. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct7.c +0 -111
  567. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct8.c +0 -131
  568. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/nested_struct9.c +0 -131
  569. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/stret_medium.c +0 -124
  570. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/stret_medium2.c +0 -125
  571. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/testclosure.c +0 -70
  572. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/unwindtest.cc +0 -117
  573. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.closures/unwindtest_ffi_call.cc +0 -54
  574. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi.bsd.mk +0 -40
  575. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/libffi.gnu.mk +0 -32
  576. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c/rbffi.h +0 -55
  577. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ffi.gemspec +0 -42
  578. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/autopointer.rb +0 -203
  579. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/data_converter.rb +0 -67
  580. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/enum.rb +0 -296
  581. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/ffi.rb +0 -47
  582. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/library.rb +0 -592
  583. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/managedstruct.rb +0 -84
  584. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/platform.rb +0 -185
  585. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/struct.rb +0 -316
  586. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/struct_layout.rb +0 -96
  587. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/struct_layout_builder.rb +0 -227
  588. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/types.rb +0 -194
  589. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/variadic.rb +0 -69
  590. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi/version.rb +0 -3
  591. data/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/lib/ffi_c.so +0 -0
  592. data/vendor/bundle/ruby/3.2.0/specifications/ffi-1.15.5.gemspec +0 -33
  593. /data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/{ffi-1.15.5 → ffi-1.16.1}/gem.build_complete +0 -0
  594. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/COPYING +0 -0
  595. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/LICENSE +0 -0
  596. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/LICENSE.SPECS +0 -0
  597. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/Call.h +0 -0
  598. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/ClosurePool.c +0 -0
  599. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/ClosurePool.h +0 -0
  600. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/DynamicLibrary.h +0 -0
  601. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/LastError.h +0 -0
  602. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/LongDouble.c +0 -0
  603. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/LongDouble.h +0 -0
  604. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/Makefile +0 -0
  605. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/MemoryPointer.h +0 -0
  606. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/MethodHandle.h +0 -0
  607. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/Platform.c +0 -0
  608. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/Platform.h +0 -0
  609. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/StructByValue.h +0 -0
  610. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/Thread.c +0 -0
  611. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/Thread.h +0 -0
  612. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/Types.h +0 -0
  613. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/.travis → ffi-1.16.1/ext/ffi_c/libffi/.ci}/ar-lib +0 -0
  614. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/.travis → ffi-1.16.1/ext/ffi_c/libffi/.ci}/bfin-sim.exp +0 -0
  615. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/.travis → ffi-1.16.1/ext/ffi_c/libffi/.ci}/compile +0 -0
  616. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/.travis → ffi-1.16.1/ext/ffi_c/libffi/.ci}/m32r-sim.exp +0 -0
  617. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/.travis → ffi-1.16.1/ext/ffi_c/libffi/.ci}/moxie-sim.exp +0 -0
  618. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/.travis → ffi-1.16.1/ext/ffi_c/libffi/.ci}/or1k-sim.exp +0 -0
  619. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/.travis → ffi-1.16.1/ext/ffi_c/libffi/.ci}/powerpc-eabisim.exp +0 -0
  620. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/.travis → ffi-1.16.1/ext/ffi_c/libffi/.ci}/wine-sim.exp +0 -0
  621. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/.gitattributes +0 -0
  622. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/.github/issue_template.md +0 -0
  623. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/ChangeLog.old +0 -0
  624. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/LICENSE-BUILDTOOLS +0 -0
  625. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/autogen.sh +0 -0
  626. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/doc/Makefile.am +0 -0
  627. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/libffi.map.in +0 -0
  628. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/libffi.pc.in +0 -0
  629. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/libffi.xcodeproj/project.pbxproj +0 -0
  630. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/libtool-ldflags +0 -0
  631. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/m4/asmcfi.m4 +0 -0
  632. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/m4/ax_append_flag.m4 +0 -0
  633. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/m4/ax_check_compile_flag.m4 +0 -0
  634. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/m4/ax_configure_args.m4 +0 -0
  635. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/m4/ax_enable_builddir.m4 +0 -0
  636. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/m4/ax_gcc_archflag.m4 +0 -0
  637. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/m4/ax_gcc_x86_cpuid.m4 +0 -0
  638. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/m4/ax_require_defined.m4 +0 -0
  639. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/make_sunver.pl +0 -0
  640. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/man/Makefile.am +0 -0
  641. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/man/ffi.3 +0 -0
  642. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/man/ffi_call.3 +0 -0
  643. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/man/ffi_prep_cif.3 +0 -0
  644. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/man/ffi_prep_cif_var.3 +0 -0
  645. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/msvc_build/aarch64/Ffi_staticLib.sln +0 -0
  646. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/msvc_build/aarch64/Ffi_staticLib.vcxproj +0 -0
  647. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/msvc_build/aarch64/Ffi_staticLib.vcxproj.filters +0 -0
  648. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/msvc_build/aarch64/Ffi_staticLib.vcxproj.user +0 -0
  649. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/msvc_build/aarch64/aarch64_include/fficonfig.h +0 -0
  650. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/aarch64/ffitarget.h +0 -0
  651. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/aarch64/win64_armasm.S +0 -0
  652. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/alpha/ffi.c +0 -0
  653. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/alpha/ffitarget.h +0 -0
  654. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/alpha/internal.h +0 -0
  655. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/alpha/osf.S +0 -0
  656. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/arm/sysv_msvc_arm32.S +0 -0
  657. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/avr32/ffi.c +0 -0
  658. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/avr32/ffitarget.h +0 -0
  659. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/avr32/sysv.S +0 -0
  660. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/bfin/ffi.c +0 -0
  661. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/bfin/ffitarget.h +0 -0
  662. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/bfin/sysv.S +0 -0
  663. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/cris/ffi.c +0 -0
  664. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/cris/ffitarget.h +0 -0
  665. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/cris/sysv.S +0 -0
  666. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/csky/ffi.c +0 -0
  667. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/csky/ffitarget.h +0 -0
  668. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/csky/sysv.S +0 -0
  669. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/debug.c +0 -0
  670. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/frv/eabi.S +0 -0
  671. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/frv/ffi.c +0 -0
  672. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/frv/ffitarget.h +0 -0
  673. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/ia64/ffitarget.h +0 -0
  674. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/ia64/ia64_flags.h +0 -0
  675. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/java_raw_api.c +0 -0
  676. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/kvx/asm.h +0 -0
  677. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/kvx/ffi.c +0 -0
  678. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/kvx/ffitarget.h +0 -0
  679. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/kvx/sysv.S +0 -0
  680. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/m32r/ffitarget.h +0 -0
  681. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/m32r/sysv.S +0 -0
  682. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/m68k/ffi.c +0 -0
  683. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/m68k/ffitarget.h +0 -0
  684. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/m68k/sysv.S +0 -0
  685. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/m88k/ffi.c +0 -0
  686. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/m88k/ffitarget.h +0 -0
  687. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/m88k/obsd.S +0 -0
  688. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/metag/ffi.c +0 -0
  689. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/metag/ffitarget.h +0 -0
  690. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/metag/sysv.S +0 -0
  691. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/microblaze/ffi.c +0 -0
  692. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/microblaze/ffitarget.h +0 -0
  693. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/microblaze/sysv.S +0 -0
  694. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/moxie/eabi.S +0 -0
  695. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/moxie/ffitarget.h +0 -0
  696. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/nios2/ffi.c +0 -0
  697. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/nios2/ffitarget.h +0 -0
  698. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/nios2/sysv.S +0 -0
  699. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/or1k/ffitarget.h +0 -0
  700. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/or1k/sysv.S +0 -0
  701. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/aix.S +0 -0
  702. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/aix_closure.S +0 -0
  703. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/asm.h +0 -0
  704. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/darwin.S +0 -0
  705. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/darwin_closure.S +0 -0
  706. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/ffi.c +0 -0
  707. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/ffi_darwin.c +0 -0
  708. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/ffi_powerpc.h +0 -0
  709. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/ffi_sysv.c +0 -0
  710. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/ffitarget.h +0 -0
  711. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/ppc_closure.S +0 -0
  712. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/powerpc/sysv.S +0 -0
  713. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/raw_api.c +0 -0
  714. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/riscv/ffitarget.h +0 -0
  715. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/riscv/sysv.S +0 -0
  716. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/s390/ffi.c +0 -0
  717. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/s390/ffitarget.h +0 -0
  718. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/s390/internal.h +0 -0
  719. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/s390/sysv.S +0 -0
  720. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sh/ffi.c +0 -0
  721. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sh/ffitarget.h +0 -0
  722. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sh/sysv.S +0 -0
  723. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sh64/ffi.c +0 -0
  724. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sh64/ffitarget.h +0 -0
  725. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sh64/sysv.S +0 -0
  726. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sparc/ffi.c +0 -0
  727. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sparc/ffitarget.h +0 -0
  728. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sparc/internal.h +0 -0
  729. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sparc/v8.S +0 -0
  730. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/sparc/v9.S +0 -0
  731. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/tile/ffi.c +0 -0
  732. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/tile/ffitarget.h +0 -0
  733. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/tile/tile.S +0 -0
  734. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/types.c +0 -0
  735. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/vax/elfbsd.S +0 -0
  736. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/vax/ffi.c +0 -0
  737. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/vax/ffitarget.h +0 -0
  738. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/x86/asmnames.h +0 -0
  739. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/src/x86/win64_intel.S +0 -0
  740. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/stamp-h.in +0 -0
  741. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/config/default.exp +0 -0
  742. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/lib/wrapper.exp +0 -0
  743. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.bhaible/Makefile +0 -0
  744. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.bhaible/README +0 -0
  745. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.bhaible/alignof.h +0 -0
  746. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.bhaible/bhaible.exp +0 -0
  747. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.bhaible/test-callback.c +0 -0
  748. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/align_mixed.c +0 -0
  749. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/align_stdcall.c +0 -0
  750. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/call.exp +0 -0
  751. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/err_bad_typedef.c +0 -0
  752. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/float.c +0 -0
  753. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/float1.c +0 -0
  754. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/float2.c +0 -0
  755. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/float3.c +0 -0
  756. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/float4.c +0 -0
  757. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/many.c +0 -0
  758. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/many2.c +0 -0
  759. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/many_double.c +0 -0
  760. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/many_mixed.c +0 -0
  761. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/negint.c +0 -0
  762. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/offsets.c +0 -0
  763. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/pr1172638.c +0 -0
  764. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/promotion.c +0 -0
  765. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.call/pyobjc-tc.c → ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.call/pyobjc_tc.c} +0 -0
  766. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_dbl.c +0 -0
  767. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_dbl1.c +0 -0
  768. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_dbl2.c +0 -0
  769. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_fl.c +0 -0
  770. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_fl1.c +0 -0
  771. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_fl2.c +0 -0
  772. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_fl3.c +0 -0
  773. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_ldl.c +0 -0
  774. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_ll.c +0 -0
  775. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_sc.c +0 -0
  776. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/return_uc.c +0 -0
  777. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/struct1.c +0 -0
  778. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/struct2.c +0 -0
  779. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/struct3.c +0 -0
  780. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/struct4.c +0 -0
  781. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/struct5.c +0 -0
  782. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/struct6.c +0 -0
  783. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/struct7.c +0 -0
  784. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/struct8.c +0 -0
  785. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/struct9.c +0 -0
  786. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.call/uninitialized.c +0 -0
  787. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.closures/closure.exp +0 -0
  788. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.closures/cls_double.c +0 -0
  789. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.closures/cls_many_mixed_args.c +0 -0
  790. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.closures/cls_many_mixed_float_double.c +0 -0
  791. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.closures/err_bad_abi.c +0 -0
  792. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.complex → ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.closures}/ffitest.h +0 -0
  793. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.closures/problem1.c +0 -0
  794. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.closures/stret_large.c +0 -0
  795. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.closures/stret_large2.c +0 -0
  796. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_align_complex.inc +0 -0
  797. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_align_complex_double.c +0 -0
  798. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_align_complex_float.c +0 -0
  799. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_align_complex_longdouble.c +0 -0
  800. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex.inc +0 -0
  801. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_double.c +0 -0
  802. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_float.c +0 -0
  803. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_longdouble.c +0 -0
  804. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_struct.inc +0 -0
  805. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_struct_double.c +0 -0
  806. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_struct_float.c +0 -0
  807. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_struct_longdouble.c +0 -0
  808. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_va.inc +0 -0
  809. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_va_double.c +0 -0
  810. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_va_float.c +0 -0
  811. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/cls_complex_va_longdouble.c +0 -0
  812. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/complex.exp +0 -0
  813. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/complex.inc +0 -0
  814. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/complex_defs_double.inc +0 -0
  815. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/complex_defs_float.inc +0 -0
  816. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/complex_defs_longdouble.inc +0 -0
  817. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/complex_double.c +0 -0
  818. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/complex_float.c +0 -0
  819. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/complex_int.c +0 -0
  820. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/complex_longdouble.c +0 -0
  821. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/ext/ffi_c/libffi/testsuite/libffi.go → ffi-1.16.1/ext/ffi_c/libffi/testsuite/libffi.complex}/ffitest.h +0 -0
  822. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/many_complex.inc +0 -0
  823. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/many_complex_double.c +0 -0
  824. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/many_complex_float.c +0 -0
  825. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/many_complex_longdouble.c +0 -0
  826. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex.inc +0 -0
  827. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex1.inc +0 -0
  828. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex1_double.c +0 -0
  829. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex1_float.c +0 -0
  830. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex1_longdouble.c +0 -0
  831. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex2.inc +0 -0
  832. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex2_double.c +0 -0
  833. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex2_float.c +0 -0
  834. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex2_longdouble.c +0 -0
  835. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex_double.c +0 -0
  836. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex_float.c +0 -0
  837. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.complex/return_complex_longdouble.c +0 -0
  838. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.go/aa-direct.c +0 -0
  839. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.go/closure1.c +0 -0
  840. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.go/go.exp +0 -0
  841. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi/testsuite/libffi.go/static-chain.h +0 -0
  842. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi.darwin.mk +0 -0
  843. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi.mk +0 -0
  844. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi.vc.mk +0 -0
  845. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/libffi.vc64.mk +0 -0
  846. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/ext/ffi_c/rbffi_endian.h +0 -0
  847. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/abstract_memory.rb +0 -0
  848. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/buffer.rb +0 -0
  849. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/callback.rb +0 -0
  850. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/errno.rb +0 -0
  851. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/io.rb +0 -0
  852. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/memorypointer.rb +0 -0
  853. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/aarch64-darwin/types.conf +0 -0
  854. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/aarch64-freebsd/types.conf +0 -0
  855. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/aarch64-freebsd12/types.conf +0 -0
  856. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/aarch64-linux/types.conf +0 -0
  857. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/aarch64-openbsd/types.conf +0 -0
  858. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/lib/ffi/platform/x86_64-windows → ffi-1.16.1/lib/ffi/platform/aarch64-windows}/types.conf +0 -0
  859. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/arm-freebsd/types.conf +0 -0
  860. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/arm-freebsd12/types.conf +0 -0
  861. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/arm-linux/types.conf +0 -0
  862. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/i386-cygwin/types.conf +0 -0
  863. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/i386-darwin/types.conf +0 -0
  864. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/i386-freebsd/types.conf +0 -0
  865. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/i386-freebsd12/types.conf +0 -0
  866. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/i386-gnu/types.conf +0 -0
  867. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/i386-linux/types.conf +0 -0
  868. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/i386-netbsd/types.conf +0 -0
  869. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/i386-openbsd/types.conf +0 -0
  870. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/i386-solaris/types.conf +0 -0
  871. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/i386-windows/types.conf +0 -0
  872. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/ia64-linux/types.conf +0 -0
  873. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/mips-linux/types.conf +0 -0
  874. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/mips64-linux/types.conf +0 -0
  875. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/mips64el-linux/types.conf +0 -0
  876. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/mipsel-linux/types.conf +0 -0
  877. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/mipsisa32r6-linux/types.conf +0 -0
  878. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/mipsisa32r6el-linux/types.conf +0 -0
  879. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/mipsisa64r6-linux/types.conf +0 -0
  880. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/mipsisa64r6el-linux/types.conf +0 -0
  881. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/powerpc-aix/types.conf +0 -0
  882. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/powerpc-darwin/types.conf +0 -0
  883. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/powerpc-linux/types.conf +0 -0
  884. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/powerpc-openbsd/types.conf +0 -0
  885. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/powerpc64-linux/types.conf +0 -0
  886. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/powerpc64le-linux/types.conf +0 -0
  887. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/riscv64-linux/types.conf +0 -0
  888. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/s390-linux/types.conf +0 -0
  889. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/s390x-linux/types.conf +0 -0
  890. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/sparc-linux/types.conf +0 -0
  891. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/sparc-solaris/types.conf +0 -0
  892. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5/lib/ffi/platform/sparc64-linux → ffi-1.16.1/lib/ffi/platform/sparcv9-linux}/types.conf +0 -0
  893. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/sparcv9-openbsd/types.conf +0 -0
  894. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/sparcv9-solaris/types.conf +0 -0
  895. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-cygwin/types.conf +0 -0
  896. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-darwin/types.conf +0 -0
  897. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-dragonflybsd/types.conf +0 -0
  898. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-freebsd/types.conf +0 -0
  899. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-freebsd12/types.conf +0 -0
  900. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-haiku/types.conf +0 -0
  901. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-linux/types.conf +0 -0
  902. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-msys/types.conf +0 -0
  903. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-netbsd/types.conf +0 -0
  904. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-openbsd/types.conf +0 -0
  905. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/platform/x86_64-solaris/types.conf +0 -0
  906. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/pointer.rb +0 -0
  907. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/struct_by_reference.rb +0 -0
  908. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/tools/const_generator.rb +0 -0
  909. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/tools/generator.rb +0 -0
  910. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/tools/generator_task.rb +0 -0
  911. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/tools/struct_generator.rb +0 -0
  912. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/tools/types_generator.rb +0 -0
  913. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi/union.rb +0 -0
  914. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/lib/ffi.rb +0 -0
  915. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/rakelib/ffi_gem_helper.rb +0 -0
  916. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/samples/getlogin.rb +0 -0
  917. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/samples/getpid.rb +0 -0
  918. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/samples/gettimeofday.rb +0 -0
  919. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/samples/hello.rb +0 -0
  920. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/samples/inotify.rb +0 -0
  921. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/samples/pty.rb +0 -0
  922. /data/vendor/bundle/ruby/3.2.0/gems/{ffi-1.15.5 → ffi-1.16.1}/samples/qsort.rb +0 -0
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: f678596f66026cf149c828135268f95532df4e554d62858a6d90a9a95514384c
4
- data.tar.gz: 6776cb0ce1c3e271325bfe42d36037120035f2277549f7edacc8aef8f06fb82e
3
+ metadata.gz: d84f31fcbe33fff67ac3da773b6fc620eb7099956fdb62e448ccc896a706fabb
4
+ data.tar.gz: cb0803fb7a724aa411587b0c3e7d94256d7aebfe85de98dd76d00f79502ce504
5
5
  SHA512:
6
- metadata.gz: 2408c28b51c2292e0535c37b6aa152d9019a5590e0fab3ad6e8e24353e9141acd11b7199993abf9eb6df46f62daa4e805fb8ae3a80a4e3f789d4949794eb2bb1
7
- data.tar.gz: d4b350967af241acf6ebd2461064773d9c90c1c3947134bcb5a2bff307f7c47da7e36b0d1378b5e74805a9937bbff26354e95e6100e25560d265b608e050f1d2
6
+ metadata.gz: b143932ea0f47ec035502cf2faade1e0a355589833d9d59a40cfe4e4302fe82b1f38d65772d54020b714b9704571f2d3dc8b802bf14f9fd480944ebdbe101aed
7
+ data.tar.gz: 71ce59123dc2ffa6702b365f7c4219d1edddd8cbe3666e3bb592b48e087cd21285a6ab17bab6d56882a339ec286411abd59dffd29f5498c78e048e43288f7cb9
data/Gemfile.lock CHANGED
@@ -1,7 +1,7 @@
1
1
  PATH
2
2
  remote: .
3
3
  specs:
4
- cybrid_api_id_ruby (0.94.30)
4
+ cybrid_api_id_ruby (0.94.33)
5
5
  typhoeus (~> 1.0, >= 1.0.1)
6
6
 
7
7
  GEM
@@ -13,7 +13,7 @@ GEM
13
13
  diff-lcs (1.5.0)
14
14
  ethon (0.16.0)
15
15
  ffi (>= 1.15.0)
16
- ffi (1.15.5)
16
+ ffi (1.16.1)
17
17
  jaro_winkler (1.5.6)
18
18
  method_source (1.0.0)
19
19
  parallel (1.23.0)
data/README.md CHANGED
@@ -149,8 +149,8 @@ An `Organization` can have multiple `banks`, in either `Sandbox` or `Production`
149
149
 
150
150
  This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
151
151
 
152
- - API version: v0.94.30
153
- - Package version: 0.94.30
152
+ - API version: v0.94.33
153
+ - Package version: 0.94.33
154
154
  - Build package: org.openapitools.codegen.languages.RubyClientCodegen
155
155
 
156
156
  ## Installation
@@ -166,16 +166,16 @@ gem build cybrid_api_id_ruby.gemspec
166
166
  Then either install the gem locally:
167
167
 
168
168
  ```shell
169
- gem install ./cybrid_api_id_ruby-0.94.30.gem
169
+ gem install ./cybrid_api_id_ruby-0.94.33.gem
170
170
  ```
171
171
 
172
- (for development, run `gem install --dev ./cybrid_api_id_ruby-0.94.30.gem` to install the development dependencies)
172
+ (for development, run `gem install --dev ./cybrid_api_id_ruby-0.94.33.gem` to install the development dependencies)
173
173
 
174
174
  or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
175
175
 
176
176
  Finally add this to the Gemfile:
177
177
 
178
- gem 'cybrid_api_id_ruby', '~> 0.94.30'
178
+ gem 'cybrid_api_id_ruby', '~> 0.94.33'
179
179
 
180
180
  ### Install from Git
181
181
 
@@ -5,7 +5,7 @@
5
5
 
6
6
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
7
7
 
8
- The version of the OpenAPI document: v0.94.30
8
+ The version of the OpenAPI document: v0.94.33
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.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.94.30
6
+ The version of the OpenAPI document: v0.94.33
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.94.30
6
+ The version of the OpenAPI document: v0.94.33
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.94.30
6
+ The version of the OpenAPI document: v0.94.33
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.94.30
6
+ The version of the OpenAPI document: v0.94.33
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.94.30
6
+ The version of the OpenAPI document: v0.94.33
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.94.30
6
+ The version of the OpenAPI document: v0.94.33
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.94.30
6
+ The version of the OpenAPI document: v0.94.33
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.94.30
6
+ The version of the OpenAPI document: v0.94.33
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.94.30
6
+ The version of the OpenAPI document: v0.94.33
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -3,7 +3,7 @@
3
3
 
4
4
  ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.sandbox.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.sandbox.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.sandbox.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.sandbox.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read rewards:execute rewards:read external_bank_accounts:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts:read external_wallets:read workflows:read deposit_addresses:read' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.sandbox.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.sandbox.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.sandbox.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
5
5
 
6
- The version of the OpenAPI document: v0.94.30
6
+ The version of the OpenAPI document: v0.94.33
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0