What is the Contact Cards mock data preset useful for?
The Contact Cards preset creates professional contact records with names, job titles, companies, emails, avatars, locations, and favorite status for address books and CRM interfaces.
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 Contact Cards preset creates professional contact records with names, job titles, companies, emails, avatars, locations, and favorite status for address books and CRM interfaces.
The Contact Cards preset includes these top-level fields: id, fullName, jobTitle, companyName, email, avatarUrl, city, country, isFavorite. You can rename, remove, or extend the fields before generating data, including nested objects and arrays where supported.
Use it to test contact grids, alphabetical sorting, company and location filters, favorite contacts, avatar fallbacks, search, and responsive card layouts.
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;
name: string;
username: string;
email: string;
avatarUrl: string;
jobTitle: string;
isActive: boolean;
createdAt: string;
}{
id: string;
employeeNumber: string;
profile: {
fullName: string;
workEmail: string;
avatarUrl: string;
city: string;
country: string;
};
position: {
jobTitle: string;
department: string;
employmentType: string;
managerId: string;
};
compensation: {
annualSalary: string;
currency: string;
};
startedAt: string;
isActive: boolean;
}{
id: string;
title: string;
description: string;
startsAt: string;
endsAt: string;
timeZone: string;
isAllDay: boolean;
location: string;
conferenceUrl: string;
organizer: {
name: string;
email: string;
};
attendees: {
id: string;
name: string;
email: string;
hasAccepted: boolean;
}[];
}