Nylas · Schema

Nylas thread.replied notification object

Sent when a participant replies to a tracked email thread. This schema describes `data.object` inside the Nylas notification envelope.

CalendarCommunicationsContactsEmailMessagingSchedulingA2A

Properties

Name Type Description
object string Always `thread`.
grant_id string The grant ID that owns the tracked thread.
message_id string The ID of the reply message.
root_message_id string The ID of the original tracked message that was replied to.
label string The tracking label you assigned when sending the original message.
reply_data object Aggregate reply data.
sender_app_id string The Nylas application ID that sent the tracked message.
thread_id string The thread ID containing the reply.
timestamp integer Unix timestamp of the reply.
reply_to_message_id string The message ID that was replied to.
from_self boolean Whether the reply was sent by the tracked message sender.
View JSON Schema on GitHub

JSON Schema

nylas-thread-replied.schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/nylas/refs/heads/main/json-schema/nylas-thread-replied.schema.json",
  "title": "Nylas thread.replied notification object",
  "description": "Sent when a participant replies to a tracked email thread. This schema describes `data.object` inside the Nylas notification envelope.",
  "type": "object",
  "properties": {
    "object": {
      "type": "string",
      "description": "Always `thread`.",
      "enum": [
        "thread"
      ]
    },
    "grant_id": {
      "type": "string",
      "description": "The grant ID that owns the tracked thread."
    },
    "message_id": {
      "type": "string",
      "description": "The ID of the reply message."
    },
    "root_message_id": {
      "type": "string",
      "description": "The ID of the original tracked message that was replied to."
    },
    "label": {
      "type": "string",
      "description": "The tracking label you assigned when sending the original message."
    },
    "reply_data": {
      "type": "object",
      "description": "Aggregate reply data.",
      "properties": {
        "count": {
          "type": "integer",
          "description": "Total number of replies to the tracked thread."
        }
      }
    },
    "sender_app_id": {
      "type": "string",
      "description": "The Nylas application ID that sent the tracked message."
    },
    "thread_id": {
      "type": "string",
      "description": "The thread ID containing the reply."
    },
    "timestamp": {
      "type": "integer",
      "description": "Unix timestamp of the reply."
    },
    "reply_to_message_id": {
      "type": "string",
      "description": "The message ID that was replied to."
    },
    "from_self": {
      "type": "boolean",
      "description": "Whether the reply was sent by the tracked message sender."
    }
  },
  "required": [
    "message_id",
    "root_message_id"
  ],
  "x-nylas-trigger": "thread.replied",
  "x-nylas-category": "Message Tracking",
  "x-provenance": {
    "method": "authored",
    "publisher": "Nylas",
    "source": "https://developer.nylas.com/docs/reference/notifications/message-tracking/thread-replied/",
    "derived_from": "nylas/developer.nylas.com@a7995fb6:src/_component-data/notification-schemas.json",
    "generated": "2026-09-28"
  },
  "examples": [
    {
      "object": "thread",
      "grant_id": "<NYLAS_GRANT_ID>",
      "message_id": "<message-id-of-reply>",
      "root_message_id": "<message-id-of-original-tracked-message>",
      "label": "some-client-label",
      "reply_data": {
        "count": 1
      },
      "reply_to_message_id": "<message-id-of-original-tracked-message>",
      "from_self": false,
      "sender_app_id": "<app-id>",
      "thread_id": "<thread-id-of-sent-message>",
      "timestamp": 1696007157
    }
  ]
}

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/nylas-thread-replied.schema"
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.