Run this generator at /tools/person-generator.
Why this matters
Production records do not belong in development databases, demo screens or automated test fixtures. Synthetic person data gives your team realistic profiles without copying customer names, dates of birth or profile attributes into places where they are harder to control. Hardcoded names like “John Doe” hide layout, sorting and validation problems. As a synthetic data generator endpoint, localised records with optional middle names, prefixes, suffixes and profile fields create better fixtures because they exercise longer strings, diacritics, optional fields and seeded test runs. Extended API calls use your Spotzee credit balance. See live per-tool pricing on the Spotzee pricing page.How it works
1
Send the request
POST to
/generic/data/generate/person with a count from 1 to 100, plus optional locale, seed, gender and include flags.2
Choose generation options
Use
locale for name style, gender for male or female name selection, and seed to repeat the random sequence. Birth dates and ages can change as the current date changes. Common locale values include en, es, fr, de, pt and zh.3
Add optional fields
Set
includeJobTitle, includeJobDetails, includeBiography, includeMiddleName, includePrefixSuffix or includePersonalDetails to true when your fixture needs those fields.4
Read the records
Use the response as test person data generator output. It returns
data.persons[], with each record containing firstName, lastName, fullName, gender, birthDate and age, plus any optional fields you requested.What to watch for
- Count outside
1to100. The API accepts up to 100 records per request. For larger datasets, call the endpoint multiple times. - Blank locale. A blank locale defaults to
en. Enter a locale code when you need language-specific names or character coverage. - Missing optional fields. Job details, biographies, middle names, prefixes, suffixes, gender identity and zodiac signs only appear when their matching include option is set to
true. - Invalid seed. Seeds must be whole numbers. Leave the field blank for random output, or reuse the same seed for repeatable fixtures.
- Strict age ranges. The person endpoint returns generated birth dates and ages. If a test needs a specific age band, combine this tool with the date generator’s birthdate methods.
FAQs
Is generated person data real?
Is generated person data real?
No. Generated person data is synthetic sample data and does not represent real people. Use it in development databases, product demos and automated tests instead of copying production records.
What fields can a person data generator return?
What fields can a person data generator return?
The person data generator always returns name, gender, birth date and age fields. You can also request middle names, prefixes, suffixes, job titles, job details, biographies, gender identity and zodiac signs. Optional fields only appear when you request them.
Can I use the person generator online for repeatable fixtures?
Can I use the person generator online for repeatable fixtures?
A numeric seed repeats the random sequence for the same count, locale and options. Birth dates and ages depend on the current date, so do not expect identical profiles across dates. Leave the seed blank for exploratory records.
Can I generate person data with email addresses?
Can I generate person data with email addresses?
The person data generator focuses on profile fields, not email addresses. Use the contact generator for synthetic email addresses, websites, usernames and social profile fields. Combine both tools when you need CRM-style test records.
How do I generate more than 100 person records?
How do I generate more than 100 person records?
Call the Extended API endpoint in a loop. Each request accepts up to 100 records and can reuse the same options. Change the seed between requests when you need distinct batches; dates and ages can still depend on the current date.
Where can I learn more about person data generation?
Where can I learn more about person data generation?
This page covers the person endpoint. For adjacent workflows, read the contact generator guide, name generator guide, and date generator guide.