---
title: "Create Terms and Conditions event"
method: POST
path: "/v1/terms_and_conditions_events"
tags: ["Terms and Conditions events"]
---

# Create Terms and Conditions event

`POST /v1/terms_and_conditions_events`

Records an instance of a customer (i.e., a person or a person on behalf of a business) accepting or rejecting a Solaris Terms and Conditions document.

## Request body

- object
  - `document_id` string, required — A 36-character hex encoded UID that corresponds with the relevant document. Solaris will provide these IDs.
  - `event_timestamp` string, date-time, required — UTC timestamp of when the customer approved/rejected the document. Format: YYYY-MM-DDTHH:MM:SSS
  - `event_type` 'APPROVED' | 'REJECTED', required — The type of action that the customer took on the Terms & Conditions document.
  - `signed_by` string, required — ID of the person who signed the Terms & Conditions document.
  - `signed_on_behalf_of` string — (For business customers) ID of the business on whose behalf the authorized person or legal representative is approving/rejecting the Terms & Conditions.
  - `product_name` 'DIGITAL_BANKING' | 'OVERDRAFT' | 'VIACASH' | 'SECURITIES_BROKERAGE' | 'IDENTIFICATION_FOURTHLINE', required — The name of the relevant product to which the Terms & Conditions document applies.

## Response `201`

Successful operation

- TermsAndConditionsEvent
  - `id` string — ID of the Terms & Conditions event.
  - `event_timestamp` string, date-time — Timestamp when the customer approved/rejected the Terms & Conditions document.
  - `created_at` string, date-time — Timestamp when the Terms & Conditions event was created using the API.
  - `event_type` 'APPROVED' | 'REJECTED' — The type of action that the customer took on the Terms & Conditions document.
  - `signed_by` string — ID of the person who approved/rejected the Terms & Conditions document.
  - `signed_on_behalf_of` string — ID of the business on whose behalf the authorized person or legal representative approved/rejected the Terms & Conditions document.
  - `product_name` 'DIGITAL_BANKING' | 'OVERDRAFT' | 'VIACASH' | 'SECURITIES_BROKERAGE' | 'IDENTIFICATION_FOURTHLINE' — The name of the relevant product to which the Terms & Conditions document applies.
  - `document_id` string — ID of the Terms & Conditions document that the customer approved/rejected.
  - `document_name` string — Name of the Terms & Conditions document that the customer approved/rejected.

## Other responses

- `400` — An error occurred on the client side.
- `403` — You are not authorized to perform this action.
- `409` — The customer has already approved the Terms & Conditions document (i.e., idempotency conflict).
- `500` — Internal server error.

---

[API](https://skmtc.net/solarisgroup/apis/compliance-features.md) · [All operations](https://skmtc.net/solarisgroup/apis/compliance-features/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/solarisgroup/compliance-features/revisions/61701b027c74/schema)