> ## Documentation Index > Fetch the complete documentation index at: https://docs.cadanapay.com/llms.txt > Use this file to discover all available pages before exploring further. # List Terms > Returns the catalog of business terms, each with the `name` and `version` a business accepts through [Accept Business Terms](/api-reference/workforce/terms/accept-business-terms). Pass `product` to get only the terms required for that product; omit it to get the full catalog. Always read term names and versions from this endpoint rather than hard-coding them — when a version changes, a business has to accept the new version. ## OpenAPI ````yaml /openapi/workforce-management.yaml get /v1/terms openapi: 3.0.0 info: description: APIs for interacting with Cadana Payroll Platform version: 1.0.0 title: Business Workforce Management termsOfService: https://cadanapay.com/terms-and-conditions contact: email: api@cadanapay.com license: name: Apache 2.0 url: http://www.apache.org/licenses/LICENSE-2.0.html servers: - url: https://api.cadanapay.com description: Prod Server - url: https://dev-api.cadanapay.com description: Dev Server security: - Authorization: [] tags: - name: Custom Auth description: APIs for interacting with Custom Authentication - name: Persons description: APIs for interacting with the HR module - name: Milestones description: APIs for milestone-based contractor pay - name: Instant Pay description: APIs for interacting with Instant Pay functionality - name: Users description: APIs for interacting with employee/contractor Cadana accounts - name: Files description: APIs for interacting with file uploads - name: Payrolls description: APIs for interacting with Payroll - name: Platform description: Platform APIs for interacting with businesses - name: Businesses description: APIs for interacting with Business - name: Treasury description: APIs for business balances, funding, and withdrawals - name: KYB description: APIs for business verification - name: Terms description: >- APIs for the business terms catalog and recording a business's acceptance of terms - name: Contracts description: APIs for interacting with contracts - name: Sandbox description: APIs for relevant sandbox simulations - name: Invoices description: APIs for interacting with invoices - name: Reimbursements description: APIs for interacting with reimbursements - name: Entities description: >- APIs for managing legal sub-entities (subsidiaries, branches) under a parent business paths: /v1/terms: get: tags: - Terms summary: List Terms description: >- Returns the catalog of business terms, each with the `name` and `version` a business accepts through [Accept Business Terms](/api-reference/workforce/terms/accept-business-terms). Pass `product` to get only the terms required for that product; omit it to get the full catalog. Always read term names and versions from this endpoint rather than hard-coding them — when a version changes, a business has to accept the new version. operationId: listTerms parameters: - $ref: '#/components/parameters/XMultiTenantKey' - name: product in: query required: false description: >- Return only the terms required for this product. `general` returns `PRIVACY_NOTICE`, `FUNDS_AVAILABILITY_DISCLOSURE`, and `ACH_AUTHORIZATION`; `virtual-accounts` returns those plus `STRIPE_TERMS`. Omit to return the full catalog. schema: type: string enum: - general - virtual-accounts - name: countryCode in: query required: false description: >- ISO 3166-1 alpha-2 country code used to select a country-specific set of terms for the given `product`. No country-specific sets are configured today, so every country gets the product's standard terms. Ignored when `product` is omitted. schema: type: string example: US responses: '200': $ref: '#/components/responses/ListTermsResponse' '400': description: Unknown `product`. content: application/json: schema: $ref: '#/components/schemas/BadRequestError' example: code: invalid_request_body message: >- One or more input values are invalid. Please re-enter valid values params: product: 'unknown product, valid products: general, virtual-accounts' 5XX: $ref: '#/components/responses/InternalError' security: - Authorization: [] components: parameters: XMultiTenantKey: name: X-MultiTenantKey in: header required: false schema: type: string description: >- Required when using a Platform API token. The tenant key identifying which business to operate on. responses: ListTermsResponse: description: list terms response content: application/json: schema: type: array items: $ref: '#/components/schemas/Term' example: - name: PRIVACY_NOTICE displayName: Privacy Notice version: '2026-05-21' url: https://assets.cadanapay.com/terms/privacy-notice/2026-05-21.pdf scopes: - business - name: FUNDS_AVAILABILITY_DISCLOSURE displayName: Funds Availability Disclosure version: '2026-07-29' url: >- https://assets.cadanapay.com/terms/funds-availability-disclosure/2026-07-29.pdf scopes: - business - name: ACH_AUTHORIZATION displayName: ACH Authorization version: '2026-07-29' url: >- https://assets.cadanapay.com/terms/ach-authorization/2026-07-29.pdf scopes: - business - name: STRIPE_TERMS displayName: Stripe Terms version: '2026-07-29' url: >- https://docs.stripe.com/treasury/connect/compliance#treasury-terms scopes: - business InternalError: description: Internal error content: application/json: schema: $ref: '#/components/schemas/InternalError' schemas: BadRequestError: description: Bad input provided by client allOf: - $ref: '#/components/schemas/Error' - type: object properties: params: description: A map for meta data around the error that occurred type: object example: code: invalid_request_body message: The request body provided is not valid params: field: Value is invalid. Term: type: object properties: name: type: string description: >- Term identifier. Send it as `type` when accepting the term and in `termsType` when checking acceptance. example: PRIVACY_NOTICE displayName: type: string description: Human-readable name to show alongside the document example: Privacy Notice version: type: string description: >- The term's current version. Send it as `version` when accepting the term; only acceptance of this version counts. example: '2026-05-21' url: type: string description: Link to the document for this version example: https://assets.cadanapay.com/terms/privacy-notice/2026-05-21.pdf scopes: type: array items: type: string example: - business Error: type: object properties: code: description: A machine parsable error code type: string enum: - invalid_request_body - resource_not_found - forbidden - internal_error message: description: A human readable message describing the error type: string InternalError: description: Internal server error allOf: - $ref: '#/components/schemas/Error' example: code: internal_error message: An unexpected error occurred. Please try again later. securitySchemes: Authorization: type: http scheme: bearer bearerFormat: API_SECRET_KEY ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.