# Create Terms and Conditions event 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. Endpoint: POST /v1/terms_and_conditions_events Version: 1.0 ## Request fields (application/json): - `document_id` (string, required) A 36-character hex encoded UID that corresponds with the relevant document. Solaris will provide these IDs. - `event_timestamp` (string, required) UTC timestamp of when the customer approved/rejected the document. Format: YYYY-MM-DDTHH:MM:SSS - `event_type` (string, required) The type of action that the customer took on the Terms & Conditions document. Enum: "APPROVED", "REJECTED" - `product_name` (string, required) The name of the relevant product to which the Terms & Conditions document applies. Enum: "DIGITAL_BANKING", "OVERDRAFT", "VIACASH", "SECURITIES_BROKERAGE", "IDENTIFICATION_FOURTHLINE" - `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. ## Response 201 fields (application/json): - `id` (string) ID of the Terms & Conditions event. Example: "2b5423a061514901a5a8791f2cb18266" - `event_timestamp` (string) Timestamp when the customer approved/rejected the Terms & Conditions document. Example: "2020-02-12T17:28:53Z" - `created_at` (string) Timestamp when the Terms & Conditions event was created using the API. Example: "2020-02-12T17:28:53Z" - `event_type` (string) The type of action that the customer took on the Terms & Conditions document. Enum: "APPROVED", "REJECTED" - `signed_by` (string) ID of the person who approved/rejected the Terms & Conditions document. Example: "52054909a5d149b2a7430eee4ba6cc22" - `signed_on_behalf_of` (string) ID of the business on whose behalf the authorized person or legal representative approved/rejected the Terms & Conditions document. Example: "52054909a5d149b2a7430eee4ba6cc22" - `product_name` (string) The name of the relevant product to which the Terms & Conditions document applies. Enum: "DIGITAL_BANKING", "OVERDRAFT", "VIACASH", "SECURITIES_BROKERAGE", "IDENTIFICATION_FOURTHLINE" - `document_id` (string) ID of the Terms & Conditions document that the customer approved/rejected. Example: "3f31dd950cb6e2b28ac4b31d1b4bb321tcdc" - `document_name` (string) Name of the Terms & Conditions document that the customer approved/rejected. Example: "Customer T&C on Data Processing" ## Response 400 fields (application/json): - `id` (string) Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86" - `status` (string) Example: "400" - `code` (string) Example: "build_pagination_headers_failure" - `title` (string) Example: "Failed to build pagination headers." - `detail` (string) Example: "Cannot connect to database." ## Response 403 fields (application/json): - `id` (string) Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86" - `status` (string) Example: "403" - `code` (string) Example: "unauthorized_action" - `title` (string) Example: "Unauthorized Action" - `detail` (string) Example: "Unauthorized action is not allowed." ## Response 409 fields (application/json): - `id` (string) Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86" - `status` (string) Example: "409" - `code` (string) Example: "record_not_unique" - `title` (string) Example: "Record Not Unique" - `detail` (string) Example: "Could not save `terms_and_conditions_event`" ## Response 500 fields (application/json): - `id` (string) Example: "e8915041-9d8c-4d96-9dd1-04e8522ecdbf" - `status` (string) Example: "500" - `code` (string) Example: "generic_error" - `title` (string) Example: "Generic Error" - `detail` (string) Example: "There was an error."