A person data generator creates synthetic person records containing a name, gender, birth date and age. The records are realistic-looking but entirely fictional — no real individuals are represented. They are designed for test databases, prototype UIs, and automated test suites where production data cannot be used.Documentation Index
Fetch the complete documentation index at: https://docs.spotzee.com/llms.txt
Use this file to discover all available pages before exploring further.
Generate sample person records at spotzee.com/tools/person-generator. Enter a count and locale, then click Generate. Use this guide for integration patterns and locale details.
Why this matters
Using production person data in development and test environments creates compliance exposure under GDPR, CCPA, and similar regulations. Synthetic data that looks realistic eliminates the risk without sacrificing the realism needed for UI and integration testing. Test suites that rely on hardcoded names like “John Doe” or “Test User” are fragile. They break when code checks for specific formats or lengths. Generated data with varied names, birth dates, and ages exercises edge cases that uniform placeholders miss. Each call to the Extended API version deducts a small per-call amount from your Spotzee credit balance. See the Spotzee pricing page for live figures.How it works
Send the request
POST to
/generic/data/generate/person with a count (1-100, as a string) and an optional locale (default en).Name generation
The API generates first and last names appropriate for the selected locale. English produces Anglo-Saxon names; Spanish, French, and German produce locale-appropriate equivalents.
Demographic data
Gender is randomly assigned. A birth date is randomly selected, and the corresponding age is calculated at the time of generation.
What to watch for
Three patterns require attention when integrating generated person data.- Count outside 1–100. The API accepts between 1 and 100 records per request. For larger datasets, call the endpoint multiple times. Each call returns independent random records.
- Locale not matching expected character set. The English locale produces Latin-script names. If your test environment needs to exercise Unicode handling, select a locale with appropriate character coverage.
- Age and birth date consistency. Age is calculated at generation time. If a test relies on a specific age range, filter the results client-side or use the date generator with the
birthdatemethod for more control.
FAQs
Is the generated person data real?
Is the generated person data real?
No. All records are synthetically generated and do not correspond to any real individual. The data is safe to use in test environments without GDPR or CCPA exposure.
Can I generate person data with email addresses?
Can I generate person data with email addresses?
The person generator returns name, gender, birth date and age. For email addresses and website URLs, use the contact generator. Combine both generators to build richer test person records.
How do I generate more than 100 records?
How do I generate more than 100 records?
The web tool and API both cap at 100 records per request. For larger datasets, call the endpoint in a loop. Each call returns a fresh, independent set of records — no pagination or cursor is needed.
Which locales are supported?
Which locales are supported?
The
locale parameter accepts IETF locale codes: en (English), es (Spanish), fr (French), de (German), pt_BR (Brazilian Portuguese), zh_CN (Simplified Chinese), and others. Unsupported locales fall back to en.Where can I learn more about generating test data?
Where can I learn more about generating test data?
Read this guide for person-specific patterns, then explore the contact generator guide, name generator guide, and date generator guide to combine all four into a complete test dataset.