> ## 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. # Accept Terms and Conditions > Records the customer's acceptance of the active Terms and Conditions for their country. This endpoint is required when the Partner integrates Ramps via API. The customer must accept the T&C before performing on-ramp or off-ramp operations. ## OpenAPI ````yaml ramps-api/openapi.json POST /api/v1/customers/{customerId}/acceptTerms/ 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: 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: 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}/acceptTerms/: post: tags: - Customers summary: Accept Terms and Conditions description: >- Records the customer's acceptance of the active Terms and Conditions for their country. This endpoint is required when the Partner integrates Ramps via API. The customer must accept the T&C before performing on-ramp or off-ramp operations. operationId: acceptTermsAndConditions parameters: - $ref: '#/components/parameters/CustomerId' requestBody: required: true description: Terms and Conditions acceptance payload. content: application/json: schema: $ref: '#/components/schemas/AcceptTermsRequest' example: termsId: 3fa85f64-5717-4562-b3fc-2c963f66afa6 ipAddress: 192.168.1.100 userAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 responses: '201': description: Terms and Conditions accepted successfully. content: application/json: schema: $ref: '#/components/schemas/CustomerTermsAcceptanceResponse' example: termsId: 94b302e4-77d4-4627-af36-8265121bef29 ipAddress: 1.1.1.1 userAgent: null acceptedAt: '2026-02-25T20:29:11.243033Z' '400': description: Bad Request - Invalid input data. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: code: 20000 type: ValidationError detail: ipAddress: - message: Enter a valid IPv4 or IPv6 address. code: invalid 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 - Customer not found or inactive, or Terms and Conditions not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: CustomerNotFound: summary: Customer not found value: code: 20001 type: CustomerNotFoundException detail: message: Customer not found. status: 404 TermsNotFound: summary: Terms and Conditions not found value: code: 20040 type: TermsAndConditionsNotFoundException detail: message: >- No active Terms and Conditions found for this id and country. 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: AcceptTermsRequest: type: object properties: termsId: type: string format: uuid description: UUID of the Terms and Conditions the customer is accepting. example: 3fa85f64-5717-4562-b3fc-2c963f66afa6 ipAddress: type: string format: ipv4 description: IP address of the customer at the time of acceptance. example: 192.168.1.100 userAgent: type: string description: User agent string from the customer's browser or app (optional). example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 required: - termsId - ipAddress CustomerTermsAcceptanceResponse: type: object properties: termsId: type: string format: uuid description: UUID of the accepted Terms and Conditions. example: 3fa85f64-5717-4562-b3fc-2c963f66afa6 ipAddress: type: string description: IP address recorded at the time of acceptance. example: 192.168.1.100 userAgent: type: - string - 'null' description: >- User agent recorded at the time of acceptance. Returns `null` if not provided in the request. example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 acceptedAt: type: string format: date-time description: Timestamp when the customer accepted the Terms and Conditions. example: '2024-06-01T12:00:00Z' required: - termsId - ipAddress - acceptedAt ErrorResponse: type: object properties: code: type: integer description: Application-specific error code. type: type: string description: Type of error or exception. detail: type: object properties: message: type: string description: Detailed error message. additionalProperties: true status: type: integer description: HTTP status code. required: - code - type - detail - status 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 `. ````