> ## 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. # Get Terms Acceptance Status > Returns whether the customer has accepted the currently active Terms and Conditions for their account's country, along with the active T&C details. Use this endpoint to check whether to show the T&C acceptance screen to the customer before proceeding with on-ramp or off-ramp operations. When no active Terms and Conditions exist for the country, `accepted` is always `true` and the term fields (`termsId`, `version`, `url`) are `null` — the customer is not blocked. ## OpenAPI ````yaml ramps-api/openapi.json GET /api/v1/customers/{customerId}/termsAcceptance/ 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}/termsAcceptance/: get: tags: - Terms and Conditions summary: Get Terms Acceptance Status description: >- Returns whether the customer has accepted the currently active Terms and Conditions for their account's country, along with the active T&C details. Use this endpoint to check whether to show the T&C acceptance screen to the customer before proceeding with on-ramp or off-ramp operations. When no active Terms and Conditions exist for the country, `accepted` is always `true` and the term fields (`termsId`, `version`, `url`) are `null` — the customer is not blocked. operationId: getTermsAcceptanceStatus parameters: - $ref: '#/components/parameters/CustomerId' responses: '200': description: Terms acceptance status retrieved successfully. content: application/json: schema: $ref: '#/components/schemas/TermsAcceptanceStatusResponse' examples: Accepted: summary: Customer has accepted the active T&C value: termsId: 3fa85f64-5717-4562-b3fc-2c963f66afa6 country: AR version: '1.0' url: https://example.com/terms/v1.0 accepted: true acceptedAt: '2024-06-01T12:00:00Z' NotAccepted: summary: Customer has not yet accepted the active T&C value: termsId: 3fa85f64-5717-4562-b3fc-2c963f66afa6 country: AR version: '1.0' url: https://example.com/terms/v1.0 accepted: false acceptedAt: null NoActiveTerms: summary: No active T&C for the country — customer is not blocked value: termsId: null country: AR version: null url: null accepted: true acceptedAt: null '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 does not exist. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: code: 20001 type: CustomerNotFoundException detail: message: Customer 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: TermsAcceptanceStatusResponse: type: object properties: termsId: type: - string - 'null' format: uuid description: >- UUID of the active Terms and Conditions. `null` when no active T&C exist for the country. example: 3fa85f64-5717-4562-b3fc-2c963f66afa6 country: type: string description: Country code these Terms and Conditions apply to. example: AR version: type: - string - 'null' description: >- Version string of the active Terms and Conditions. `null` when no active T&C exist. example: '1.0' url: type: - string - 'null' format: uri description: >- URL where the full Terms and Conditions document can be read. `null` when no active T&C exist. example: https://example.com/terms/v1.0 accepted: type: boolean description: >- Whether the customer has accepted the currently active Terms and Conditions. Always `true` when no active T&C exist for the country (the customer is not blocked). example: true acceptedAt: type: - string - 'null' format: date-time description: >- Timestamp when the customer last accepted the active Terms and Conditions. `null` if not yet accepted. example: '2024-06-01T12:00:00Z' required: - country - accepted 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 `. ````