The legal BS. We are not affiliated with the NFL.
Mandy is the Organizer.
She loads the 272 NFL games into the Calendar Invite Server using her Google Calendar client by sending them to create@calendarsnack.com. This is an API endpoint we call the Inbound Processor.
It is a bundle of processes for multiple organizers to drop off Calendar Event data from their Calendar Clients, for disassembly and storage for future use.
The Calendar event data is used by the Calendar Invite Server APIs to display event data in the analytics console and to support the messaging pipeline for sending, updating, deleting, and tracking Calendar Invites from the Rest API.
Mandy reviews the game data in her Calendar Invite Server Console using the Calendarsnack App.
She edits the NFL game events in her Calendar Client, which is attached to the calendar invite server, and saves them to the email address create@calendarsnack.com, which sends them back to the Inbound Processor for ETL and storage.
In this demo, the Calendarsnack App and NFL Demo App use the same APIs to drive data to their respective applications, using Mandy’s NFL demo game data.
Mandy shares the NFL Page with Greg a customer.
Greg reviews the games by clicking through the NFL schedule and selects the games from week 16.
He enters his email address and clicks the button to receive the calendar invites for four games that Sunday.
The Outbound Processor calls the Calendar Invite Messaging pipeline REST API, reassembles the calendar invite data for that UID, builds a calendar invite for that game, and sends it to the requester’s email address.
Greg gets the calendar invites to his email address and see’s them in his google mail and calendar clients as a calendar invitation.
He says Yes to a few and maybe to one.
The calendar receipt data is sent back to the calendar invite server API Gateway for calendar receipt collection storage and analytics.
The Outbound Processor is a Rest API that is embedded into the web pages of the custom NFL demo application sends, tracks, updates and deletes the calendar invites.
Above is the workflow of how the Calendar Invite Server API’s serve up the data collection from various calendar invite campaigns into the reporting displays for Mandy the Organizer using the CalendarSnack App.
Mandy navigates to the December 21st week to view the calendar invite campaign data collected from the calendar clients of customers for this particular day.
Mandy is able to use the calendarsnack reporting panels to drill down into the NFL game Day for Sunday, 12/21/25. Or Week 16.
Then, into the specifics of Sunday for the New York Giants vs. Minnesota Vikings - NFL 2025 Round 16 - 12/21.
Mandy sees Calendar Invite Data for the New York Giants vs Minnesota Vikings - NFL 2025 Round 16 and decides to change the calendar invite messaging to include a promotion of “Stop by our Surprise Vendor Booth 983 at the NFL Game and get a free $125 Valued NFL Jersey”.
The promotion update will be sent to those customers who have already responded Y or M to the Calendar Invite from Mandy sent by the Calendar Invite Server.
Greg has the calendar invite shown above in his Google Calendar. It was sent by the Outbound processor on the Calendar Invite Server, which is hooked to the NFL Demo Landing Page Schedule.
It is a series of functions that make up the REST API for sending calendar invites when called with a UID in WebPages, like the NFL demo.
It matches the Email address with the UID, sends the calendar invite, and tracks calendar receipts from customers’ calendar clients (Y, N, or M) by requesting them to be sent back to the API Gateway for storage and analytics.
Mandy changes the data in her Calendar Client for the New York Giants vs Minnesota Vikings - NFL 2025 Round 16 and its resent to the Inbound processor.
That data is disassembled, stored, and called by the Outbound processor, which is a series of functions that reassemble the updated data and send the calendar invite Update to those customers who have responded Y or M to the previous calendar invite.
Mandy can edit and update any parts of her Calendar Client for the Event as needed and resend to the Calendar Invite Server.
NERD ALERT - How Calendar Receipt data Collection works.
Each Calendar Invitation sent by the Calendar Invite Server includes a UID request parameter that requests calendar receipt data be sent back to the API Gateway for storage and analytics.
The customers’ calendar clients are monitored, and data is collected and updated in the database whenever a customer changes the status to Y, N, or M.
Ok, this is a wrap-up for this post on Dec 16, 2025.
