cybrid_api_id_ruby 0.68.91 → 0.69.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (65) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +2 -2
  3. data/README.md +9 -7
  4. data/cybrid_api_id_ruby.gemspec +2 -2
  5. data/lib/cybrid_api_id_ruby/api/bank_applications_idp_api.rb +2 -2
  6. data/lib/cybrid_api_id_ruby/api/customer_tokens_idp_api.rb +2 -2
  7. data/lib/cybrid_api_id_ruby/api/organization_applications_idp_api.rb +2 -2
  8. data/lib/cybrid_api_id_ruby/api_client.rb +2 -2
  9. data/lib/cybrid_api_id_ruby/api_error.rb +2 -2
  10. data/lib/cybrid_api_id_ruby/configuration.rb +2 -2
  11. data/lib/cybrid_api_id_ruby/models/application_idp_model.rb +2 -2
  12. data/lib/cybrid_api_id_ruby/models/application_list_idp_model.rb +2 -2
  13. data/lib/cybrid_api_id_ruby/models/application_with_secret_all_of_idp_model.rb +2 -2
  14. data/lib/cybrid_api_id_ruby/models/application_with_secret_idp_model.rb +2 -2
  15. data/lib/cybrid_api_id_ruby/models/customer_token_idp_model.rb +2 -2
  16. data/lib/cybrid_api_id_ruby/models/post_bank_application_idp_model.rb +2 -2
  17. data/lib/cybrid_api_id_ruby/models/post_customer_token_idp_model.rb +2 -2
  18. data/lib/cybrid_api_id_ruby/models/post_organization_application_idp_model.rb +2 -2
  19. data/lib/cybrid_api_id_ruby/version.rb +3 -3
  20. data/lib/cybrid_api_id_ruby.rb +2 -2
  21. data/spec/api/bank_applications_idp_api_spec.rb +2 -2
  22. data/spec/api/customer_tokens_idp_api_spec.rb +2 -2
  23. data/spec/api/organization_applications_idp_api_spec.rb +2 -2
  24. data/spec/api_client_spec.rb +2 -2
  25. data/spec/configuration_spec.rb +2 -2
  26. data/spec/models/application_idp_model_spec.rb +3 -3
  27. data/spec/models/application_list_idp_model_spec.rb +2 -2
  28. data/spec/models/application_with_secret_all_of_idp_model_spec.rb +2 -2
  29. data/spec/models/application_with_secret_idp_model_spec.rb +3 -3
  30. data/spec/models/customer_token_idp_model_spec.rb +2 -2
  31. data/spec/models/post_bank_application_idp_model_spec.rb +2 -2
  32. data/spec/models/post_customer_token_idp_model_spec.rb +3 -3
  33. data/spec/models/post_organization_application_idp_model_spec.rb +2 -2
  34. data/spec/spec_helper.rb +2 -2
  35. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/byebug-11.1.3/gem_make.out +6 -6
  36. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/ffi-1.15.5/gem_make.out +6 -6
  37. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/jaro_winkler-1.5.4/gem_make.out +6 -6
  38. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/psych-5.1.0/gem_make.out +6 -6
  39. data/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0/stringio-3.0.6/gem_make.out +6 -6
  40. data/vendor/bundle/ruby/3.2.0/specifications/ast-2.4.2.gemspec +2 -2
  41. data/vendor/bundle/ruby/3.2.0/specifications/byebug-11.1.3.gemspec +2 -2
  42. data/vendor/bundle/ruby/3.2.0/specifications/coderay-1.1.3.gemspec +2 -2
  43. data/vendor/bundle/ruby/3.2.0/specifications/diff-lcs-1.5.0.gemspec +2 -2
  44. data/vendor/bundle/ruby/3.2.0/specifications/ethon-0.16.0.gemspec +2 -2
  45. data/vendor/bundle/ruby/3.2.0/specifications/ffi-1.15.5.gemspec +2 -2
  46. data/vendor/bundle/ruby/3.2.0/specifications/jaro_winkler-1.5.4.gemspec +2 -2
  47. data/vendor/bundle/ruby/3.2.0/specifications/method_source-1.0.0.gemspec +2 -2
  48. data/vendor/bundle/ruby/3.2.0/specifications/parallel-1.23.0.gemspec +2 -2
  49. data/vendor/bundle/ruby/3.2.0/specifications/parser-3.2.2.1.gemspec +2 -2
  50. data/vendor/bundle/ruby/3.2.0/specifications/pry-0.14.2.gemspec +2 -2
  51. data/vendor/bundle/ruby/3.2.0/specifications/pry-byebug-3.10.1.gemspec +2 -2
  52. data/vendor/bundle/ruby/3.2.0/specifications/psych-5.1.0.gemspec +2 -2
  53. data/vendor/bundle/ruby/3.2.0/specifications/rainbow-3.1.1.gemspec +2 -2
  54. data/vendor/bundle/ruby/3.2.0/specifications/rake-13.0.6.gemspec +2 -2
  55. data/vendor/bundle/ruby/3.2.0/specifications/rspec-3.12.0.gemspec +2 -2
  56. data/vendor/bundle/ruby/3.2.0/specifications/rspec-core-3.12.2.gemspec +2 -2
  57. data/vendor/bundle/ruby/3.2.0/specifications/rspec-expectations-3.12.3.gemspec +2 -2
  58. data/vendor/bundle/ruby/3.2.0/specifications/rspec-mocks-3.12.5.gemspec +2 -2
  59. data/vendor/bundle/ruby/3.2.0/specifications/rspec-support-3.12.0.gemspec +2 -2
  60. data/vendor/bundle/ruby/3.2.0/specifications/rubocop-0.66.0.gemspec +2 -2
  61. data/vendor/bundle/ruby/3.2.0/specifications/ruby-progressbar-1.13.0.gemspec +2 -2
  62. data/vendor/bundle/ruby/3.2.0/specifications/stringio-3.0.6.gemspec +2 -2
  63. data/vendor/bundle/ruby/3.2.0/specifications/typhoeus-1.4.0.gemspec +2 -2
  64. data/vendor/bundle/ruby/3.2.0/specifications/unicode-display_width-1.5.0.gemspec +2 -2
  65. metadata +2 -2
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #Cybrid Identity API
3
3
 
4
- ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), 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://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.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 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 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 banks:read banks:write banks:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts: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) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Reward | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | 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 | | 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 | BankVerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | 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 | 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 | Reward | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
4
+ ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), 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://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.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 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 banks:read banks:write banks: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) | | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Reward | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | 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 | | 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 | BankVerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | 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 | Reward | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | 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.68.91
6
+ The version of the OpenAPI document: v0.69.1
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
data/spec/spec_helper.rb CHANGED
@@ -1,9 +1,9 @@
1
1
  =begin
2
2
  #Cybrid Identity API
3
3
 
4
- ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), 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://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.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 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 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 banks:read banks:write banks:execute customers:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:execute external_bank_accounts: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) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Reward | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | 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 | | 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 | BankVerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | 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 | 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 | Reward | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
4
+ ## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.sandbox.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Understanding the Platform](https://kb.cybrid.xyz/understanding-the-platform) 2. [Getting Started in the Cybrid Sandbox](https://kb.cybrid.xyz/getting-started-guide) 3. [Getting Ready for Trading](https://kb.cybrid.xyz/getting-ready-for-trading) 4. [Running the Web Demo App](https://kb.cybrid.xyz/locally-running-the-web-demo-app) (or, alternatively, [Testing with Hosted Web Demo App](https://kb.cybrid.xyz/testing-with-hosted-web-demo-app)) In [Getting Started in the Cybrid Sandbox](https://www.cybrid.xyz/guides/getting-started), 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://www.cybrid.xyz/guides/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. If you've already run through the first two guides, you can follow the [Running the Web Demo App](https://www.cybrid.xyz/guides/running-the-cybrid-web-demo-crypto-app) guide to test our web SDK with your sandbox `bank` and `customer`. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.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 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 banks:read banks:write banks: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) | | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Reward | rewards:read (Bank, Customer) | | rewards:execute (Bank) | | 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 | | 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 | BankVerificationKey | /api/bank_verification_keys | Create, list and retrive verification keys, used for signing identities | | 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 | Reward | /api/rewards | Create a new reward (automates quote/trade for simplicity) | | 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.68.91
6
+ The version of the OpenAPI document: v0.69.1
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 6.0.0
@@ -1,14 +1,14 @@
1
1
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug
2
- /usr/local/bin/ruby -I /usr/local/lib/ruby/site_ruby/3.2.0 extconf.rb
2
+ /usr/local/bin/ruby extconf.rb
3
3
  creating Makefile
4
4
 
5
5
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug
6
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-ol4slr sitelibdir\=./.gem.20230508-3966-ol4slr clean
6
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-m78k6h sitelibdir\=./.gem.20230508-4001-m78k6h clean
7
7
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug'
8
8
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug'
9
9
 
10
10
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug
11
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-ol4slr sitelibdir\=./.gem.20230508-3966-ol4slr
11
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-m78k6h sitelibdir\=./.gem.20230508-4001-m78k6h
12
12
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug'
13
13
  compiling breakpoint.c
14
14
  compiling byebug.c
@@ -39,12 +39,12 @@ linking shared-object byebug/byebug.so
39
39
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug'
40
40
 
41
41
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug
42
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-ol4slr sitelibdir\=./.gem.20230508-3966-ol4slr install
42
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-m78k6h sitelibdir\=./.gem.20230508-4001-m78k6h install
43
43
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug'
44
- /usr/bin/install -c -m 0755 byebug.so ./.gem.20230508-3966-ol4slr/byebug
44
+ /usr/bin/install -c -m 0755 byebug.so ./.gem.20230508-4001-m78k6h/byebug
45
45
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug'
46
46
 
47
47
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug
48
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-ol4slr sitelibdir\=./.gem.20230508-3966-ol4slr clean
48
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-m78k6h sitelibdir\=./.gem.20230508-4001-m78k6h clean
49
49
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug'
50
50
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/byebug-11.1.3/ext/byebug'
@@ -1,5 +1,5 @@
1
1
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c
2
- /usr/local/bin/ruby -I /usr/local/lib/ruby/site_ruby/3.2.0 extconf.rb
2
+ /usr/local/bin/ruby extconf.rb
3
3
  checking for ffi_prep_closure_loc() in -lffi... yes
4
4
  checking for ffi_prep_cif_var()... yes
5
5
  checking for ffi_raw_call()... yes
@@ -9,12 +9,12 @@ creating extconf.h
9
9
  creating Makefile
10
10
 
11
11
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c
12
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-7sylm3 sitelibdir\=./.gem.20230508-3966-7sylm3 clean
12
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-swo9w8 sitelibdir\=./.gem.20230508-4001-swo9w8 clean
13
13
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c'
14
14
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c'
15
15
 
16
16
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c
17
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-7sylm3 sitelibdir\=./.gem.20230508-3966-7sylm3
17
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-swo9w8 sitelibdir\=./.gem.20230508-4001-swo9w8
18
18
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c'
19
19
  compiling AbstractMemory.c
20
20
  compiling ArrayType.c
@@ -43,12 +43,12 @@ linking shared-object ffi_c.so
43
43
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c'
44
44
 
45
45
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c
46
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-7sylm3 sitelibdir\=./.gem.20230508-3966-7sylm3 install
46
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-swo9w8 sitelibdir\=./.gem.20230508-4001-swo9w8 install
47
47
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c'
48
- /usr/bin/install -c -m 0755 ffi_c.so ./.gem.20230508-3966-7sylm3
48
+ /usr/bin/install -c -m 0755 ffi_c.so ./.gem.20230508-4001-swo9w8
49
49
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c'
50
50
 
51
51
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c
52
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-7sylm3 sitelibdir\=./.gem.20230508-3966-7sylm3 clean
52
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-swo9w8 sitelibdir\=./.gem.20230508-4001-swo9w8 clean
53
53
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c'
54
54
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/ffi-1.15.5/ext/ffi_c'
@@ -1,14 +1,14 @@
1
1
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
2
- /usr/local/bin/ruby -I /usr/local/lib/ruby/site_ruby/3.2.0 extconf.rb
2
+ /usr/local/bin/ruby extconf.rb
3
3
  creating Makefile
4
4
 
5
5
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
6
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-onxto5 sitelibdir\=./.gem.20230508-3966-onxto5 clean
6
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-7h33oa sitelibdir\=./.gem.20230508-4001-7h33oa clean
7
7
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
8
8
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
9
9
 
10
10
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
11
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-onxto5 sitelibdir\=./.gem.20230508-3966-onxto5
11
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-7h33oa sitelibdir\=./.gem.20230508-4001-7h33oa
12
12
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
13
13
  compiling adj_matrix.c
14
14
  adj_matrix.c: In function ‘adj_matrix_default’:
@@ -63,12 +63,12 @@ linking shared-object jaro_winkler/jaro_winkler_ext.so
63
63
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
64
64
 
65
65
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
66
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-onxto5 sitelibdir\=./.gem.20230508-3966-onxto5 install
66
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-7h33oa sitelibdir\=./.gem.20230508-4001-7h33oa install
67
67
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
68
- /usr/bin/install -c -m 0755 jaro_winkler_ext.so ./.gem.20230508-3966-onxto5/jaro_winkler
68
+ /usr/bin/install -c -m 0755 jaro_winkler_ext.so ./.gem.20230508-4001-7h33oa/jaro_winkler
69
69
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
70
70
 
71
71
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler
72
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-onxto5 sitelibdir\=./.gem.20230508-3966-onxto5 clean
72
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-7h33oa sitelibdir\=./.gem.20230508-4001-7h33oa clean
73
73
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
74
74
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/jaro_winkler-1.5.4/ext/jaro_winkler'
@@ -1,11 +1,11 @@
1
1
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych
2
- /usr/local/bin/ruby -I /usr/local/lib/ruby/site_ruby/3.2.0 extconf.rb
2
+ /usr/local/bin/ruby extconf.rb
3
3
  checking for yaml.h... yes
4
4
  checking for yaml_get_version() in -lyaml... yes
5
5
  creating Makefile
6
6
 
7
7
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych
8
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-l5l84z sitelibdir\=./.gem.20230508-3966-l5l84z clean
8
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-hejwse sitelibdir\=./.gem.20230508-4001-hejwse clean
9
9
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych'
10
10
  cd libyaml && make clean
11
11
  /bin/sh: 1: cd: can't cd to libyaml
@@ -13,7 +13,7 @@ make[1]: [Makefile:283: clean-so] Error 2 (ignored)
13
13
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych'
14
14
 
15
15
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych
16
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-l5l84z sitelibdir\=./.gem.20230508-3966-l5l84z
16
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-hejwse sitelibdir\=./.gem.20230508-4001-hejwse
17
17
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych'
18
18
  compiling psych.c
19
19
  compiling psych_emitter.c
@@ -24,13 +24,13 @@ linking shared-object psych.so
24
24
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych'
25
25
 
26
26
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych
27
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-l5l84z sitelibdir\=./.gem.20230508-3966-l5l84z install
27
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-hejwse sitelibdir\=./.gem.20230508-4001-hejwse install
28
28
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych'
29
- /usr/bin/install -c -m 0755 psych.so ./.gem.20230508-3966-l5l84z
29
+ /usr/bin/install -c -m 0755 psych.so ./.gem.20230508-4001-hejwse
30
30
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych'
31
31
 
32
32
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych
33
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-l5l84z sitelibdir\=./.gem.20230508-3966-l5l84z clean
33
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-hejwse sitelibdir\=./.gem.20230508-4001-hejwse clean
34
34
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/psych-5.1.0/ext/psych'
35
35
  cd libyaml && make clean
36
36
  /bin/sh: 1: cd: can't cd to libyaml
@@ -1,27 +1,27 @@
1
1
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio
2
- /usr/local/bin/ruby -I /usr/local/lib/ruby/site_ruby/3.2.0 extconf.rb
2
+ /usr/local/bin/ruby extconf.rb
3
3
  checking for rb_io_extract_modeenc() in ruby/io.h... yes
4
4
  creating Makefile
5
5
 
6
6
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio
7
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-ibjae8 sitelibdir\=./.gem.20230508-3966-ibjae8 clean
7
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-i8s9ih sitelibdir\=./.gem.20230508-4001-i8s9ih clean
8
8
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio'
9
9
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio'
10
10
 
11
11
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio
12
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-ibjae8 sitelibdir\=./.gem.20230508-3966-ibjae8
12
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-i8s9ih sitelibdir\=./.gem.20230508-4001-i8s9ih
13
13
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio'
14
14
  compiling stringio.c
15
15
  linking shared-object stringio.so
16
16
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio'
17
17
 
18
18
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio
19
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-ibjae8 sitelibdir\=./.gem.20230508-3966-ibjae8 install
19
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-i8s9ih sitelibdir\=./.gem.20230508-4001-i8s9ih install
20
20
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio'
21
- /usr/bin/install -c -m 0755 stringio.so ./.gem.20230508-3966-ibjae8
21
+ /usr/bin/install -c -m 0755 stringio.so ./.gem.20230508-4001-i8s9ih
22
22
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio'
23
23
 
24
24
  current directory: /home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio
25
- make DESTDIR\= sitearchdir\=./.gem.20230508-3966-ibjae8 sitelibdir\=./.gem.20230508-3966-ibjae8 clean
25
+ make DESTDIR\= sitearchdir\=./.gem.20230508-4001-i8s9ih sitelibdir\=./.gem.20230508-4001-i8s9ih clean
26
26
  make[1]: Entering directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio'
27
27
  make[1]: Leaving directory '/home/circleci/project/api-service-clients/api-idp/ruby/vendor/bundle/ruby/3.2.0/gems/stringio-3.0.6/ext/stringio'
@@ -13,10 +13,10 @@ Gem::Specification.new do |s|
13
13
  s.email = ["whitequark@whitequark.org".freeze]
14
14
  s.homepage = "https://whitequark.github.io/ast/".freeze
15
15
  s.licenses = ["MIT".freeze]
16
- s.rubygems_version = "3.4.7".freeze
16
+ s.rubygems_version = "3.4.12".freeze
17
17
  s.summary = "A library for working with Abstract Syntax Trees.".freeze
18
18
 
19
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
19
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
20
20
 
21
21
  s.specification_version = 4
22
22
 
@@ -20,10 +20,10 @@ Gem::Specification.new do |s|
20
20
  s.homepage = "https://github.com/deivid-rodriguez/byebug".freeze
21
21
  s.licenses = ["BSD-2-Clause".freeze]
22
22
  s.required_ruby_version = Gem::Requirement.new(">= 2.4.0".freeze)
23
- s.rubygems_version = "3.4.7".freeze
23
+ s.rubygems_version = "3.4.12".freeze
24
24
  s.summary = "Ruby fast debugger - base + CLI".freeze
25
25
 
26
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
26
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
27
27
 
28
28
  s.specification_version = 4
29
29
 
@@ -18,8 +18,8 @@ Gem::Specification.new do |s|
18
18
  s.licenses = ["MIT".freeze]
19
19
  s.rdoc_options = ["-SNw2".freeze, "-mREADME_INDEX.rdoc".freeze, "-t CodeRay Documentation".freeze]
20
20
  s.required_ruby_version = Gem::Requirement.new(">= 1.8.6".freeze)
21
- s.rubygems_version = "3.4.7".freeze
21
+ s.rubygems_version = "3.4.12".freeze
22
22
  s.summary = "Fast syntax highlighting for selected languages.".freeze
23
23
 
24
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
24
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
25
25
  end
@@ -19,10 +19,10 @@ Gem::Specification.new do |s|
19
19
  s.licenses = ["MIT".freeze, "Artistic-2.0".freeze, "GPL-2.0+".freeze]
20
20
  s.rdoc_options = ["--main".freeze, "README.rdoc".freeze]
21
21
  s.required_ruby_version = Gem::Requirement.new(">= 1.8".freeze)
22
- s.rubygems_version = "3.4.7".freeze
22
+ s.rubygems_version = "3.4.12".freeze
23
23
  s.summary = "Diff::LCS computes the difference between two Enumerable sequences using the McIlroy-Hunt longest common subsequence (LCS) algorithm".freeze
24
24
 
25
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
25
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
26
26
 
27
27
  s.specification_version = 4
28
28
 
@@ -13,10 +13,10 @@ Gem::Specification.new do |s|
13
13
  s.email = ["me@hans.io".freeze]
14
14
  s.homepage = "https://github.com/typhoeus/ethon".freeze
15
15
  s.licenses = ["MIT".freeze]
16
- s.rubygems_version = "3.4.7".freeze
16
+ s.rubygems_version = "3.4.12".freeze
17
17
  s.summary = "Libcurl wrapper.".freeze
18
18
 
19
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
19
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
20
20
 
21
21
  s.specification_version = 4
22
22
 
@@ -19,10 +19,10 @@ Gem::Specification.new do |s|
19
19
  s.licenses = ["BSD-3-Clause".freeze]
20
20
  s.rdoc_options = ["--exclude=ext/ffi_c/.*\\.o$".freeze, "--exclude=ffi_c\\.(bundle|so)$".freeze]
21
21
  s.required_ruby_version = Gem::Requirement.new(">= 2.3".freeze)
22
- s.rubygems_version = "3.4.7".freeze
22
+ s.rubygems_version = "3.4.12".freeze
23
23
  s.summary = "Ruby FFI".freeze
24
24
 
25
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
25
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
26
26
 
27
27
  s.specification_version = 4
28
28
 
@@ -16,10 +16,10 @@ Gem::Specification.new do |s|
16
16
  s.files = ["ext/jaro_winkler/extconf.rb".freeze]
17
17
  s.homepage = "https://github.com/tonytonyjan/jaro_winkler".freeze
18
18
  s.licenses = ["MIT".freeze]
19
- s.rubygems_version = "3.4.7".freeze
19
+ s.rubygems_version = "3.4.12".freeze
20
20
  s.summary = "An implementation of Jaro-Winkler distance algorithm written \\ in C extension which supports any kind of string encoding.".freeze
21
21
 
22
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
22
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
23
23
 
24
24
  s.specification_version = 4
25
25
 
@@ -13,10 +13,10 @@ Gem::Specification.new do |s|
13
13
  s.email = "jrmair@gmail.com".freeze
14
14
  s.homepage = "http://banisterfiend.wordpress.com".freeze
15
15
  s.licenses = ["MIT".freeze]
16
- s.rubygems_version = "3.4.7".freeze
16
+ s.rubygems_version = "3.4.12".freeze
17
17
  s.summary = "retrieve the sourcecode for a method".freeze
18
18
 
19
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
19
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
20
20
 
21
21
  s.specification_version = 4
22
22
 
@@ -14,8 +14,8 @@ Gem::Specification.new do |s|
14
14
  s.homepage = "https://github.com/grosser/parallel".freeze
15
15
  s.licenses = ["MIT".freeze]
16
16
  s.required_ruby_version = Gem::Requirement.new(">= 2.5".freeze)
17
- s.rubygems_version = "3.4.7".freeze
17
+ s.rubygems_version = "3.4.12".freeze
18
18
  s.summary = "Run any kind of code in parallel processes".freeze
19
19
 
20
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
20
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
21
21
  end
@@ -17,10 +17,10 @@ Gem::Specification.new do |s|
17
17
  s.homepage = "https://github.com/whitequark/parser".freeze
18
18
  s.licenses = ["MIT".freeze]
19
19
  s.required_ruby_version = Gem::Requirement.new(">= 2.0.0".freeze)
20
- s.rubygems_version = "3.4.7".freeze
20
+ s.rubygems_version = "3.4.12".freeze
21
21
  s.summary = "A Ruby parser written in pure Ruby.".freeze
22
22
 
23
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
23
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
24
24
 
25
25
  s.specification_version = 4
26
26
 
@@ -17,10 +17,10 @@ Gem::Specification.new do |s|
17
17
  s.homepage = "http://pry.github.io".freeze
18
18
  s.licenses = ["MIT".freeze]
19
19
  s.required_ruby_version = Gem::Requirement.new(">= 2.0".freeze)
20
- s.rubygems_version = "3.4.7".freeze
20
+ s.rubygems_version = "3.4.12".freeze
21
21
  s.summary = "A runtime developer console and IRB alternative with powerful introspection capabilities.".freeze
22
22
 
23
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
23
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
24
24
 
25
25
  s.specification_version = 4
26
26
 
@@ -16,10 +16,10 @@ Gem::Specification.new do |s|
16
16
  s.homepage = "https://github.com/deivid-rodriguez/pry-byebug".freeze
17
17
  s.licenses = ["MIT".freeze]
18
18
  s.required_ruby_version = Gem::Requirement.new(">= 2.7.0".freeze)
19
- s.rubygems_version = "3.4.7".freeze
19
+ s.rubygems_version = "3.4.12".freeze
20
20
  s.summary = "Fast debugging with Pry.".freeze
21
21
 
22
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
22
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
23
23
 
24
24
  s.specification_version = 4
25
25
 
@@ -20,10 +20,10 @@ Gem::Specification.new do |s|
20
20
  s.licenses = ["MIT".freeze]
21
21
  s.rdoc_options = ["--main".freeze, "README.md".freeze]
22
22
  s.required_ruby_version = Gem::Requirement.new(">= 2.4.0".freeze)
23
- s.rubygems_version = "3.4.7".freeze
23
+ s.rubygems_version = "3.4.12".freeze
24
24
  s.summary = "Psych is a YAML parser and emitter".freeze
25
25
 
26
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
26
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
27
27
 
28
28
  s.specification_version = 4
29
29
 
@@ -14,10 +14,10 @@ Gem::Specification.new do |s|
14
14
  s.homepage = "https://github.com/sickill/rainbow".freeze
15
15
  s.licenses = ["MIT".freeze]
16
16
  s.required_ruby_version = Gem::Requirement.new(">= 2.3.0".freeze)
17
- s.rubygems_version = "3.4.7".freeze
17
+ s.rubygems_version = "3.4.12".freeze
18
18
  s.summary = "Colorize printed text on ANSI terminals".freeze
19
19
 
20
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
20
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
21
21
 
22
22
  s.specification_version = 4
23
23
 
@@ -19,8 +19,8 @@ Gem::Specification.new do |s|
19
19
  s.licenses = ["MIT".freeze]
20
20
  s.rdoc_options = ["--main".freeze, "README.rdoc".freeze]
21
21
  s.required_ruby_version = Gem::Requirement.new(">= 2.2".freeze)
22
- s.rubygems_version = "3.4.7".freeze
22
+ s.rubygems_version = "3.4.12".freeze
23
23
  s.summary = "Rake is a Make-like program implemented in Ruby".freeze
24
24
 
25
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
25
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
26
26
  end
@@ -18,10 +18,10 @@ Gem::Specification.new do |s|
18
18
  s.homepage = "http://github.com/rspec".freeze
19
19
  s.licenses = ["MIT".freeze]
20
20
  s.rdoc_options = ["--charset=UTF-8".freeze]
21
- s.rubygems_version = "3.4.7".freeze
21
+ s.rubygems_version = "3.4.12".freeze
22
22
  s.summary = "rspec-3.12.0".freeze
23
23
 
24
- s.installed_by_version = "3.4.7" if s.respond_to? :installed_by_version
24
+ s.installed_by_version = "3.4.12" if s.respond_to? :installed_by_version
25
25
 
26
26
  s.specification_version = 4
27
27