> ## Documentation Index > Fetch the complete documentation index at: https://docs.ripio.com/llms.txt > Use this file to discover all available pages before exploring further. # Simulate KYC Approval > **Sandbox only.** Simulates the identity reviewer's decision and marks the verification of a KYC Submission as approved, so you can test the [KYC with liveness check](/crypto-as-a-service/kyc/kyc-with-liveness-check) without a real review. The end user does not need to complete the liveness check at `provider_url` first. The endpoint answers `200 OK` with no body. The KYC Submission moves to `COMPLETED` a few moments later, when the KYC service reports the decision back: you receive the `KYC.COMPLETED` webhook as in production (see [BaaS Webhooks](/crypto-as-a-service/webhooks/baas-webhooks#verification-submission-webhook)), or you can poll [Retrieve KYC Submission](/crypto-as-a-service/kyc-submissions/retrieve-kyc-submission). Use it to let the end user operate and keep testing the rest of your integration. See [KYC in sandbox](/crypto-as-a-service/kyc/kyc-in-sandbox) for the full flow. ## OpenAPI ````yaml crypto-as-a-service/openapi.json POST /api/v1/simulate-kyc-validation/{submission_id}/approve/ openapi: 3.0.2 info: title: B2B API version: '1.0' description: >- B2B API allows a third party to access different use cases and services inside of Ripio ecosystem. It is organized around RESTful constraints, with requests and responses in JSON format, using HTTP in the standard format and the answer codes. The API is designed to be compliant with OpenAPI Specification v3.0, which is a trusted open source standard for HTTP-Based APIs. The API offers the ability to test it with a simple, yet powerful sandbox that will enhance developer experience and replicate production capabilities in a well isolated and safe environment, giving developers full freedom to try the integration without compromises. # Error Handling If a request to B2B REST API fails, the response will contain an five-digit error code with a corresponding error message to indicate the details of the error. The following code snippet is a sample error response that contains an error code and message pair: ```` { "code": 40001, "type": "NotAuthenticated", "detail": { "message": "Authentication credentials were not provided.", "code": "not_authenticated" }, "status": 403 } ```` ## Error Codes | Code | Error Category | Description | Resolution | | :------- | :------ | :------ | :----- | | 20000 | Validation Error | Raised when there is a semantic error in the payload of the request. | Check the docs for precise information on how to provide correct values for each resource atribute. | | 20001 | Parse Error | Raised when the API receives a malformed JSON document. | Check for syntax errors in the payload of your request. Also look for sample requests in the docs related to the desired operation. | | 20010 | Expired Quote | Raised when the received quote to execute has expired. | Generate a new quote and execute it within the 30 seconds time window. | | 20011 | Already Executed Quote | Raised when the received quote to execute has been executed before. | Try Generating a new quote with the former pair/amounts to replicate a similar trade. | | 20012 | Not Enough Balance | Raised when the amount to operate (sale/purchase) is larger than the balance amount of the debited currency. | Check end user's balances in order to inform the discrepancy before quote execution. Please contact our support team for further assistance. | | 20013 | Buy Limit Frequency Exceeded | Raised when the "BUY" frequency limit for a given end user has been reached.| Check end user's limits using Limits API in order to inform the discrepancy before performing a quote execution. | | 20014 | Sell Limit Frequency Exceeded | Raised when the "SELL" frequency limit for a given end user has been reached.| Check end user's limits using Limits API in order to inform the discrepancy before performing a quote execution. | | 20015 | Buy Limit Amount Exceeded | Raised when the "BUY" amount limit for a given end user has been reached.| Check end user's limits using Limits API in order to inform the discrepancy before performing a quote execution. | | 20016 | Sell Limit Amount Exceeded | Raised when the "SELL" amount limit for a given end user has been reached.| Check end user's limits using Limits API in order to inform the discrepancy before performing a quote execution. | | 20017 | Buy Transaction Min Limit Exceeded | Raised when the "BUY" amount min limit on a single transaction is exceeded.| Check Ripio's min and max transaction limits. | | 20018 | Buy Transaction Max Limit Exceeded | Raised when the "BUY" amount max limit on a single transaction is exceeded.| Check Ripio's min and max transaction limits. | | 20019 | Sell Transaction Min Limit Exceeded | Raised when the "SELL" amount min limit on a single transaction is exceeded.| Check Ripio's min and max transaction limits. | | 20020 | Sell Transaction Max Limit Exceeded | Raised when the "SELL" amount max limit on a single transaction is exceeded.| Check Ripio's min and max transaction limits. | | 20021 | Banned EndUser | Raised when a quote execution request comes from a banned user.| Please reach out our support team in order to get full detail on why the end user has been banned. | | 20022 | Swap Transaction Min Limit Exceeded | Raised when the "SWAP" amount min limit on a single transaction is exceeded.| Check Ripio's min and max transaction limits. | | 20023 | Swap Transaction Max Limit Exceeded | Raised when the "SWAP" amount max limit on a single transaction is exceeded.| Check Ripio's min and max transaction limits. | | 20024 | Swap Limit Frequency Exceeded | Raised when the "SWAP" frequency limit for a given end user has been reached.| Check end user's limits using Limits API in order to inform the discrepancy before performing a quote execution. | | 20025 | Swap Limit Amount Exceeded | Raised when the "SWAP" amount limit for a given end user has been reached.| Check end user's limits using Limits API in order to inform the discrepancy before performing a quote execution. | | 20026 | Quote With No Price | Raised when the received reusable quote to execute has no price. | Try Generating a new reusable quote with the former pair to replicate a similar trade. | | 20027 | Expired Withdrawal Fee | Raised when trying to execute a withdrawal fee that has already expired. | Request another withdrawal Fee. | | 20029 | Invalid address | Raised when the address provided is not valid on given network. | Try with a valid addres for that network. | | 20030 | Kyc not approved for end user | Raised when the end user doesn't have a kyc process approved. | Check the status of end user's verification submission | | 20031 | Kyc already approved for end user | Raised when the end user already has an approved kyc process. | - | | 20032 | Invalid or disabled payment method type | Raised when the payment_method_type does not exist or is disabled for the acccount. | Please reach out our support team. | | 20033 | Frequency limit exceeded for fiat withdrawals | Raised when the QTY limit for a given currency in a FIAT_WITHDRAWAL operation is exceeded. | - | | 20034 | Amount limit exceeded for fiat withdrawals | Raised when the amount limit for a given currency in a FIAT_WITHDRAWAL operation is exceeded. | - | | 20035 | Fiat account is required | Raised when a fiat account is required. | Create a Fiat account first. | | 20036 | Withdrawal amount less than network dust limit. | Raised when the amount of withdrawal request is less to the network dust limit. | Increase Withrawal amount. | | 20037 | There is no address created for end user and given network. | Raised when there is no address for a given concrete network name. | Create an AutoSwap address first. | || | 40000 | Authentication Failed | Raised when an incoming request includes incorrect authentication. | Check for invalid credentials in your request when trying to authenticate. | | 40001 | Not Authenticated | Raised when an unauthenticated request fails the permission checks. | Check if your request contains a valid and non-expired `access_token`. | | 40003 | Permission Denied | Raised when an authenticated request fails the permission checks. | Check if you have OAuth scopes to access requested resource. Please contact our support team if you think this is an error. | | 40004 | Not Found | Raised when a resource does not exists at the given URL. | Check if the resource you're looking for does exist. | | 40005 | Method Not Allowed | Raised when an incoming request has been performed with certain HTTP verb that is not valid for the requested resource. | Check the resource's docs section to learn the accepted HTTP methods. | | 40006 | Bad Request | Raised when historical market price API endpoint has not been used properly. | Check for syntax errors in the payload of your request. Also look for sample requests in the docs related to the desired operation. | | 40007 | Bad Request | Raised when a currency network is not allowed to operate the selected currency. | Check if your request contains a valid network for the selected currency. | | 40008 | Not Found | Raised when a currency doesn't have its limits configured. | Please reach out our support team with the error details and detailed execution flow. | | 40009 | Bad Request | Raised when an existing Quote with defined external_ref has not been executed, thus it can not be excuted idempotently. | Use another external_ref for the Quote. | | 40010 | Service Unavailable | Raised when there are no addresses available for networks compatible with a specific network name. | Please reach out our support team with the error details and detailed execution flow. | | 40015 | Unsupported Media Type | Raised when the content type of the request data is not JSON compliant. | Check if your request data is compliant with JSON format. | | 40029 | Throttled | Raised when an incoming request fails the throttling checks. | Check if you are exceding the daily/hourly request quota for your account. Please contact our support team if you think you'll need an extended quota for your use-case. | || | 50003 | Service Unavailable | Raised when the service (or requested resource) is not available. | Please reach out our support team with the error details and detailed execution flow. | contact: name: Ripio email: b2b@ripio.com url: https://ripio.com termsOfService: https://www.ripio.com/ar/terms/ servers: - url: https://sandbox-b2b.ripio.com description: Sandbox environment - url: https://b2b-api.ripio.com/ description: Production environment security: - OAuth2: [] tags: - name: Access Token - name: Addresses - name: Auto Swap Addresses - name: Balance - name: Beneficiary Fiat Accounts - name: Deposit IPN - name: Deposits - name: End User - name: Fiat Accounts - name: IPN Webhooks - name: Pairs - name: Periodic Limits - name: Quote Execution - name: Quotes - name: Rates - name: Reusable Quote Execution - name: Reusable Quotes - name: Service Status - name: Swap Reusable Quote Execution - name: Swap Reusable Quotes - name: Transactions - name: TXN Limits - name: Withdrawals - name: Fiat Withdrawals - name: Fiat Deposits - name: KYC Requirements - name: KYC Submissions - name: Simulate Fiat Deposit - name: Simulate KYC Validation - name: Yields - name: IPN Messages paths: /api/v1/simulate-kyc-validation/{submission_id}/approve/: summary: Simulate KYC Approval parameters: - schema: type: string format: uuid name: submission_id in: path required: true description: >- `submission_id` returned by [Create KYC Submission](/crypto-as-a-service/kyc-submissions/create-kyc-submission). post: tags: - Simulate KYC Validation summary: Simulate KYC Approval description: >- **Sandbox only.** Simulates the identity reviewer's decision and marks the verification of a KYC Submission as approved, so you can test the [KYC with liveness check](/crypto-as-a-service/kyc/kyc-with-liveness-check) without a real review. The end user does not need to complete the liveness check at `provider_url` first. The endpoint answers `200 OK` with no body. The KYC Submission moves to `COMPLETED` a few moments later, when the KYC service reports the decision back: you receive the `KYC.COMPLETED` webhook as in production (see [BaaS Webhooks](/crypto-as-a-service/webhooks/baas-webhooks#verification-submission-webhook)), or you can poll [Retrieve KYC Submission](/crypto-as-a-service/kyc-submissions/retrieve-kyc-submission). Use it to let the end user operate and keep testing the rest of your integration. See [KYC in sandbox](/crypto-as-a-service/kyc/kyc-in-sandbox) for the full flow. operationId: post-api-v1-simulate-kyc-validation-submission_id-approve responses: '200': description: >- OK. The decision was sent to the KYC service; the KYC Submission status changes a few moments later. content: text/plain: examples: Example 1: value: '' '400': description: Bad Request. The KYC Submission cannot be approved. content: application/json: schema: type: object properties: code: type: integer description: >- Ripio error code. See [Error handling](/crypto-as-a-service/errors/error-handling). type: type: string description: Error type. detail: type: object properties: message: type: string description: Human-readable description of the error. status: type: integer description: HTTP status code. examples: Account approves KYC automatically: value: code: 20093 type: KycAutoApprovedAccountException detail: message: >- This account approves KYC automatically: there is no KYC review to approve or reject. status: 400 Submission already decided: value: code: 20094 type: KycValidationAlreadyResolvedException detail: message: >- KYC submission '6295fdf3-fae8-4a3f-a16b-6b43b258a6c0' is already COMPLETED. status: 400 No verification open with the provider: value: code: 20095 type: KycValidationNotStartedException detail: message: >- KYC submission '6295fdf3-fae8-4a3f-a16b-6b43b258a6c0' has no verification open with the KYC provider yet, so there is nothing to approve or reject. status: 400 '404': description: >- Not Found. There is no KYC Submission with that `submission_id` in your account. security: - OAuth2: - write components: securitySchemes: OAuth2: type: oauth2 flows: clientCredentials: scopes: read: Default scope to read all resources. write: Default scope to performe write operations on certain resources. tokenUrl: https://sandbox-b2b.ripio.com/oauth2/token/ description: > B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow: * **clientCredentials** allows you to access your own B2B account (First-Party Integration) and performs transactions against the public API. This oauth2 flow is well suited for this API, as it allows machine-to-machine communication. Every call to the API has to be authenticated with an OAuth2 Token. In order to request this token, you will need to have sandbox or production API Keys (client id and client secret) that will be needed to generate a credential in order to negotiate an ephemeral access token. Every request must be accompianed by an `Authorization` header with a value that follows the following schema: `Bearer ACCESS_TOKEN` ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.