MailDeltaFetch

Summary

  • Combines Microsoft Graph delta tracking with full message retrieval so clients receive every new or updated mail (including body content) since their last stored delta token.

  • createdDateTime is returned for each message so consumers can quickly separate brand-new items from updates to existing ones.

Graph Endpoint

  • GET /me/messages/delta

  • GET /me/messages/{id}

Parameters

Required

  • mailDelta: string — Delta token from a prior MailDeltaFetch or MailInitDelta call. Use this to resume change tracking.

Optional

  • deltaLink: string — Legacy alias for mailDelta. Only one of mailDelta or deltaLink is needed.

  • folder: string — Folder ID or well-known name (e.g., Inbox). Used when starting without a token or when the token becomes invalid.

Usage (app.businessFunction)

Minimal

With options

Response

  • Returns the full messages (same shape as MailGet) plus the next delta token to persist for the following call.

Notes

  • Use MailInitDelta to bootstrap the first mailDelta token. Afterwards, persist the deltaLink returned by each MailDeltaFetch.

  • Messages marked as removed by Microsoft Graph are skipped; clients should continue to rely on MailDelta if they need delete notifications.

  • If the delta token is expired or invalid, the operation throws a friendly error so callers can fall back to MailInitDelta.

  • createdDateTime stays constant for the lifetime of a message, allowing consumers to ignore older mails that were only modified (e.g., read/unread changes) while still upserting updates where needed.

Last updated

Was this helpful?