AsyncAPI channel · Nylas · Nylas Notifications

{topicArn}

Messages published to your SNS topic; Message is the JSON envelope.

Provider: Nylas AsyncAPI: v3.0.0 Spec: Nylas Notifications Operations: 1 Messages: 53

Channel address

{topicArn}

Parameters

Operations

send
publishSnsNotification

Messages

grant.created
Sent when a user successfully authenticates with your Nylas application for the first time.
Content-Type: application/json
grant.updated
Sent when a grant is modified, updated, or re-authenticated.
Content-Type: application/json
grant.deleted
Sent when a grant is deleted because of a Delete Grant request.
Content-Type: application/json
grant.expired
Sent when a grant's credentials expire, typically due to a change in the user's password on the provider, OAuth token expiration without successful refresh, the provider revoking access, or an admin r
Content-Type: application/json
grant.imap_sync_completed
Sent when a grant is created for an IMAP account and the initial historic sync completes.
Content-Type: application/json
message.created
Sent when a new message arrives or is synced for a user.
Content-Type: application/json
message.created.cleaned
Sent when a new message is synced and the [Clean Conversations](/docs/v3/email/parse-messages/) feature is enabled for the application. The message `body` contains cleaned markdown content instead of
Content-Type: application/json
message.updated
Sent when a user modifies or updates a message.
Content-Type: application/json
message.deleted
Sent when a message is deleted.
Content-Type: application/json
message.send_success
Sent when a message is sent and delivered successfully. Fires for scheduled sends (using `send_at`), and for synchronous sends when you enable synchronous send webhooks in the Nylas Dashboard.
Content-Type: application/json
message.send_failed
Sent when a message fails to send or deliver. Fires for scheduled sends (using `send_at`), and for synchronous sends when you enable synchronous send webhooks in the Nylas Dashboard.
Content-Type: application/json
message.bounce_detected
Sent when Nylas detects a Non-Delivery Report (NDR) in the sender's inbox for a message sent via Nylas. Requires the provider to generate an NDR. Available for Google, Microsoft Graph, iCloud, and Yah
Content-Type: application/json
message.opened
Sent when a participant opens a tracked message.
Content-Type: application/json
message.link_clicked
Sent when a participant clicks a link in a tracked message.
Content-Type: application/json
thread.replied
Sent when a participant replies to a tracked email thread.
Content-Type: application/json
message.opened.legacy
Legacy format for message opened tracking notifications.
Content-Type: application/json
message.link_clicked.legacy
Legacy format for link clicked tracking notifications.
Content-Type: application/json
thread.replied.legacy
Legacy format for thread replied tracking notifications.
Content-Type: application/json
message.created.metadata
Sent for Google grants using the `/gmail.metadata` scope. Does not include `body`, `snippet`, or `attachment` fields.
Content-Type: application/json
message.updated.metadata
Sent for Google grants using the `/gmail.metadata` scope when a message is updated. Limited field set.
Content-Type: application/json
folder.created
Sent when a user creates a folder.
Content-Type: application/json
folder.updated
Sent when a user updates a folder.
Content-Type: application/json
folder.deleted
Sent when a user deletes a folder.
Content-Type: application/json
calendar.created
Sent when a user creates a calendar.
Content-Type: application/json
calendar.updated
Sent when the name, description, location, or timezone of a calendar changes.
Content-Type: application/json
calendar.deleted
Sent when a user deletes a calendar.
Content-Type: application/json
event.created
Sent when an event is created on a user's calendar.
Content-Type: application/json
event.updated
Sent when an event is modified or updated. Includes the `occurrences` parameter if the updated event is a single occurrence of a recurring Google event.
Content-Type: application/json
event.deleted
Sent when an event is deleted from a user's calendar.
Content-Type: application/json
contact.updated
Sent when a user creates or updates a contact. Most providers don't differentiate between creating and updating contacts.
Content-Type: application/json
contact.deleted
Sent when a user deletes a contact.
Content-Type: application/json
booking.created
Sent when a guest creates a booking.
Content-Type: application/json
booking.pending
Sent when a guest schedules a pending booking that requires confirmation.
Content-Type: application/json
booking.rescheduled
Sent when a guest reschedules a booking.
Content-Type: application/json
booking.cancelled
Sent when a guest cancels a booking.
Content-Type: application/json
booking.reminder
Sent at the scheduled reminder time before a booking.
Content-Type: application/json
notetaker.created
Sent when you create or schedule a Notetaker bot. For ad-hoc meetings, `join_time`, `event.ical_uid`, and `event.event_id` are omitted.
Content-Type: application/json
notetaker.updated
Sent when you update a scheduled Notetaker bot's settings or join time. Only fires while in `scheduled` state.
Content-Type: application/json
notetaker.deleted
Sent when a Notetaker bot is deleted, its associated event is cancelled, or its settings are set to null.
Content-Type: application/json
notetaker.meeting_state
Sent when the Notetaker bot transitions between meeting lifecycle states. The notification includes both a `state` field (the lifecycle phase) and a `meeting_state` field (the specific reason for the
Content-Type: application/json
notetaker.media
Sent when a recording or transcription is processing, available, or deleted. When the [retention window](/docs/v3/notetaker/retention-policies/) elapses, Nylas sends a final `notetaker.media` notifica
Content-Type: application/json
message.intelligence.order
Sent when a user receives a message with e-commerce order information.
Content-Type: application/json
message.intelligence.tracking
Sent when a user receives a message with tracking information for an e-commerce order.
Content-Type: application/json
message.intelligence.return
Sent when a user receives a message with return information for an e-commerce order.
Content-Type: application/json
message.intelligence.travel
Sent when a user receives a message with travel booking information such as flights, hotels, or car rentals.
Content-Type: application/json
message.transactional.bounced
Sent when a transactional email was not delivered due to a hard bounce.
Content-Type: application/json
message.transactional.complaint
Sent when a transactional email was delivered but the recipient marked it as spam.
Content-Type: application/json
message.transactional.delivered
Sent when a transactional email was successfully delivered to the recipient's mail server.
Content-Type: application/json
message.transactional.rejected
Sent when a transactional email was rejected because one or more attachments contained a virus.
Content-Type: application/json
message.bounced
Sent when an email was not delivered due to a hard bounce.
Content-Type: application/json
message.complaint
Sent when an email was delivered but the recipient marked it as spam.
Content-Type: application/json
message.delivered
Sent when an email was successfully delivered to the recipient's mail server.
Content-Type: application/json
message.rejected
Sent when an email was rejected because one or more attachments contained a virus.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel 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 event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel 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 channel
curl "https://apis.io/api/v1/channels/topicarn"
All event channels
curl "https://apis.io/api/v1/channels?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.