FrontApp · Schema

UpdateConversation

CompanyCommunicationsCustomer ServiceShared InboxEmailMessagingCollaborationHelp Desk

Properties

Name Type Description
assignee_id stringnull ID of the teammate to assign the conversation to. Set it to null to unassign.
inbox_id string ID of the inbox to move the conversation to.
status string New status of the conversation
status_id string Unique identifier of the status to set the conversation to. Only one of status and status_id should be provided. Ticketing must be enabled for the company to use this field.
tag_ids array List of all the tag IDs replacing the old conversation tags
description stringnull Description of the task. Only allowed on task conversations. Set to null to clear.
due_at numbernull Unix timestamp in seconds when the task is due. Must be in the future and within 50 years. Only allowed on task conversations. Set to null to clear.
custom_fields object Custom fields for this conversation. If you want to keep all custom fields the same when updating this resource, do not include any custom fields in the update. If you want to update custom fields, ma
View JSON Schema on GitHub

JSON Schema

frontapp-update-conversation-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/frontapp/main/json-schema/frontapp-update-conversation-schema.json",
  "title": "UpdateConversation",
  "x-generated": "2026-10-14",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/frontapp-core-api-openapi.yml#/components/schemas/UpdateConversation",
  "properties": {
    "assignee_id": {
      "type": [
        "string",
        "null"
      ],
      "description": "ID of the teammate to assign the conversation to. Set it to null to unassign."
    },
    "inbox_id": {
      "type": "string",
      "description": "ID of the inbox to move the conversation to."
    },
    "status": {
      "type": "string",
      "description": "New status of the conversation",
      "enum": [
        "archived",
        "open",
        "deleted",
        "spam"
      ]
    },
    "status_id": {
      "type": "string",
      "description": "Unique identifier of the status to set the conversation to. Only one of status and status_id should be provided. Ticketing must be enabled for the company to use this field."
    },
    "tag_ids": {
      "type": "array",
      "description": "List of all the tag IDs replacing the old conversation tags",
      "items": {
        "$ref": "#/$defs/ResourceID"
      }
    },
    "description": {
      "type": [
        "string",
        "null"
      ],
      "maxLength": 65535,
      "description": "Description of the task. Only allowed on task conversations. Set to null to clear."
    },
    "due_at": {
      "type": [
        "number",
        "null"
      ],
      "description": "Unix timestamp in seconds when the task is due. Must be in the future and within 50 years. Only allowed on task conversations. Set to null to clear."
    },
    "custom_fields": {
      "description": "Custom fields for this conversation. If you want to keep all custom fields the same when updating this resource, do not include any custom fields in the update. If you want to update custom fields, make sure to include all custom fields, not just the fields you want to add or update. If you send only the custom fields you want to update, the other custom fields will be erased. You can retrieve the existing custom fields before making the update to note the current fields. Send as an object of key:value pairs where the key is the custom field name and the value is the custom field value.",
      "$ref": "#/$defs/CustomFieldParameter"
    }
  },
  "$defs": {
    "CustomFieldParameter": {
      "type": "object",
      "description": "An object whose key is the `name` property defined for the custom field in the Front UI. The value of the key must use the same `type` specified for the custom field, as described in https://dev.frontapp.com/reference/custom-fields"
    },
    "ResourceID": {
      "type": "string"
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/frontapp-update-conversation"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.