---
title: "Update Email Settings"
method: PUT
path: "/company-email-settings"
tags: ["company-email-settings"]
---

# Update Email Settings

`PUT /company-email-settings`

Write the company's email branding, creating the row on first save.

Applies to email sent from here on; mail already delivered keeps the
branding it was rendered with.

## Request body

- CompanyEmailSettingsUpdate — Request body for the company's email branding. The whole configuration, not one named field: the settings page sends the state it wants, so a new setting is a field here rather than an endpoint.
  - `reply_to_email` string, email, required
  - `use_company_icon` boolean

## Response `200`

Successful Response

- CompanyEmailSettingsResponse — The company's email branding, as the settings page renders it. Unlike the document-settings response this one *can* be empty — a company that has never configured branding has no reply-to to invent, and the page needs to know that so it presents the form as unsaved rather than as holding a value nobody chose. ``configured`` says which state this is.
  - `configured` boolean, required
  - `reply_to_email` string, nullable, required
  - `use_company_icon` boolean, required
  - `logo_url` string, nullable, required
  - `custom_logo_url` string, nullable, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/kobaltlabs/apis/fastapi.md) · [All operations](https://skmtc.dev/kobaltlabs/apis/fastapi/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/kobaltlabs/fastapi/revisions/3ff4c0bd276b/schema)