cybrid-api-bank-python 0.123.287__py3-none-any.whl → 0.125.156__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (209) hide show
  1. cybrid_api_bank/__init__.py +2 -2
  2. cybrid_api_bank/api/accounts_bank_api.py +3 -3
  3. cybrid_api_bank/api/assets_bank_api.py +2 -2
  4. cybrid_api_bank/api/banks_bank_api.py +3 -3
  5. cybrid_api_bank/api/counterparties_bank_api.py +5 -5
  6. cybrid_api_bank/api/customers_bank_api.py +5 -5
  7. cybrid_api_bank/api/deposit_addresses_bank_api.py +3 -3
  8. cybrid_api_bank/api/deposit_bank_accounts_bank_api.py +3 -3
  9. cybrid_api_bank/api/executions_bank_api.py +312 -0
  10. cybrid_api_bank/api/external_bank_accounts_bank_api.py +11 -5
  11. cybrid_api_bank/api/external_wallets_bank_api.py +10 -4
  12. cybrid_api_bank/api/files_bank_api.py +10 -4
  13. cybrid_api_bank/api/identity_verifications_bank_api.py +17 -5
  14. cybrid_api_bank/api/invoices_bank_api.py +3 -3
  15. cybrid_api_bank/api/payment_instructions_bank_api.py +3 -3
  16. cybrid_api_bank/api/persona_sessions_bank_api.py +177 -0
  17. cybrid_api_bank/api/plans_bank_api.py +312 -0
  18. cybrid_api_bank/api/prices_bank_api.py +2 -2
  19. cybrid_api_bank/api/quotes_bank_api.py +3 -3
  20. cybrid_api_bank/api/symbols_bank_api.py +2 -2
  21. cybrid_api_bank/api/trades_bank_api.py +4 -4
  22. cybrid_api_bank/api/transfers_bank_api.py +151 -4
  23. cybrid_api_bank/api/workflows_bank_api.py +3 -3
  24. cybrid_api_bank/api_client.py +2 -2
  25. cybrid_api_bank/apis/__init__.py +3 -0
  26. cybrid_api_bank/configuration.py +3 -3
  27. cybrid_api_bank/exceptions.py +2 -2
  28. cybrid_api_bank/model/account.py +3 -3
  29. cybrid_api_bank/model/account_association.py +322 -0
  30. cybrid_api_bank/model/account_list.py +2 -2
  31. cybrid_api_bank/model/account_state.py +2 -2
  32. cybrid_api_bank/model/account_type.py +2 -2
  33. cybrid_api_bank/model/activity_limit.py +13 -5
  34. cybrid_api_bank/model/activity_side.py +291 -0
  35. cybrid_api_bank/model/activity_type.py +6 -6
  36. cybrid_api_bank/model/asset.py +4 -4
  37. cybrid_api_bank/model/asset_list.py +2 -2
  38. cybrid_api_bank/model/asset_types.py +2 -2
  39. cybrid_api_bank/model/bank.py +2 -2
  40. cybrid_api_bank/model/bank_feature.py +2 -2
  41. cybrid_api_bank/model/bank_list.py +2 -2
  42. cybrid_api_bank/model/bank_supported_payout_symbols_inner.py +2 -2
  43. cybrid_api_bank/model/bank_type.py +2 -2
  44. cybrid_api_bank/model/compliance_check.py +4 -4
  45. cybrid_api_bank/model/compliance_check_outcome.py +7 -6
  46. cybrid_api_bank/model/compliance_check_type.py +2 -2
  47. cybrid_api_bank/model/compliance_decision.py +6 -2
  48. cybrid_api_bank/model/compliance_decision_state.py +2 -2
  49. cybrid_api_bank/model/compliance_decision_type.py +2 -2
  50. cybrid_api_bank/model/counterparty.py +2 -2
  51. cybrid_api_bank/model/counterparty_address.py +2 -2
  52. cybrid_api_bank/model/counterparty_aliases_inner.py +2 -2
  53. cybrid_api_bank/model/counterparty_list.py +2 -2
  54. cybrid_api_bank/model/counterparty_name.py +2 -2
  55. cybrid_api_bank/model/counterparty_state.py +2 -2
  56. cybrid_api_bank/model/counterparty_type.py +2 -2
  57. cybrid_api_bank/model/customer.py +2 -2
  58. cybrid_api_bank/model/customer_address.py +2 -2
  59. cybrid_api_bank/model/customer_aliases_inner.py +2 -2
  60. cybrid_api_bank/model/customer_list.py +2 -2
  61. cybrid_api_bank/model/customer_name.py +2 -2
  62. cybrid_api_bank/model/customer_state.py +2 -2
  63. cybrid_api_bank/model/customer_type.py +2 -2
  64. cybrid_api_bank/model/deposit_address.py +2 -2
  65. cybrid_api_bank/model/deposit_address_format.py +2 -2
  66. cybrid_api_bank/model/deposit_address_list.py +2 -2
  67. cybrid_api_bank/model/deposit_address_state.py +2 -2
  68. cybrid_api_bank/model/deposit_bank_account.py +6 -2
  69. cybrid_api_bank/model/deposit_bank_account_account_details_inner.py +2 -2
  70. cybrid_api_bank/model/deposit_bank_account_counterparty_address.py +2 -2
  71. cybrid_api_bank/model/deposit_bank_account_list.py +2 -2
  72. cybrid_api_bank/model/deposit_bank_account_routing_details_inner.py +2 -2
  73. cybrid_api_bank/model/deposit_bank_account_routing_number_type.py +2 -2
  74. cybrid_api_bank/model/deposit_bank_account_state.py +2 -2
  75. cybrid_api_bank/model/error_response.py +2 -2
  76. cybrid_api_bank/model/execution.py +370 -0
  77. cybrid_api_bank/model/execution_travel_rule_info.py +290 -0
  78. cybrid_api_bank/model/external_bank_account.py +11 -3
  79. cybrid_api_bank/model/external_bank_account_balances.py +2 -2
  80. cybrid_api_bank/model/external_bank_account_kind.py +2 -2
  81. cybrid_api_bank/model/external_bank_account_list.py +2 -2
  82. cybrid_api_bank/model/external_bank_account_pii_inner.py +2 -2
  83. cybrid_api_bank/model/external_bank_account_pii_inner_addresses_inner.py +2 -2
  84. cybrid_api_bank/model/external_bank_account_pii_inner_routing_details_inner.py +2 -2
  85. cybrid_api_bank/model/external_bank_account_state.py +2 -2
  86. cybrid_api_bank/model/external_wallet.py +12 -4
  87. cybrid_api_bank/model/external_wallet_environment.py +2 -2
  88. cybrid_api_bank/model/external_wallet_list.py +2 -2
  89. cybrid_api_bank/model/external_wallet_state.py +2 -2
  90. cybrid_api_bank/model/fee_association.py +286 -0
  91. cybrid_api_bank/model/identification_number.py +4 -4
  92. cybrid_api_bank/model/identity_verification.py +10 -4
  93. cybrid_api_bank/model/identity_verification_business_associate.py +288 -0
  94. cybrid_api_bank/model/identity_verification_document.py +290 -0
  95. cybrid_api_bank/model/identity_verification_document_file.py +280 -0
  96. cybrid_api_bank/model/identity_verification_list.py +2 -2
  97. cybrid_api_bank/model/identity_verification_method.py +7 -6
  98. cybrid_api_bank/model/identity_verification_options.py +264 -0
  99. cybrid_api_bank/model/identity_verification_outcome.py +2 -2
  100. cybrid_api_bank/model/identity_verification_persona_state.py +2 -2
  101. cybrid_api_bank/model/identity_verification_state.py +2 -2
  102. cybrid_api_bank/model/identity_verification_type.py +2 -2
  103. cybrid_api_bank/model/identity_verification_with_details.py +26 -4
  104. cybrid_api_bank/model/identity_verification_with_details_pii.py +26 -2
  105. cybrid_api_bank/model/identity_verification_with_details_pii_address.py +2 -2
  106. cybrid_api_bank/model/{post_external_bank_account_counterparty_bank_account.py → identity_verification_with_details_pii_aliases_inner.py} +10 -23
  107. cybrid_api_bank/model/identity_verification_with_details_pii_name.py +2 -2
  108. cybrid_api_bank/model/invoice.py +3 -3
  109. cybrid_api_bank/model/invoice_list.py +2 -2
  110. cybrid_api_bank/model/list_request_page.py +2 -2
  111. cybrid_api_bank/model/list_request_per_page.py +2 -2
  112. cybrid_api_bank/model/patch_bank.py +2 -2
  113. cybrid_api_bank/model/patch_customer.py +2 -2
  114. cybrid_api_bank/model/patch_external_bank_account.py +2 -2
  115. cybrid_api_bank/model/patch_transfer.py +282 -0
  116. cybrid_api_bank/model/patch_transfer_participant.py +291 -0
  117. cybrid_api_bank/model/payment_instruction.py +2 -2
  118. cybrid_api_bank/model/payment_instruction_list.py +2 -2
  119. cybrid_api_bank/model/persona_session.py +282 -0
  120. cybrid_api_bank/model/plan.py +366 -0
  121. cybrid_api_bank/model/plan_travel_rule_info.py +290 -0
  122. cybrid_api_bank/model/platform_file.py +52 -32
  123. cybrid_api_bank/model/platform_file_list.py +2 -2
  124. cybrid_api_bank/model/post_account.py +3 -3
  125. cybrid_api_bank/model/post_bank.py +2 -2
  126. cybrid_api_bank/model/post_bank_account_details.py +321 -0
  127. cybrid_api_bank/model/post_counterparty.py +2 -2
  128. cybrid_api_bank/model/post_counterparty_address.py +2 -2
  129. cybrid_api_bank/model/post_counterparty_aliases_inner.py +2 -2
  130. cybrid_api_bank/model/post_counterparty_name.py +2 -2
  131. cybrid_api_bank/model/post_customer.py +2 -2
  132. cybrid_api_bank/model/post_customer_address.py +2 -2
  133. cybrid_api_bank/model/post_customer_aliases_inner.py +2 -2
  134. cybrid_api_bank/model/post_customer_name.py +2 -2
  135. cybrid_api_bank/model/post_deposit_address.py +2 -2
  136. cybrid_api_bank/model/post_deposit_bank_account.py +2 -2
  137. cybrid_api_bank/model/post_execution.py +274 -0
  138. cybrid_api_bank/model/post_external_bank_account.py +8 -8
  139. cybrid_api_bank/model/post_external_bank_account_counterparty_address.py +2 -2
  140. cybrid_api_bank/model/post_external_bank_account_counterparty_name.py +2 -2
  141. cybrid_api_bank/model/post_external_wallet.py +15 -4
  142. cybrid_api_bank/model/post_fee.py +2 -2
  143. cybrid_api_bank/model/post_file.py +8 -2
  144. cybrid_api_bank/model/post_identification_number.py +3 -2
  145. cybrid_api_bank/model/post_identity_verification.py +9 -4
  146. cybrid_api_bank/model/post_identity_verification_address.py +2 -2
  147. cybrid_api_bank/model/post_identity_verification_aliases_inner.py +2 -2
  148. cybrid_api_bank/model/post_identity_verification_name.py +2 -2
  149. cybrid_api_bank/model/post_invoice.py +3 -3
  150. cybrid_api_bank/model/post_payment_instruction.py +2 -2
  151. cybrid_api_bank/model/post_persona_session.py +276 -0
  152. cybrid_api_bank/model/post_plan.py +317 -0
  153. cybrid_api_bank/model/post_plan_destination_account.py +278 -0
  154. cybrid_api_bank/model/post_plan_source_account.py +278 -0
  155. cybrid_api_bank/model/post_plan_travel_rule_info.py +276 -0
  156. cybrid_api_bank/model/post_quote.py +7 -8
  157. cybrid_api_bank/model/post_quote_entry.py +2 -2
  158. cybrid_api_bank/model/post_supported_payout_symbols.py +2 -2
  159. cybrid_api_bank/model/post_trade.py +2 -3
  160. cybrid_api_bank/model/post_transfer.py +2 -2
  161. cybrid_api_bank/model/post_transfer_participant.py +2 -2
  162. cybrid_api_bank/model/post_ultimate_beneficial_owner.py +2 -2
  163. cybrid_api_bank/model/post_workflow.py +4 -4
  164. cybrid_api_bank/model/quote.py +5 -5
  165. cybrid_api_bank/model/quote_entry.py +2 -2
  166. cybrid_api_bank/model/quote_entry_destination_account.py +2 -2
  167. cybrid_api_bank/model/quote_entry_source_account.py +2 -2
  168. cybrid_api_bank/model/quote_list.py +2 -2
  169. cybrid_api_bank/model/quote_side.py +2 -2
  170. cybrid_api_bank/model/quote_type.py +2 -2
  171. cybrid_api_bank/model/stage.py +328 -0
  172. cybrid_api_bank/model/symbol_price.py +3 -3
  173. cybrid_api_bank/model/symbol_price_response.py +2 -2
  174. cybrid_api_bank/model/symbols.py +2 -2
  175. cybrid_api_bank/model/trade.py +6 -6
  176. cybrid_api_bank/model/trade_failure_code.py +7 -6
  177. cybrid_api_bank/model/trade_list.py +2 -2
  178. cybrid_api_bank/model/trade_side.py +2 -2
  179. cybrid_api_bank/model/trade_state.py +7 -6
  180. cybrid_api_bank/model/trade_type.py +2 -2
  181. cybrid_api_bank/model/transfer.py +37 -9
  182. cybrid_api_bank/model/transfer_account_type.py +2 -2
  183. cybrid_api_bank/model/transfer_destination_account.py +2 -2
  184. cybrid_api_bank/model/transfer_entry.py +2 -2
  185. cybrid_api_bank/model/transfer_entry_destination_account.py +2 -2
  186. cybrid_api_bank/model/transfer_failure_code.py +9 -6
  187. cybrid_api_bank/model/transfer_hold_details.py +272 -0
  188. cybrid_api_bank/model/transfer_identifiers_inner.py +273 -0
  189. cybrid_api_bank/model/transfer_list.py +2 -2
  190. cybrid_api_bank/model/transfer_participant.py +2 -2
  191. cybrid_api_bank/model/transfer_side.py +2 -2
  192. cybrid_api_bank/model/transfer_source_account.py +2 -2
  193. cybrid_api_bank/model/transfer_state.py +7 -6
  194. cybrid_api_bank/model/transfer_type.py +2 -2
  195. cybrid_api_bank/model/travel_rule_info_party.py +280 -0
  196. cybrid_api_bank/model/workflow.py +2 -2
  197. cybrid_api_bank/model/workflow_state.py +2 -2
  198. cybrid_api_bank/model/workflow_type.py +2 -2
  199. cybrid_api_bank/model/workflow_with_details.py +2 -2
  200. cybrid_api_bank/model/workflow_with_details_all_of.py +2 -2
  201. cybrid_api_bank/model/workflows_list.py +2 -2
  202. cybrid_api_bank/model_utils.py +2 -2
  203. cybrid_api_bank/models/__init__.py +26 -1
  204. cybrid_api_bank/rest.py +2 -2
  205. {cybrid_api_bank_python-0.123.287.dist-info → cybrid_api_bank_python-0.125.156.dist-info}/METADATA +2 -2
  206. cybrid_api_bank_python-0.125.156.dist-info/RECORD +210 -0
  207. {cybrid_api_bank_python-0.123.287.dist-info → cybrid_api_bank_python-0.125.156.dist-info}/WHEEL +1 -1
  208. cybrid_api_bank_python-0.123.287.dist-info/RECORD +0 -182
  209. {cybrid_api_bank_python-0.123.287.dist-info → cybrid_api_bank_python-0.125.156.dist-info}/top_level.txt +0 -0
@@ -0,0 +1,290 @@
1
+ """
2
+ Cybrid Bank API
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.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 Introduction](https://docs.cybrid.xyz/docs/how-is-cybrid-architected) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/testing-with-hosted-web-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/how-do-i-get-started-with-the-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://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer. # noqa: E501
5
+
6
+ The version of the OpenAPI document: v0.125.156
7
+ Contact: support@cybrid.app
8
+ Generated by: https://openapi-generator.tech
9
+ """
10
+
11
+
12
+ import re # noqa: F401
13
+ import sys # noqa: F401
14
+
15
+ from cybrid_api_bank.model_utils import ( # noqa: F401
16
+ ApiTypeError,
17
+ ModelComposed,
18
+ ModelNormal,
19
+ ModelSimple,
20
+ cached_property,
21
+ change_keys_js_to_python,
22
+ convert_js_args_to_python_args,
23
+ date,
24
+ datetime,
25
+ file_type,
26
+ none_type,
27
+ validate_get_composed_info,
28
+ OpenApiModel
29
+ )
30
+ from cybrid_api_bank.exceptions import ApiAttributeError
31
+
32
+
33
+ def lazy_import():
34
+ from cybrid_api_bank.model.travel_rule_info_party import TravelRuleInfoParty
35
+ globals()['TravelRuleInfoParty'] = TravelRuleInfoParty
36
+
37
+
38
+ class PlanTravelRuleInfo(ModelNormal):
39
+ """NOTE: This class is auto generated by OpenAPI Generator.
40
+ Ref: https://openapi-generator.tech
41
+
42
+ Do not edit the class manually.
43
+
44
+ Attributes:
45
+ allowed_values (dict): The key is the tuple path to the attribute
46
+ and the for var_name this is (var_name,). The value is a dict
47
+ with a capitalized key describing the allowed value and an allowed
48
+ value. These dicts store the allowed enum values.
49
+ attribute_map (dict): The key is attribute name
50
+ and the value is json key in definition.
51
+ discriminator_value_class_map (dict): A dict to go from the discriminator
52
+ variable value to the discriminator class name.
53
+ validations (dict): The key is the tuple path to the attribute
54
+ and the for var_name this is (var_name,). The value is a dict
55
+ that stores validations for max_length, min_length, max_items,
56
+ min_items, exclusive_maximum, inclusive_maximum, exclusive_minimum,
57
+ inclusive_minimum, and regex.
58
+ additional_properties_type (tuple): A tuple of classes accepted
59
+ as additional properties values.
60
+ """
61
+
62
+ allowed_values = {
63
+ }
64
+
65
+ validations = {
66
+ }
67
+
68
+ @cached_property
69
+ def additional_properties_type():
70
+ """
71
+ This must be a method because a model may have properties that are
72
+ of type self, this must run after the class is loaded
73
+ """
74
+ lazy_import()
75
+ return (bool, date, datetime, dict, float, int, list, str, none_type,) # noqa: E501
76
+
77
+ _nullable = False
78
+
79
+ @cached_property
80
+ def openapi_types():
81
+ """
82
+ This must be a method because a model may have properties that are
83
+ of type self, this must run after the class is loaded
84
+
85
+ Returns
86
+ openapi_types (dict): The key is attribute name
87
+ and the value is attribute type.
88
+ """
89
+ lazy_import()
90
+ return {
91
+ 'originating_party': (TravelRuleInfoParty,), # noqa: E501
92
+ 'receiving_party': (TravelRuleInfoParty,), # noqa: E501
93
+ 'ultimate_originating_party': (TravelRuleInfoParty,), # noqa: E501
94
+ 'ultimate_receiving_party': (TravelRuleInfoParty,), # noqa: E501
95
+ }
96
+
97
+ @cached_property
98
+ def discriminator():
99
+ return None
100
+
101
+
102
+ attribute_map = {
103
+ 'originating_party': 'originating_party', # noqa: E501
104
+ 'receiving_party': 'receiving_party', # noqa: E501
105
+ 'ultimate_originating_party': 'ultimate_originating_party', # noqa: E501
106
+ 'ultimate_receiving_party': 'ultimate_receiving_party', # noqa: E501
107
+ }
108
+
109
+ read_only_vars = {
110
+ }
111
+
112
+ _composed_schemas = {}
113
+
114
+ @classmethod
115
+ @convert_js_args_to_python_args
116
+ def _from_openapi_data(cls, originating_party, receiving_party, *args, **kwargs): # noqa: E501
117
+ """PlanTravelRuleInfo - a model defined in OpenAPI
118
+
119
+ Args:
120
+ originating_party (TravelRuleInfoParty):
121
+ receiving_party (TravelRuleInfoParty):
122
+
123
+ Keyword Args:
124
+ _check_type (bool): if True, values for parameters in openapi_types
125
+ will be type checked and a TypeError will be
126
+ raised if the wrong type is input.
127
+ Defaults to True
128
+ _path_to_item (tuple/list): This is a list of keys or values to
129
+ drill down to the model in received_data
130
+ when deserializing a response
131
+ _spec_property_naming (bool): True if the variable names in the input data
132
+ are serialized names, as specified in the OpenAPI document.
133
+ False if the variable names in the input data
134
+ are pythonic names, e.g. snake case (default)
135
+ _configuration (Configuration): the instance to use when
136
+ deserializing a file_type parameter.
137
+ If passed, type conversion is attempted
138
+ If omitted no type conversion is done.
139
+ _visited_composed_classes (tuple): This stores a tuple of
140
+ classes that we have traveled through so that
141
+ if we see that class again we will not use its
142
+ discriminator again.
143
+ When traveling through a discriminator, the
144
+ composed schema that is
145
+ is traveled through is added to this set.
146
+ For example if Animal has a discriminator
147
+ petType and we pass in "Dog", and the class Dog
148
+ allOf includes Animal, we move through Animal
149
+ once using the discriminator, and pick Dog.
150
+ Then in Dog, we will make an instance of the
151
+ Animal class but this time we won't travel
152
+ through its discriminator because we passed in
153
+ _visited_composed_classes = (Animal,)
154
+ ultimate_originating_party (TravelRuleInfoParty): [optional] # noqa: E501
155
+ ultimate_receiving_party (TravelRuleInfoParty): [optional] # noqa: E501
156
+ """
157
+
158
+ _check_type = kwargs.pop('_check_type', True)
159
+ _spec_property_naming = kwargs.pop('_spec_property_naming', True)
160
+ _path_to_item = kwargs.pop('_path_to_item', ())
161
+ _configuration = kwargs.pop('_configuration', None)
162
+ _visited_composed_classes = kwargs.pop('_visited_composed_classes', ())
163
+
164
+ self = super(OpenApiModel, cls).__new__(cls)
165
+
166
+ if args:
167
+ for arg in args:
168
+ if isinstance(arg, dict):
169
+ kwargs.update(arg)
170
+ else:
171
+ raise ApiTypeError(
172
+ "Invalid positional arguments=%s passed to %s. Remove those invalid positional arguments." % (
173
+ args,
174
+ self.__class__.__name__,
175
+ ),
176
+ path_to_item=_path_to_item,
177
+ valid_classes=(self.__class__,),
178
+ )
179
+
180
+ self._data_store = {}
181
+ self._check_type = _check_type
182
+ self._spec_property_naming = _spec_property_naming
183
+ self._path_to_item = _path_to_item
184
+ self._configuration = _configuration
185
+ self._visited_composed_classes = _visited_composed_classes + (self.__class__,)
186
+
187
+ self.originating_party = originating_party
188
+ self.receiving_party = receiving_party
189
+ for var_name, var_value in kwargs.items():
190
+ if var_name not in self.attribute_map and \
191
+ self._configuration is not None and \
192
+ self._configuration.discard_unknown_keys and \
193
+ self.additional_properties_type is None:
194
+ # discard variable.
195
+ continue
196
+ setattr(self, var_name, var_value)
197
+ return self
198
+
199
+ required_properties = set([
200
+ '_data_store',
201
+ '_check_type',
202
+ '_spec_property_naming',
203
+ '_path_to_item',
204
+ '_configuration',
205
+ '_visited_composed_classes',
206
+ ])
207
+
208
+ @convert_js_args_to_python_args
209
+ def __init__(self, originating_party, receiving_party, *args, **kwargs): # noqa: E501
210
+ """PlanTravelRuleInfo - a model defined in OpenAPI
211
+
212
+ Args:
213
+ originating_party (TravelRuleInfoParty):
214
+ receiving_party (TravelRuleInfoParty):
215
+
216
+ Keyword Args:
217
+ _check_type (bool): if True, values for parameters in openapi_types
218
+ will be type checked and a TypeError will be
219
+ raised if the wrong type is input.
220
+ Defaults to True
221
+ _path_to_item (tuple/list): This is a list of keys or values to
222
+ drill down to the model in received_data
223
+ when deserializing a response
224
+ _spec_property_naming (bool): True if the variable names in the input data
225
+ are serialized names, as specified in the OpenAPI document.
226
+ False if the variable names in the input data
227
+ are pythonic names, e.g. snake case (default)
228
+ _configuration (Configuration): the instance to use when
229
+ deserializing a file_type parameter.
230
+ If passed, type conversion is attempted
231
+ If omitted no type conversion is done.
232
+ _visited_composed_classes (tuple): This stores a tuple of
233
+ classes that we have traveled through so that
234
+ if we see that class again we will not use its
235
+ discriminator again.
236
+ When traveling through a discriminator, the
237
+ composed schema that is
238
+ is traveled through is added to this set.
239
+ For example if Animal has a discriminator
240
+ petType and we pass in "Dog", and the class Dog
241
+ allOf includes Animal, we move through Animal
242
+ once using the discriminator, and pick Dog.
243
+ Then in Dog, we will make an instance of the
244
+ Animal class but this time we won't travel
245
+ through its discriminator because we passed in
246
+ _visited_composed_classes = (Animal,)
247
+ ultimate_originating_party (TravelRuleInfoParty): [optional] # noqa: E501
248
+ ultimate_receiving_party (TravelRuleInfoParty): [optional] # noqa: E501
249
+ """
250
+
251
+ _check_type = kwargs.pop('_check_type', True)
252
+ _spec_property_naming = kwargs.pop('_spec_property_naming', False)
253
+ _path_to_item = kwargs.pop('_path_to_item', ())
254
+ _configuration = kwargs.pop('_configuration', None)
255
+ _visited_composed_classes = kwargs.pop('_visited_composed_classes', ())
256
+
257
+ if args:
258
+ for arg in args:
259
+ if isinstance(arg, dict):
260
+ kwargs.update(arg)
261
+ else:
262
+ raise ApiTypeError(
263
+ "Invalid positional arguments=%s passed to %s. Remove those invalid positional arguments." % (
264
+ args,
265
+ self.__class__.__name__,
266
+ ),
267
+ path_to_item=_path_to_item,
268
+ valid_classes=(self.__class__,),
269
+ )
270
+
271
+ self._data_store = {}
272
+ self._check_type = _check_type
273
+ self._spec_property_naming = _spec_property_naming
274
+ self._path_to_item = _path_to_item
275
+ self._configuration = _configuration
276
+ self._visited_composed_classes = _visited_composed_classes + (self.__class__,)
277
+
278
+ self.originating_party = originating_party
279
+ self.receiving_party = receiving_party
280
+ for var_name, var_value in kwargs.items():
281
+ if var_name not in self.attribute_map and \
282
+ self._configuration is not None and \
283
+ self._configuration.discard_unknown_keys and \
284
+ self.additional_properties_type is None:
285
+ # discard variable.
286
+ continue
287
+ setattr(self, var_name, var_value)
288
+ if var_name in self.read_only_vars:
289
+ raise ApiAttributeError(f"`{var_name}` is a read-only attribute. Use `from_openapi_data` to instantiate "
290
+ f"class with read only attributes.")
@@ -1,9 +1,9 @@
1
1
  """
2
2
  Cybrid Bank 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.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 Introduction](https://docs.cybrid.xyz/docs/how-is-cybrid-architected) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/testing-with-hosted-web-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/how-do-i-get-started-with-the-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://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:write counterparties:execute customers:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers: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 deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:write identity_verifications:execute files:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:execute counterparties:read 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 deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read files:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer. # noqa: E501
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 Introduction](https://docs.cybrid.xyz/docs/how-is-cybrid-architected) 3. [Testing with Hosted Web Demo App](https://docs.cybrid.xyz/docs/testing-with-hosted-web-demo-app) In [Getting Started in the Cybrid Sandbox](https://docs.cybrid.xyz/docs/how-do-i-get-started-with-the-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://kb.cybrid.xyz/getting-ready-for-trading), we walk through creating customers, customer identities, accounts, as well as executing quotes and trades. ## Working with the Cybrid Platform There are three primary ways you can interact with the Cybrid platform: 1. Directly via our RESTful API (this documentation) 2. Using our API clients available in a variety of languages ([Angular](https://github.com/Cybrid-app/cybrid-api-bank-angular), [Java](https://github.com/Cybrid-app/cybrid-api-bank-java), [Kotlin](https://github.com/Cybrid-app/cybrid-api-bank-kotlin), [Python](https://github.com/Cybrid-app/cybrid-api-bank-python), [Ruby](https://github.com/Cybrid-app/cybrid-api-bank-ruby), [Swift](https://github.com/Cybrid-app/cybrid-api-bank-swift) or [Typescript](https://github.com/Cybrid-app/cybrid-api-bank-typescript)) 3. Integrating a platform specific SDK ([Web](https://github.com/Cybrid-app/cybrid-sdk-web), [Android](https://github.com/Cybrid-app/cybrid-sdk-android), [iOS](https://github.com/Cybrid-app/cybrid-sdk-ios)) Our complete set of APIs allows you to manage resources across three distinct areas: your `Organization`, your `Banks` and your `Identities`. For most of your testing and interaction you'll be using the `Bank` API, which is where the majority of APIs reside. *The complete set of APIs can be found on the following pages:* | API | Description | |------------------------------------------------------------------|-------------------------------------------------------------| | [Organization API](https://organization.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organizations | | [Bank API](https://bank.production.cybrid.app/api/schema/swagger-ui) | APIs to manage banks (and all downstream customer activity) | | [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui) | APIs to manage organization and bank identities | For questions please contact [Support](mailto:support@cybrid.xyz) at any time for assistance, or contact the [Product Team](mailto:product@cybrid.xyz) for product suggestions. ## Authenticating with the API The Cybrid Platform uses OAuth 2.0 Bearer Tokens to authenticate requests to the platform. Credentials to create `Organization` and `Bank` tokens can be generated via the [Cybrid Sandbox](https://id.production.cybrid.app). Access tokens can be generated for a `Customer` as well via the [Cybrid IdP](https://id.production.cybrid.app) as well. An `Organization` access token applies broadly to the whole Organization and all of its `Banks`, whereas, a `Bank` access token is specific to an individual Bank. `Customer` tokens, similarly, are scoped to a specific customer in a bank. Both `Organization` and `Bank` tokens can be created using the OAuth Client Credential Grant flow. Each Organization and Bank has its own unique `Client ID` and `Secret` that allows for machine-to-machine authentication. A `Bank` can then generate `Customer` access tokens via API using our [Identities API](https://id.production.cybrid.app/api/schema/swagger-ui). <font color=\"orange\">**⚠️ Never share your Client ID or Secret publicly or in your source code repository.**</font> Your `Client ID` and `Secret` can be exchanged for a time-limited `Bearer Token` by interacting with the Cybrid Identity Provider or through interacting with the **Authorize** button in this document. The following curl command can be used to quickly generate a `Bearer Token` for use in testing the API or demo applications. ``` # Example request when using Bank credentials curl -X POST https://id.production.cybrid.app/oauth/token -d '{ \"grant_type\": \"client_credentials\", \"client_id\": \"<Your Client ID>\", \"client_secret\": \"<Your Secret>\", \"scope\": \"banks:read banks:write bank_applications:execute accounts:read accounts:execute counterparties:read counterparties:pii:read counterparties:write counterparties:execute customers:read customers:pii:read customers:write customers:execute prices:read quotes:execute quotes:read trades:execute trades:read transfers:execute transfers:read transfers:write external_bank_accounts:read external_bank_accounts:pii:read external_bank_accounts:write external_bank_accounts:execute external_wallets:read external_wallets:execute workflows:read workflows:execute deposit_addresses:read deposit_addresses:execute deposit_bank_accounts:read deposit_bank_accounts:execute invoices:read invoices:write invoices:execute identity_verifications:read identity_verifications:pii:read identity_verifications:write identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute\" }' -H \"Content-Type: application/json\" # When using Organization credentials set `scope` to 'organizations:read organizations:write organization_applications:execute banks:read banks:write banks:execute bank_applications:execute users:read users:write users:execute counterparties:read counterparties:pii:read customers:read customers:pii:read accounts:read prices:read quotes:execute quotes:read trades:execute trades:read transfers:read transfers:write transfers:execute external_bank_accounts:read external_bank_accounts:pii:read external_wallets:read workflows:read deposit_addresses:read deposit_bank_accounts:read invoices:read subscriptions:read subscriptions:write subscriptions:execute subscription_events:read subscription_events:execute identity_verifications:read identity_verifications:pii:read identity_verifications:execute persona_sessions:execute plans:execute plans:read executions:execute executions:read files:read files:pii:read files:execute' ``` <font color=\"orange\">**⚠️ Note: The above curl will create a bearer token with full scope access. Delete scopes if you'd like to restrict access.**</font> ## Authentication Scopes The Cybrid platform supports the use of scopes to control the level of access a token is limited to. Scopes do not grant access to resources; instead, they provide limits, in support of the least privilege principal. The following scopes are available on the platform and can be requested when generating either an Organization, Bank or Customer token. Generally speaking, the _Read_ scope is required to read and list resources, the _Write_ scope is required to update a resource and the _Execute_ scope is required to create a resource. | Resource | Read scope (Token Type) | Write scope (Token Type) | Execute scope (Token Type) | |-----------------------|------------------------------------------------------------|-----------------------------------------------|--------------------------------------------------| | Account | accounts:read (Organization, Bank, Customer) | | accounts:execute (Bank, Customer) | | Bank | banks:read (Organization, Bank) | banks:write (Organization, Bank) | banks:execute (Organization) | | Customer | customers:read (Organization, Bank, Customer) | customers:write (Bank, Customer) | customers:execute (Bank) | | Counterparty | counterparties:read (Organization, Bank, Customer) | counterparties:write (Bank, Customer) | counterparties:execute (Bank) | | Deposit Address | deposit_addresses:read (Organization, Bank, Customer) | deposit_addresses:write (Bank, Customer) | deposit_addresses:execute (Bank, Customer) | | External Bank Account | external_bank_accounts:read (Organization, Bank, Customer) | external_bank_accounts:write (Bank, Customer) | external_bank_accounts:execute (Bank, Customer) | | External Wallet | external_wallet:read (Organization, Bank, Customer) | | external_wallet:execute (Bank, Customer) | | Organization | organizations:read (Organization) | organizations:write (Organization) | | | User | users:read (Organization) | | users:execute (Organization) | | Price | prices:read (Bank, Customer) | | | | Quote | quotes:read (Organization, Bank, Customer) | | quotes:execute (Organization, Bank, Customer) | | Trade | trades:read (Organization, Bank, Customer) | | trades:execute (Organization, Bank, Customer) | | Transfer | transfers:read (Organization, Bank, Customer) | | transfers:execute (Organization, Bank, Customer) | | Workflow | workflows:read (Organization, Bank, Customer) | | workflows:execute (Bank, Customer) | | Invoice | invoices:read (Organization, Bank, Customer) | invoices:write (Bank, Customer) | invoices:execute (Bank, Customer) | ## Available Endpoints The available APIs for the [Identity](https://id.production.cybrid.app/api/schema/swagger-ui), [Organization](https://organization.production.cybrid.app/api/schema/swagger-ui) and [Bank](https://bank.production.cybrid.app/api/schema/swagger-ui) API services are listed below: | API Service | Model | API Endpoint Path | Description | |--------------|----------------------|--------------------------------|---------------------------------------------------------------------------------------------------| | Identity | Bank | /api/bank_applications | Create and list banks | | Identity | CustomerToken | /api/customer_tokens | Create customer JWT access tokens | | Identity | Organization | /api/organization_applications | Create and list organizations | | Identity | Organization | /api/users | Create and list organization users | | Organization | Organization | /api/organizations | APIs to retrieve and update organization name | | Bank | Account | /api/accounts | Create and list accounts, which hold a specific asset for a customers | | Bank | Asset | /api/assets | Get a list of assets supported by the platform (ex: BTC, ETH) | | Bank | Bank | /api/banks | Create, update and list banks, the parent to customers, accounts, etc | | Bank | Customer | /api/customers | Create and list customers | | Bank | Counterparty | /api/counterparties | Create and list counterparties | | Bank | DepositAddress | /api/deposit_addresses | Create, get and list deposit addresses | | Bank | ExternalBankAccount | /api/external_bank_accounts | Create, get and list external bank accounts, which connect customer bank accounts to the platform | | Bank | ExternalWallet | /api/external_wallets | Create, get, list and delete external wallets, which connect customer wallets to the platform | | Bank | IdentityVerification | /api/identity_verifications | Create and list identity verifications, which are performed on customers for KYC | | Bank | Invoice | /api/invoices | Create, get, cancel and list invoices | | Bank | PaymentInstruction | /api/payment_instructions | Create, get and list payment instructions for invoices | | Bank | Price | /api/prices | Get the current prices for assets on the platform | | Bank | Quote | /api/quotes | Create and list quotes, which are required to execute trades | | Bank | Symbol | /api/symbols | Get a list of symbols supported for trade (ex: BTC-USD) | | Bank | Trade | /api/trades | Create and list trades, which buy or sell cryptocurrency | | Bank | Transfer | /api/transfers | Create, get and list transfers (e.g., funding, book) | | Bank | Workflow | /api/workflows | Create, get and list workflows | ## Understanding Object Models & Endpoints **Organizations** An `Organization` is meant to represent the organization partnering with Cybrid to use our platform. An `Organization` typically does not directly interact with `customers`. Instead, an Organization has one or more `banks`, which encompass the financial service offerings of the platform. **Banks** A `Bank` is owned by an `Organization` and can be thought of as an environment or container for `customers` and product offerings. Banks are created in either `Sandbox` or `Production` mode, where `Sandbox` is the environment that you would test, prototype and build in prior to moving to `Production`. An `Organization` can have multiple `banks`, in either `Sandbox` or `Production` environments. A `Sandbox Bank` will be backed by stubbed data and process flows. For instance, funding source transfer processes as well as trades will be simulated rather than performed, however asset prices are representative of real-world values. You have an unlimited amount of simulated fiat currency for testing purposes. **Customers** `Customers` represent your banking users on the platform. At present, we offer support for `Individuals` as Customers. `Customers` must be verified (i.e., KYC'd) in our system before they can play any part on the platform, which means they must have an associated and a passing `Identity Verification`. See the Identity Verifications section for more details on how a customer can be verified. `Customers` must also have an `Account` to be able to transact, in the desired asset class. See the Accounts APIs for more details on setting up accounts for the customer. # noqa: E501
5
5
 
6
- The version of the OpenAPI document: v0.123.287
6
+ The version of the OpenAPI document: v0.125.156
7
7
  Contact: support@cybrid.app
8
8
  Generated by: https://openapi-generator.tech
9
9
  """
@@ -56,30 +56,6 @@ class PlatformFile(ModelNormal):
56
56
  """
57
57
 
58
58
  allowed_values = {
59
- ('file_type',): {
60
- 'DRIVERS_LICENSE_FRONT': "drivers_license_front",
61
- 'DRIVERS_LICENSE_BACK': "drivers_license_back",
62
- 'PASSPORT': "passport",
63
- 'VISA': "visa",
64
- 'IDENTIFICATION_CARD': "identification_card",
65
- 'RESIDENCE_CARD': "residence_card",
66
- 'SELFIE': "selfie",
67
- 'SELFIE_VIDEO': "selfie_video",
68
- 'SELFIE_LEFT': "selfie_left",
69
- 'SELFIE_RIGHT': "selfie_right",
70
- 'UTILITY_BILL': "utility_bill",
71
- 'BANK_STATEMENT': "bank_statement",
72
- 'PROPERTY_TAX': "property_tax",
73
- 'TAX_DOCUMENT': "tax_document",
74
- 'EIN_LETTER': "ein_letter",
75
- 'INCORPORATION_CERTIFICATE': "incorporation_certificate",
76
- },
77
- ('content_type',): {
78
- 'IMAGE/JPEG': "image/jpeg",
79
- 'IMAGE/PNG': "image/png",
80
- 'APPLICATION/PDF': "application/pdf",
81
- 'VIDEO/MP4': "video/mp4",
82
- },
83
59
  ('state',): {
84
60
  'STORING': "storing",
85
61
  'COMPLETED': "completed",
@@ -92,6 +68,18 @@ class PlatformFile(ModelNormal):
92
68
  'max_length': 32,
93
69
  'min_length': 32,
94
70
  },
71
+ ('organization_guid',): {
72
+ 'max_length': 32,
73
+ 'min_length': 32,
74
+ },
75
+ ('bank_guid',): {
76
+ 'max_length': 32,
77
+ 'min_length': 32,
78
+ },
79
+ ('customer_guid',): {
80
+ 'max_length': 32,
81
+ 'min_length': 32,
82
+ },
95
83
  }
96
84
 
97
85
  @cached_property
@@ -116,12 +104,20 @@ class PlatformFile(ModelNormal):
116
104
  """
117
105
  return {
118
106
  'guid': (str,), # noqa: E501
119
- 'file_type': (str,), # noqa: E501
107
+ 'organization_guid': (str,), # noqa: E501
108
+ 'bank_guid': (str, none_type,), # noqa: E501
109
+ 'customer_guid': (str, none_type,), # noqa: E501
110
+ 'type': (str,), # noqa: E501
120
111
  'content_type': (str,), # noqa: E501
112
+ 'filename': (str,), # noqa: E501
121
113
  'completed_at': (datetime,), # noqa: E501
122
114
  'failed_at': (datetime,), # noqa: E501
123
115
  'state': (str,), # noqa: E501
124
116
  'failure_code': (str, none_type,), # noqa: E501
117
+ 'upload_url': (str, none_type,), # noqa: E501
118
+ 'upload_expires_at': (datetime, none_type,), # noqa: E501
119
+ 'download_url': (str, none_type,), # noqa: E501
120
+ 'download_expires_at': (datetime, none_type,), # noqa: E501
125
121
  }
126
122
 
127
123
  @cached_property
@@ -131,12 +127,20 @@ class PlatformFile(ModelNormal):
131
127
 
132
128
  attribute_map = {
133
129
  'guid': 'guid', # noqa: E501
134
- 'file_type': 'file_type', # noqa: E501
130
+ 'organization_guid': 'organization_guid', # noqa: E501
131
+ 'bank_guid': 'bank_guid', # noqa: E501
132
+ 'customer_guid': 'customer_guid', # noqa: E501
133
+ 'type': 'type', # noqa: E501
135
134
  'content_type': 'content_type', # noqa: E501
135
+ 'filename': 'filename', # noqa: E501
136
136
  'completed_at': 'completed_at', # noqa: E501
137
137
  'failed_at': 'failed_at', # noqa: E501
138
138
  'state': 'state', # noqa: E501
139
139
  'failure_code': 'failure_code', # noqa: E501
140
+ 'upload_url': 'upload_url', # noqa: E501
141
+ 'upload_expires_at': 'upload_expires_at', # noqa: E501
142
+ 'download_url': 'download_url', # noqa: E501
143
+ 'download_expires_at': 'download_expires_at', # noqa: E501
140
144
  }
141
145
 
142
146
  read_only_vars = {
@@ -181,12 +185,20 @@ class PlatformFile(ModelNormal):
181
185
  through its discriminator because we passed in
182
186
  _visited_composed_classes = (Animal,)
183
187
  guid (str): The unique identifier for the file.. [optional] # noqa: E501
184
- file_type (str): The file type; one of drivers_license_front, drivers_license_back, passport, visa, identification_card, residence_card, selfie, selfie_video, selfie_left, selfie_right, utility_bill, bank_statement, property_tax, tax_document, ein_letter, or incorporation_certificate.. [optional] # noqa: E501
185
- content_type (str): The media type; one of image/jpeg, image/png, application/pdf, or video/mp4.. [optional] # noqa: E501
188
+ organization_guid (str): The organization identifier.. [optional] # noqa: E501
189
+ bank_guid (str, none_type): The bank identifier.. [optional] # noqa: E501
190
+ customer_guid (str, none_type): The customer identifier.. [optional] # noqa: E501
191
+ type (str): The file type; one of drivers_license_front, drivers_license_back, passport, passport_card, visa, identification_card, residence_card, work_permit, selfie, selfie_video, selfie_left, selfie_right, utility_bill, proof_of_address, bank_statement, property_tax, tax_document, ein_letter, incorporation_certificate, persona_inquiry_report, or persona_inquiry_export.. [optional] # noqa: E501
192
+ content_type (str): The media type; one of image/jpeg, image/png, application/pdf, application/json, or video/mp4.. [optional] # noqa: E501
193
+ filename (str): The name of the file.. [optional] # noqa: E501
186
194
  completed_at (datetime): The ISO8601 datetime the file was completed at.. [optional] # noqa: E501
187
195
  failed_at (datetime): The ISO8601 datetime the file failed at.. [optional] # noqa: E501
188
196
  state (str): The state of the file. One of storing, completed, or failed.. [optional] # noqa: E501
189
197
  failure_code (str, none_type): The failure code for failed files.. [optional] # noqa: E501
198
+ upload_url (str, none_type): The URL to upload the file to.. [optional] # noqa: E501
199
+ upload_expires_at (datetime, none_type): The ISO8601 datetime the upload URL expires at.. [optional] # noqa: E501
200
+ download_url (str, none_type): The URL to download the file from.. [optional] # noqa: E501
201
+ download_expires_at (datetime, none_type): The ISO8601 datetime the download URL expires at.. [optional] # noqa: E501
190
202
  """
191
203
 
192
204
  _check_type = kwargs.pop('_check_type', True)
@@ -273,12 +285,20 @@ class PlatformFile(ModelNormal):
273
285
  through its discriminator because we passed in
274
286
  _visited_composed_classes = (Animal,)
275
287
  guid (str): The unique identifier for the file.. [optional] # noqa: E501
276
- file_type (str): The file type; one of drivers_license_front, drivers_license_back, passport, visa, identification_card, residence_card, selfie, selfie_video, selfie_left, selfie_right, utility_bill, bank_statement, property_tax, tax_document, ein_letter, or incorporation_certificate.. [optional] # noqa: E501
277
- content_type (str): The media type; one of image/jpeg, image/png, application/pdf, or video/mp4.. [optional] # noqa: E501
288
+ organization_guid (str): The organization identifier.. [optional] # noqa: E501
289
+ bank_guid (str, none_type): The bank identifier.. [optional] # noqa: E501
290
+ customer_guid (str, none_type): The customer identifier.. [optional] # noqa: E501
291
+ type (str): The file type; one of drivers_license_front, drivers_license_back, passport, passport_card, visa, identification_card, residence_card, work_permit, selfie, selfie_video, selfie_left, selfie_right, utility_bill, proof_of_address, bank_statement, property_tax, tax_document, ein_letter, incorporation_certificate, persona_inquiry_report, or persona_inquiry_export.. [optional] # noqa: E501
292
+ content_type (str): The media type; one of image/jpeg, image/png, application/pdf, application/json, or video/mp4.. [optional] # noqa: E501
293
+ filename (str): The name of the file.. [optional] # noqa: E501
278
294
  completed_at (datetime): The ISO8601 datetime the file was completed at.. [optional] # noqa: E501
279
295
  failed_at (datetime): The ISO8601 datetime the file failed at.. [optional] # noqa: E501
280
296
  state (str): The state of the file. One of storing, completed, or failed.. [optional] # noqa: E501
281
297
  failure_code (str, none_type): The failure code for failed files.. [optional] # noqa: E501
298
+ upload_url (str, none_type): The URL to upload the file to.. [optional] # noqa: E501
299
+ upload_expires_at (datetime, none_type): The ISO8601 datetime the upload URL expires at.. [optional] # noqa: E501
300
+ download_url (str, none_type): The URL to download the file from.. [optional] # noqa: E501
301
+ download_expires_at (datetime, none_type): The ISO8601 datetime the download URL expires at.. [optional] # noqa: E501
282
302
  """
283
303
 
284
304
  _check_type = kwargs.pop('_check_type', True)