What is the Calendar Events mock data preset useful for?
The Calendar Events preset generates scheduled events with start and end times, time zones, locations, conference links, organizers, and attendee responses for calendars and booking tools.
Generate API-ready mock data from this preset schema using the hosted mocking.dev faker API.
Edit, reorder, add, or remove fields before generating mock data from this preset.
This preview always requests one generated item from faker.mocking.dev, regardless of the download count.
The Calendar Events preset generates scheduled events with start and end times, time zones, locations, conference links, organizers, and attendee responses for calendars and booking tools.
The Calendar Events preset includes these top-level fields: id, title, description, startsAt, endsAt, timeZone, isAllDay, location, conferenceUrl, organizer, attendees. You can rename, remove, or extend the fields before generating data, including nested objects and arrays where supported.
Use it to test agenda and calendar views, attendee lists, all-day events, time-zone labels, conference links, acceptance states, date sorting, and event detail dialogs.
Customize the fields, row count, seed, and locale in the editor. The preview updates as you make changes, and you can download the generated records as a JSON file when the schema is ready.
Yes. mocking.dev uses Faker.js through its mock data API to generate names, emails, dates, numbers, locations, commerce data, and other realistic values. The seed makes results repeatable, while the locale controls regional data.
No. The records are synthetic and intended for development, demos, fixtures, and automated tests. Generated values can resemble real information by coincidence, so do not treat them as verified identities or use them to contact people.
{
id: string;
title: string;
description: string;
isCompleted: boolean;
priority: number;
dueAt: string;
assigneeName: string;
tags: string[];
createdAt: string;
}{
id: string;
fullName: string;
jobTitle: string;
companyName: string;
email: string;
avatarUrl: string;
city: string;
country: string;
isFavorite: boolean;
}{
id: string;
title: string;
message: string;
isRead: boolean;
actionUrl: string;
createdAt: string;
}