> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-legal-documents/terms-and-conditions-1.md).

# Terms And Conditions

## Get terms and conditions

> Retrieve all terms and conditions applicable to the specified merchant.

```json
{"openapi":"3.0.1","info":{"title":"External US Onboarding Workflow","version":"0.0.1"},"paths":{"/api/legaldocuments/v1/TermsAndConditions/{merchantNumber}":{"get":{"tags":["Terms And Conditions"],"summary":"Get terms and conditions","description":"Retrieve all terms and conditions applicable to the specified merchant.","parameters":[{"name":"merchantNumber","in":"path","description":"The merchant's unique identification number.","required":true,"schema":{"type":"string"}},{"name":"shouldMaskSensitiveData","in":"query","description":"Indicates whether sensitive data should be masked in the response.","schema":{"type":"boolean","default":true}}],"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TermsAndConditionsCollection"}}}},"500":{"description":"Server Error","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResults"}}}}}}}},"components":{"schemas":{"TermsAndConditionsCollection":{"type":"object","properties":{"content":{"type":"array","items":{"$ref":"#/components/schemas/TermsAndConditions"},"nullable":true}},"additionalProperties":false},"TermsAndConditions":{"type":"object","properties":{"termsAndConditionsID":{"type":"integer","description":"Deprecated identifier for terms and conditions. Values may differ between Sandbox and Production. Use typeID instead.","format":"int32"},"typeID":{"type":"integer","description":"Identifier for a specific set of terms and conditions. When programming against the terms and conditions endpoints this identifier should be used to select the desired set of terms and conditions.","format":"int32"},"text":{"type":"string","description":"A string containing the terms and conditions in an HTML format. Can be used for displaying the terms and conditions on a website.","nullable":true},"effectiveDateUTC":{"type":"string","description":"The UTC date when these terms and conditions went into effect.","format":"date-time"}},"additionalProperties":false},"ErrorResults":{"type":"object","properties":{"errors":{"type":"array","items":{"$ref":"#/components/schemas/BoardingError"},"nullable":true}},"additionalProperties":false},"BoardingError":{"type":"object","properties":{"errorMessage":{"type":"string","nullable":true},"resultCode":{"type":"integer","format":"int32"},"timeStamp":{"type":"string","format":"date-time","readOnly":true},"fieldPath":{"type":"array","items":{"type":"string"},"nullable":true}},"additionalProperties":false}}}}
```

## Get terms and conditions by type ID

> Retrieve the terms and conditions entry associated with the specified merchant and type ID.

```json
{"openapi":"3.0.1","info":{"title":"External US Onboarding Workflow","version":"0.0.1"},"paths":{"/api/legaldocuments/v1/TermsAndConditions/{merchantNumber}/{typeID}":{"get":{"tags":["Terms And Conditions"],"summary":"Get terms and conditions by type ID","description":"Retrieve the terms and conditions entry associated with the specified merchant and type ID.","parameters":[{"name":"merchantNumber","in":"path","description":"The merchant's unique identification number.","required":true,"schema":{"type":"string"}},{"name":"typeID","in":"path","description":"The unique identifier of the terms and conditions type.","required":true,"schema":{"type":"integer","format":"int32"}},{"name":"shouldMaskSensitiveData","in":"query","description":"Indicates whether sensitive data should be masked in the response.","schema":{"type":"boolean","default":true}}],"responses":{"200":{"description":"Success","content":{"application/json":{"schema":{"$ref":"#/components/schemas/TermsAndConditions"}}}},"500":{"description":"Server Error","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ErrorResults"}}}}}}}},"components":{"schemas":{"TermsAndConditions":{"type":"object","properties":{"termsAndConditionsID":{"type":"integer","description":"Deprecated identifier for terms and conditions. Values may differ between Sandbox and Production. Use typeID instead.","format":"int32"},"typeID":{"type":"integer","description":"Identifier for a specific set of terms and conditions. When programming against the terms and conditions endpoints this identifier should be used to select the desired set of terms and conditions.","format":"int32"},"text":{"type":"string","description":"A string containing the terms and conditions in an HTML format. Can be used for displaying the terms and conditions on a website.","nullable":true},"effectiveDateUTC":{"type":"string","description":"The UTC date when these terms and conditions went into effect.","format":"date-time"}},"additionalProperties":false},"ErrorResults":{"type":"object","properties":{"errors":{"type":"array","items":{"$ref":"#/components/schemas/BoardingError"},"nullable":true}},"additionalProperties":false},"BoardingError":{"type":"object","properties":{"errorMessage":{"type":"string","nullable":true},"resultCode":{"type":"integer","format":"int32"},"timeStamp":{"type":"string","format":"date-time","readOnly":true},"fieldPath":{"type":"array","items":{"type":"string"},"nullable":true}},"additionalProperties":false}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-legal-documents/terms-and-conditions-1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.