cybrid_api_id_ruby 0.129.1220 → 0.129.1222
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/Gemfile.lock +2 -2
- data/README.md +5 -5
- data/cybrid_api_id_ruby.gemspec +1 -1
- data/docs/PostCustomerTokenIdpModel.md +5 -1
- data/lib/cybrid_api_id_ruby/api/bank_applications_idp_api.rb +1 -1
- data/lib/cybrid_api_id_ruby/api/customer_tokens_idp_api.rb +1 -1
- data/lib/cybrid_api_id_ruby/api/organization_applications_idp_api.rb +1 -1
- data/lib/cybrid_api_id_ruby/api/users_idp_api.rb +1 -1
- data/lib/cybrid_api_id_ruby/api_client.rb +1 -1
- data/lib/cybrid_api_id_ruby/api_error.rb +1 -1
- data/lib/cybrid_api_id_ruby/configuration.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/application_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/application_list_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/application_with_secret_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/customer_token_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/error_response_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/patch_application_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/patch_user_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/post_bank_application_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/post_customer_token_idp_model.rb +31 -5
- data/lib/cybrid_api_id_ruby/models/post_organization_application_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/post_user_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/user_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/models/user_list_idp_model.rb +1 -1
- data/lib/cybrid_api_id_ruby/version.rb +2 -2
- data/lib/cybrid_api_id_ruby.rb +1 -1
- data/spec/api/bank_applications_idp_api_spec.rb +1 -1
- data/spec/api/customer_tokens_idp_api_spec.rb +1 -1
- data/spec/api/organization_applications_idp_api_spec.rb +1 -1
- data/spec/api/users_idp_api_spec.rb +1 -1
- data/spec/models/application_idp_model_spec.rb +1 -1
- data/spec/models/application_list_idp_model_spec.rb +1 -1
- data/spec/models/application_with_secret_idp_model_spec.rb +1 -1
- data/spec/models/customer_token_idp_model_spec.rb +1 -1
- data/spec/models/error_response_idp_model_spec.rb +1 -1
- data/spec/models/patch_application_idp_model_spec.rb +1 -1
- data/spec/models/patch_user_idp_model_spec.rb +1 -1
- data/spec/models/post_bank_application_idp_model_spec.rb +1 -1
- data/spec/models/post_customer_token_idp_model_spec.rb +13 -1
- data/spec/models/post_organization_application_idp_model_spec.rb +1 -1
- data/spec/models/post_user_idp_model_spec.rb +1 -1
- data/spec/models/user_idp_model_spec.rb +1 -1
- data/spec/models/user_list_idp_model_spec.rb +1 -1
- data/spec/spec_helper.rb +1 -1
- data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/byebug-13.0.0/gem_make.out +5 -5
- data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/date-3.5.1/gem_make.out +5 -5
- data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/io-console-0.9.4/gem_make.out +5 -5
- data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/jaro_winkler-1.5.6/gem_make.out +5 -5
- data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/psych-5.5.0/gem_make.out +5 -5
- data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/racc-1.8.1/gem_make.out +5 -5
- data/vendor/bundle/ruby/4.0.0/extensions/x86_64-linux/4.0.0/stringio-3.2.0/gem_make.out +5 -5
- metadata +1 -1
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
|
|
4
4
|
## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:read accounts:read accounts:write accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:write external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:write deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:read banks:read banks:write banks:execute bank_applications:read users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read accounts:write prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_wallets:read external_wallets:write workflows:read deposit_addresses:read deposit_addresses:write deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Bank Application | bank_applications:read (Organization, Bank) | | | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization Application | organization_applications:read (Organization) | | | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | API keys are created, updated and deleted only in the Partner Portal. Tokens issued for an organization API key can list and get organization and bank applications, and tokens issued for a bank API key can list and get bank applications; neither can create, update or delete them. Requesting the `organization_applications:write`, `organization_applications:execute`, `bank_applications:write` or `bank_applications:execute` scopes alongside other scopes is tolerated: they are dropped and the token is issued with the rest. ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Get and list bank API keys | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Get and list organization API keys | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
|
|
5
5
|
|
|
6
|
-
The version of the OpenAPI document: v0.129.
|
|
6
|
+
The version of the OpenAPI document: v0.129.1222
|
|
7
7
|
Contact: support@cybrid.app
|
|
8
8
|
Generated by: https://openapi-generator.tech
|
|
9
9
|
Generator version: 7.8.0
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
|
|
4
4
|
## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:read accounts:read accounts:write accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:write external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:write deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:read banks:read banks:write banks:execute bank_applications:read users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read accounts:write prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_wallets:read external_wallets:write workflows:read deposit_addresses:read deposit_addresses:write deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Bank Application | bank_applications:read (Organization, Bank) | | | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization Application | organization_applications:read (Organization) | | | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | API keys are created, updated and deleted only in the Partner Portal. Tokens issued for an organization API key can list and get organization and bank applications, and tokens issued for a bank API key can list and get bank applications; neither can create, update or delete them. Requesting the `organization_applications:write`, `organization_applications:execute`, `bank_applications:write` or `bank_applications:execute` scopes alongside other scopes is tolerated: they are dropped and the token is issued with the rest. ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Get and list bank API keys | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Get and list organization API keys | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
|
|
5
5
|
|
|
6
|
-
The version of the OpenAPI document: v0.129.
|
|
6
|
+
The version of the OpenAPI document: v0.129.1222
|
|
7
7
|
Contact: support@cybrid.app
|
|
8
8
|
Generated by: https://openapi-generator.tech
|
|
9
9
|
Generator version: 7.8.0
|
data/spec/spec_helper.rb
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
|
|
4
4
|
## Cybrid API documentation Welcome to Cybrid, an all-in-one crypto platform that enables you to easily **build** and **launch** white-label crypto products or services. In these documents, you'll find details on how our REST API operates and generally how our platform functions. If you're looking for our UI SDK Widgets for Web or Mobile (iOS/Android), generated API clients, or demo applications, head over to our [Github repo](https://github.com/Cybrid-app). 💡 We recommend bookmarking the [Cybrid LinkTree](https://linktr.ee/cybridtechnologies) which contains many helpful links to platform resources. ## Getting Started This is Cybrid's public interactive API documentation, which allows you to fully test our APIs. If you'd like to use a different tool to exercise our APIs, you can download the [Open API 3.0 yaml](https://bank.production.cybrid.app/api/schema/v1/swagger.yaml) for import. If you're new to our APIs and the Cybrid Platform, follow the below guides to get set up and familiar with the platform: 1. [Introduction](https://docs.cybrid.xyz/docs/introduction) 2. [Platform Overview](https://docs.cybrid.xyz/docs/platform-overview) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/hosted-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/cybrid-sandbox), we walk you through how to use the [Cybrid Sandbox](https://id.sandbox.cybrid.app/) to create a test bank and generate API keys. In [Getting Ready for Trading](https://docs.cybrid.xyz/docs/trade-process), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:read accounts:read accounts:write accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:write external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:write deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:read banks:read banks:write banks:execute bank_applications:read users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read accounts:write prices:read quotes:execute quotes:read trades:execute trades:read transactions:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_wallets:read external_wallets:write workflows:read deposit_addresses:read deposit_addresses:write deposit_bank_accounts:read deposit_bank_accounts:write deposit_bank_accounts:execute invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute sardine_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Bank Application | bank_applications:read (Organization, Bank) | | | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization Application | organization_applications:read (Organization) | | | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | API keys are created, updated and deleted only in the Partner Portal. Tokens issued for an organization API key can list and get organization and bank applications, and tokens issued for a bank API key can list and get bank applications; neither can create, update or delete them. Requesting the `organization_applications:write`, `organization_applications:execute`, `bank_applications:write` or `bank_applications:execute` scopes alongside other scopes is tolerated: they are dropped and the token is issued with the rest. ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Get and list bank API keys | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Get and list organization API keys | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer.
|
|
5
5
|
|
|
6
|
-
The version of the OpenAPI document: v0.129.
|
|
6
|
+
The version of the OpenAPI document: v0.129.1222
|
|
7
7
|
Contact: support@cybrid.app
|
|
8
8
|
Generated by: https://openapi-generator.tech
|
|
9
9
|
Generator version: 7.8.0
|
|
@@ -3,12 +3,12 @@ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vend
|
|
|
3
3
|
creating Makefile
|
|
4
4
|
|
|
5
5
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug
|
|
6
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
6
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-kvkj4o sitelibdir\=./.gem.20261003-3695-kvkj4o clean
|
|
7
7
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
|
|
8
8
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
|
|
9
9
|
|
|
10
10
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug
|
|
11
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
11
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-kvkj4o sitelibdir\=./.gem.20261003-3695-kvkj4o
|
|
12
12
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/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/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
|
|
40
40
|
|
|
41
41
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug
|
|
42
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
42
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-kvkj4o sitelibdir\=./.gem.20261003-3695-kvkj4o install
|
|
43
43
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
|
|
44
|
-
/usr/bin/install -c -m 0755 byebug.so ./.gem.
|
|
44
|
+
/usr/bin/install -c -m 0755 byebug.so ./.gem.20261003-3695-kvkj4o/byebug
|
|
45
45
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
|
|
46
46
|
|
|
47
47
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug
|
|
48
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
48
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-kvkj4o sitelibdir\=./.gem.20261003-3695-kvkj4o clean
|
|
49
49
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
|
|
50
50
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/byebug-13.0.0/ext/byebug'
|
|
@@ -6,12 +6,12 @@ checking for altzone in time.h with -Werror... no
|
|
|
6
6
|
creating Makefile
|
|
7
7
|
|
|
8
8
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date
|
|
9
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
9
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-ot9lko sitelibdir\=./.gem.20261003-3695-ot9lko clean
|
|
10
10
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
|
|
11
11
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
|
|
12
12
|
|
|
13
13
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date
|
|
14
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
14
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-ot9lko sitelibdir\=./.gem.20261003-3695-ot9lko
|
|
15
15
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
|
|
16
16
|
compiling date_core.c
|
|
17
17
|
compiling date_parse.c
|
|
@@ -21,12 +21,12 @@ linking shared-object date_core.so
|
|
|
21
21
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
|
|
22
22
|
|
|
23
23
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date
|
|
24
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
24
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-ot9lko sitelibdir\=./.gem.20261003-3695-ot9lko install
|
|
25
25
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
|
|
26
|
-
/usr/bin/install -c -m 0755 date_core.so ./.gem.
|
|
26
|
+
/usr/bin/install -c -m 0755 date_core.so ./.gem.20261003-3695-ot9lko
|
|
27
27
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
|
|
28
28
|
|
|
29
29
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date
|
|
30
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
30
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-ot9lko sitelibdir\=./.gem.20261003-3695-ot9lko clean
|
|
31
31
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
|
|
32
32
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/date-3.5.1/ext/date'
|
|
@@ -19,24 +19,24 @@ checking for gperf... no
|
|
|
19
19
|
creating Makefile
|
|
20
20
|
|
|
21
21
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console
|
|
22
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
22
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-c3ihz7 sitelibdir\=./.gem.20261003-3695-c3ihz7 clean
|
|
23
23
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console'
|
|
24
24
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console'
|
|
25
25
|
|
|
26
26
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console
|
|
27
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
27
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-c3ihz7 sitelibdir\=./.gem.20261003-3695-c3ihz7
|
|
28
28
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console'
|
|
29
29
|
compiling console.c
|
|
30
30
|
linking shared-object io/console.so
|
|
31
31
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console'
|
|
32
32
|
|
|
33
33
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console
|
|
34
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
34
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-c3ihz7 sitelibdir\=./.gem.20261003-3695-c3ihz7 install
|
|
35
35
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console'
|
|
36
|
-
/usr/bin/install -c -m 0755 console.so ./.gem.
|
|
36
|
+
/usr/bin/install -c -m 0755 console.so ./.gem.20261003-3695-c3ihz7/io
|
|
37
37
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console'
|
|
38
38
|
|
|
39
39
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console
|
|
40
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
40
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-c3ihz7 sitelibdir\=./.gem.20261003-3695-c3ihz7 clean
|
|
41
41
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console'
|
|
42
42
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/io-console-0.9.4/ext/io/console'
|
|
@@ -3,12 +3,12 @@ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vend
|
|
|
3
3
|
creating Makefile
|
|
4
4
|
|
|
5
5
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler
|
|
6
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
6
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-l7cz1c sitelibdir\=./.gem.20261003-3695-l7cz1c clean
|
|
7
7
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
|
|
8
8
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
|
|
9
9
|
|
|
10
10
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler
|
|
11
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
11
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-l7cz1c sitelibdir\=./.gem.20261003-3695-l7cz1c
|
|
12
12
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
|
|
13
13
|
compiling adj_matrix.c
|
|
14
14
|
adj_matrix.c: In function ‘adj_matrix_default’:
|
|
@@ -26,12 +26,12 @@ linking shared-object jaro_winkler/jaro_winkler_ext.so
|
|
|
26
26
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
|
|
27
27
|
|
|
28
28
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler
|
|
29
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
29
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-l7cz1c sitelibdir\=./.gem.20261003-3695-l7cz1c install
|
|
30
30
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
|
|
31
|
-
/usr/bin/install -c -m 0755 jaro_winkler_ext.so ./.gem.
|
|
31
|
+
/usr/bin/install -c -m 0755 jaro_winkler_ext.so ./.gem.20261003-3695-l7cz1c/jaro_winkler
|
|
32
32
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
|
|
33
33
|
|
|
34
34
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler
|
|
35
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
35
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-l7cz1c sitelibdir\=./.gem.20261003-3695-l7cz1c clean
|
|
36
36
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
|
|
37
37
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/jaro_winkler-1.5.6/ext/jaro_winkler'
|
|
@@ -4,7 +4,7 @@ checking for pkg-config for yaml-0.1... [" ", "", "-lyaml"]
|
|
|
4
4
|
creating Makefile
|
|
5
5
|
|
|
6
6
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych
|
|
7
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
7
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-f7xeo4 sitelibdir\=./.gem.20261003-3695-f7xeo4 clean
|
|
8
8
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
|
|
9
9
|
cd libyaml && make clean
|
|
10
10
|
/bin/sh: 1: cd: can't cd to libyaml
|
|
@@ -12,7 +12,7 @@ make[1]: [Makefile:287: clean-so] Error 2 (ignored)
|
|
|
12
12
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
|
|
13
13
|
|
|
14
14
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych
|
|
15
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
15
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-f7xeo4 sitelibdir\=./.gem.20261003-3695-f7xeo4
|
|
16
16
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
|
|
17
17
|
compiling psych.c
|
|
18
18
|
compiling psych_emitter.c
|
|
@@ -23,13 +23,13 @@ linking shared-object psych.so
|
|
|
23
23
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
|
|
24
24
|
|
|
25
25
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych
|
|
26
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
26
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-f7xeo4 sitelibdir\=./.gem.20261003-3695-f7xeo4 install
|
|
27
27
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
|
|
28
|
-
/usr/bin/install -c -m 0755 psych.so ./.gem.
|
|
28
|
+
/usr/bin/install -c -m 0755 psych.so ./.gem.20261003-3695-f7xeo4
|
|
29
29
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
|
|
30
30
|
|
|
31
31
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych
|
|
32
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
32
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-f7xeo4 sitelibdir\=./.gem.20261003-3695-f7xeo4 clean
|
|
33
33
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/psych-5.5.0/ext/psych'
|
|
34
34
|
cd libyaml && make clean
|
|
35
35
|
/bin/sh: 1: cd: can't cd to libyaml
|
|
@@ -3,24 +3,24 @@ current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vend
|
|
|
3
3
|
creating Makefile
|
|
4
4
|
|
|
5
5
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse
|
|
6
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
6
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-12xkig sitelibdir\=./.gem.20261003-3695-12xkig clean
|
|
7
7
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
|
|
8
8
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
|
|
9
9
|
|
|
10
10
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse
|
|
11
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
11
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-12xkig sitelibdir\=./.gem.20261003-3695-12xkig
|
|
12
12
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
|
|
13
13
|
compiling cparse.c
|
|
14
14
|
linking shared-object racc/cparse.so
|
|
15
15
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
|
|
16
16
|
|
|
17
17
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse
|
|
18
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
18
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-12xkig sitelibdir\=./.gem.20261003-3695-12xkig install
|
|
19
19
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
|
|
20
|
-
/usr/bin/install -c -m 0755 cparse.so ./.gem.
|
|
20
|
+
/usr/bin/install -c -m 0755 cparse.so ./.gem.20261003-3695-12xkig/racc
|
|
21
21
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
|
|
22
22
|
|
|
23
23
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse
|
|
24
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
24
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-12xkig sitelibdir\=./.gem.20261003-3695-12xkig clean
|
|
25
25
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
|
|
26
26
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/racc-1.8.1/ext/racc/cparse'
|
|
@@ -4,24 +4,24 @@ checking for rb_io_mode_t in ruby/io.h... yes
|
|
|
4
4
|
creating Makefile
|
|
5
5
|
|
|
6
6
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio
|
|
7
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
7
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-f3ibcz sitelibdir\=./.gem.20261003-3695-f3ibcz clean
|
|
8
8
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
|
|
9
9
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
|
|
10
10
|
|
|
11
11
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio
|
|
12
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
12
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-f3ibcz sitelibdir\=./.gem.20261003-3695-f3ibcz
|
|
13
13
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
|
|
14
14
|
compiling stringio.c
|
|
15
15
|
linking shared-object stringio.so
|
|
16
16
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
|
|
17
17
|
|
|
18
18
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio
|
|
19
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
19
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-f3ibcz sitelibdir\=./.gem.20261003-3695-f3ibcz install
|
|
20
20
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
|
|
21
|
-
/usr/bin/install -c -m 0755 stringio.so ./.gem.
|
|
21
|
+
/usr/bin/install -c -m 0755 stringio.so ./.gem.20261003-3695-f3ibcz
|
|
22
22
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
|
|
23
23
|
|
|
24
24
|
current directory: /home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio
|
|
25
|
-
make DESTDIR\= sitearchdir\=./.gem.
|
|
25
|
+
make DESTDIR\= sitearchdir\=./.gem.20261003-3695-f3ibcz sitelibdir\=./.gem.20261003-3695-f3ibcz clean
|
|
26
26
|
make[1]: Entering directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
|
|
27
27
|
make[1]: Leaving directory '/home/circleci/project/build/public-clients/api-idp/ruby/vendor/bundle/ruby/4.0.0/gems/stringio-3.2.0/ext/stringio'
|