> ## 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. # Submit Investor Profile > **Brazilian accounts only.** Records the customer's answers to the active investor questionnaire and returns the resulting profile. It does not depend on the KYC status — the recommended moment is right after KYC — but the customer must have an email set. Every submission creates a new profile, valid for **one year**. It can be submitted at any time — including while `EXPIRING_SOON`, to renew — and the previous ones are kept as history. See [Investor Profile (Brazil)](/ramps-api/investor-profile/introduction). ## OpenAPI ````yaml ramps-api/openapi.json POST /api/v1/customers/{customerId}/investorProfile/ openapi: 3.1.0 info: title: Ripio Ramp API version: v1 description: >- API for Ripio ramp services, enabling partners to integrate On-Ramp, Off-Ramp, customer management, KYC processes, and other financial functionalities. This API is RESTful, uses JSON for requests and responses, and standard HTTP status codes. This document is based on the 'onramp-api.pdf' provided and aims to be compliant with OpenAPI Specification v3.1.0. The PDF indicates that the API documentation is a draft and subject to change. servers: - url: https://skala-sandbox.ripio.com description: Sandbox environment - url: https://skala.ripio.com description: Production environment security: - BearerToken: [] tags: - name: Authentication description: Operations related to API authentication and authorization. - name: Support Tickets description: >- Operations for raising and tracking customer support tickets with Ripio's support team. This feature must be enabled for your account by the Ripio team. - name: Customers description: Operations related to customer management. - name: KYC description: Operations related to Know Your Customer processes. - name: Investor Profile description: >- Brazilian accounts only: the investor-profile (suitability) questionnaire required by Resolução BCB nº 520/2025. - name: Fiat Accounts description: Operations related to managing fiat accounts and their requirements. - name: Quotes description: Operations related to obtaining and managing conversion quotes. - name: On-Ramp description: Operations related to fiat-to-crypto (on-ramp) processes. - name: Off-Ramp description: Operations related to crypto-to-fiat (off-ramp) processes. - name: Refunds description: >- Operations for returning the money of an on-ramp or off-ramp operation that could not be completed. Each ramp must be enabled for your account by the Ripio team. - name: Transactions description: Operations related to listing and managing all transaction types. - name: Networks description: >- Operations related to retrieving available deposit and withdrawal networks. - name: Rates description: Operations related to retrieving market rates. - name: Transaction Limits description: >- Operations related to retrieving per-transaction limits by currency and ramp operation. - name: Sandbox description: Operations specific to the sandbox environment for testing purposes. - name: Webhooks description: Webhook event notifications from Ripio Ramp API. - name: Sell and Pay description: >- Endpoints for managing Sell and Pay transactions, which allow customers to convert cryptocurrency to fiat currency and pay merchants via QR codes paths: /api/v1/customers/{customerId}/investorProfile/: post: tags: - Investor Profile summary: Submit Investor Profile description: >- **Brazilian accounts only.** Records the customer's answers to the active investor questionnaire and returns the resulting profile. It does not depend on the KYC status — the recommended moment is right after KYC — but the customer must have an email set. Every submission creates a new profile, valid for **one year**. It can be submitted at any time — including while `EXPIRING_SOON`, to renew — and the previous ones are kept as history. See [Investor Profile (Brazil)](/ramps-api/investor-profile/introduction). operationId: submitInvestorProfile parameters: - $ref: '#/components/parameters/CustomerId' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SubmitInvestorProfileRequest' example: questionnaireVersion: 1 answers: - questionId: familiarity_experience answerId: invests_regularly - questionId: investment_goal answerId: maximize_returns - questionId: investment_horizon answerId: more_than_3_years - questionId: drawdown_reaction answerId: buy_more - questionId: savings_allocation answerId: most_savings responses: '201': description: >- Profile recorded. Same body as Get Investor Profile Status; a fresh profile is always `VALID`. content: application/json: schema: $ref: '#/components/schemas/InvestorProfileStatusResponse' example: status: VALID deadline: null investorProfile: profile: AGGRESSIVE description: >- Você tolera alta volatilidade e possíveis perdas em busca de maior rentabilidade. questionnaireVersion: 1 createdAt: '2026-10-01T12:34:56.789012Z' validUntil: '2027-10-01T12:34:56.789012Z' answers: - questionId: familiarity_experience questionText: >- Como você descreveria sua experiência e seu conhecimento com ativos virtuais? answerId: invests_regularly answerText: Invisto regularmente - questionId: investment_goal questionText: Quando você investe, qual é o seu principal objetivo? answerId: maximize_returns answerText: Maximizar os ganhos, mesmo correndo algum risco - questionId: investment_horizon questionText: >- Por quanto tempo você pretende manter seus ativos virtuais? answerId: more_than_3_years answerText: Mais de 3 anos - questionId: drawdown_reaction questionText: >- Se o seu investimento caísse 30% em um mês, o que você faria? answerId: buy_more answerText: Aproveitaria para comprar mais barato - questionId: savings_allocation questionText: >- Que parte das suas economias você pretende destinar a investimentos? answerId: most_savings answerText: A maior parte (mais de 50%) '400': description: Bad Request - nothing was recorded. Told apart by `code`. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: versionNotActive: summary: The questionnaire version is no longer active (20096) description: >- The questionnaire changed after you fetched it. Fetch it again, show the new questions and submit with the new `version`. value: code: 20096 type: InvestorQuestionnaireVersionNotActiveException detail: message: >- Investor questionnaire version '1' is not active for this country. status: 400 invalidAnswers: summary: Missing, repeated or unknown answers (20097) description: >- The reason names the offending question: `question '' was not answered.`, `question '' was answered more than once.`, `unknown question ''.` or `invalid answer '' for question ''.` value: code: 20097 type: InvalidInvestorProfileAnswersException detail: message: >- Invalid investor questionnaire answers: question 'savings_allocation' was not answered. status: 400 notRequired: summary: The investor profile does not apply to your account (20099) description: >- Your account is not a Brazilian account, or the investor profile is not enabled for it. value: code: 20099 type: InvestorProfileNotRequiredException detail: message: The investor profile is not enabled for this account. status: 400 emailRequired: summary: The customer has no email set yet (20014) description: >- Set the customer's email — when creating the customer, or with Update Customer — and submit again. value: code: 20014 type: EmailRequiredException detail: message: The customer must have an email setup. status: 400 validationError: summary: Malformed body (20000) value: code: 20000 type: ValidationError detail: questionnaireVersion: - message: This field is required. code: required status: 400 '401': description: Unauthorized - Invalid or missing access token. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: code: 40001 type: NotAuthenticated detail: message: Authentication credentials were not provided. code: not_authenticated status: 401 '404': description: >- Not Found - the customer does not exist, does not belong to your account, or was deactivated. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: code: 40004 type: NotFound detail: message: Not found. code: not_found status: 404 components: parameters: CustomerId: name: customerId in: path required: true description: Unique identifier for the customer. schema: type: string format: uuid example: 8142b065-79c4-4f48-9e33-11b17bc658d4 schemas: SubmitInvestorProfileRequest: type: object properties: questionnaireVersion: type: integer minimum: 1 description: >- The `version` of the questionnaire the customer answered. It must still be the active one. example: 1 answers: type: array minItems: 1 description: >- One answer per question, in any order. Every question must be answered exactly once. items: $ref: '#/components/schemas/InvestorProfileAnswerInput' required: - questionnaireVersion - answers InvestorProfileStatusResponse: type: object properties: status: type: string enum: - NOT_REQUIRED - REQUIRED_SOON - REQUIRED - VALID - EXPIRING_SOON - EXPIRED description: >- Where the customer stands. Only `REQUIRED` and `EXPIRED` block operations. - `NOT_REQUIRED`: the investor profile does not apply to your account (not a Brazilian account, or not enabled). - `REQUIRED_SOON`: no valid profile yet, but enforcement has not started. The customer can still operate until `deadline`. - `REQUIRED`: no profile, and it is enforced. Orders, sessions and destination accounts are refused with `20100`. - `VALID`: valid profile with more than 30 days left. - `EXPIRING_SOON`: valid profile that expires within 30 days. The customer can still operate; ask them to renew before `deadline`. - `EXPIRED`: the latest profile expired. Orders, sessions and destination accounts are refused with `20100`. example: VALID deadline: type: - string - 'null' format: date-time description: >- When the customer stops being able to operate without answering. Only set for `REQUIRED_SOON` (the start of enforcement) and `EXPIRING_SOON` (the profile's expiry, or the start of enforcement if that is later); `null` otherwise. example: null investorProfile: description: >- The customer's latest profile, or `null` if they never answered. For `EXPIRED` it is the expired profile, returned for reference. The profile belongs to the person, so it may also be present with `NOT_REQUIRED` if they answered it through another integration. oneOf: - $ref: '#/components/schemas/InvestorProfile' - type: 'null' required: - status - deadline - investorProfile ErrorResponse: type: object properties: code: type: integer description: Application-specific error code. type: type: string description: Type of error or exception. detail: type: - object - array description: >- Error details. The shape depends on the error: - Most business errors return an object with a `message` key. - Field validation errors return an object keyed by field name, each holding an array of `{ message, code }`. - Request-level validation errors (e.g. a missing query parameter) return a bare array of `{ message, code }`. properties: message: type: string description: Detailed error message. additionalProperties: true status: type: integer description: HTTP status code. required: - code - type - detail - status InvestorProfileAnswerInput: type: object properties: questionId: type: string description: A `questionId` from the questionnaire. example: familiarity_experience answerId: type: string description: One of the `answerId`s offered for that question. example: invests_regularly required: - questionId - answerId InvestorProfile: type: object properties: profile: type: string enum: - CONSERVATIVE - MODERATE - AGGRESSIVE description: >- The resulting risk profile. Stable identifier: use it as a translation key. example: AGGRESSIVE description: type: string description: Description of the profile, in Portuguese. example: >- Você tolera alta volatilidade e possíveis perdas em busca de maior rentabilidade. questionnaireVersion: type: integer description: Version of the questionnaire that was answered. example: 1 createdAt: type: string format: date-time description: When the answers were submitted. example: '2026-10-01T12:34:56.789012Z' validUntil: type: string format: date-time description: 'When the profile expires: one year after `createdAt`.' example: '2027-10-01T12:34:56.789012Z' answers: type: array items: $ref: '#/components/schemas/InvestorProfileAnswer' required: - profile - description - questionnaireVersion - createdAt - validUntil - answers InvestorProfileAnswer: type: object description: >- An answer as it was given, with the texts of the questionnaire version the customer answered — so it stands on its own as evidence even after the questionnaire changes. properties: questionId: type: string example: familiarity_experience questionText: type: string example: >- Como você descreveria sua experiência e seu conhecimento com ativos virtuais? answerId: type: string example: invests_regularly answerText: type: string example: Invisto regularmente required: - questionId - questionText - answerId - answerText securitySchemes: BearerToken: type: http scheme: bearer bearerFormat: JWT description: >- Access token obtained via [/oauth2/token/](/ramps-api/authentication/acquire-access-token). Use as `Authorization: Bearer `. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.