Random User Generator
Pricing
from $10.00 / 1,000 results
Pricing
from $10.00 / 1,000 results
Rating
0.0
(0)
Developer

Taher Ali Badnawarwala
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
20 days ago
Last modified
Categories
Share
TL;DR
- Input: Count (1–100), gender, nationalities, include/exclude fields
- Output: Random user profiles in dataset (name, email, location, picture, login, etc.)
- Use it for: Testing, demos, seed data, staging, automation
- Result time: Usually under 10 seconds
Table of contents
- Try it now
- Overview
- Usage examples
- Features
- Configuration
- Usage
- Output
- For bloggers & tutorial writers
- Integration
- Technical details
- FAQ
- Resources
Try it now
| Action | Link |
|---|---|
| Run in Apify Console | Open Actor → Start |
| API (sync) | POST https://api.apify.com/v2/acts/YOUR_USERNAME~random-user-generator-apify/run-sync |
Replace YOUR_USERNAME with your Apify username.
Overview
The Random User Generator fetches random user data from the MultipleWords API. You set how many users to generate (1–100), optional filters (gender, nationalities), and which fields to include or exclude. The Actor returns structured JSON: name, email, location, phone, picture URLs, login, and more.
This Actor is useful when you need realistic user-like data at scale or as part of an automated workflow.
Common use cases
| Category | Examples |
|---|---|
| Development | Seed databases, test sign-up flows, mock user lists |
| QA & testing | Test forms, profile pages, A/B tests with varied user data |
| Demos | Populate dashboards, sample user tables, prototype UIs |
| Automation | Feed user data into Make, Zapier, or custom pipelines |
Note: Data is generated by the upstream API. Review API terms before heavy or commercial use.
Usage examples
Paste these into the Actor input or API request body.
| Scenario | Input |
|---|---|
| 10 users, both genders | { "count": 10, "gender": "both" } |
| Female users, AU & US | { "count": 5, "gender": "female", "nationalities": "AU" } (or use enum value for US) |
| Name, email, picture only | { "count": 20, "inc": ["name", "email", "picture"] } |
| Exclude login & id | { "count": 10, "exc": ["login", "id"] } |
Features
- Generate 1–100 random user profiles per run
- Filter by gender (male, female, both) and nationalities
- Include or exclude fields (gender, name, location, email, login, registered, dob, phone, cell, id, picture, nat)
- Clean JSON output for easy integration
- Standby mode with HTTP API (POST /) and batch mode from storage
- Input validation and error handling
- Runs on Apify (Console, API, automation tools)
Configuration
All settings are provided via the Actor input.
Input parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
count | integer | No | 10 | Number of random users to generate (1–100) |
gender | string | No | both | Filter by gender: male, female, both |
nationalities | string | No | (any) | Nationality code(s), e.g. AU, US, GB (see schema enum) |
inc | array | No | (all) | Fields to include only (e.g. name, email, picture) |
exc | array | No | (none) | Fields to exclude (e.g. login, id) |
passwordMinLength | integer | No | 8 | Min password length for validation |
passwordMaxLength | integer | No | 18 | Max password length for validation |
passwordRequireUppercase | boolean | No | true | Require at least one uppercase letter |
passwordRequireLowercase | boolean | No | true | Require at least one lowercase letter |
passwordRequireSymbol | boolean | No | true | Require at least one symbol |
passwordRequireRange | boolean | No | true | Require length between min and max |
Example input
{"count": 10,"gender": "female","nationalities": "AU","inc": ["name", "email", "picture", "location"]}
Usage
Apify Console
- Open the Actor in Apify Console.
- Set Count, Gender, Nationality, and optionally Include fields or Exclude fields.
- Click Start and check the Output tab for the random user dataset (table with Photo, Name, Email, etc.).
API (run-sync)
Replace YOUR_USERNAME with your Apify username and YOUR_API_TOKEN with your Apify API token.
curl -X POST "https://api.apify.com/v2/acts/YOUR_USERNAME~random-user-generator-apify/run-sync?token=YOUR_API_TOKEN" \-H "Content-Type: application/json" \-d '{"count": 5, "gender": "female", "inc": ["name", "email", "picture"]}'
Response includes runId, status, and dataset items with user objects (name, email, picture, etc.).
HTTP API (standby mode)
When the Actor runs in standby mode, POST to the root path:
curl -X POST http://localhost:8080/ \-H "Content-Type: application/json" \-d '{"count": 5, "gender": "male", "nationalities": "US", "inc": ["name", "email", "picture"]}'
Replace localhost:8080 with the Actor container URL when run on Apify.
Output
Each run writes one item per generated user to the default dataset. The Actor has an output schema so the Apify Console shows results in organized tables with clear field names and types.
Output fields (dataset item)
| Field | Description |
|---|---|
gender | male or female |
name | title, first, last |
location | street, city, state, country, postcode, coordinates, timezone |
email | Email address |
login | uuid, username, password hashes (when not excluded) |
registered | Registration date and age |
dob | Date of birth and age |
phone, cell | Phone numbers |
id | ID name and value |
picture | large, medium, thumbnail image URLs |
nat | Nationality code |
Example output (dataset item)
{"gender": "female","name": {"title": "Ms","first": "Emma","last": "Wilson"},"location": {"street": { "number": 1234, "name": "Main St" },"city": "Sydney","state": "New South Wales","country": "Australia","postcode": "2000","coordinates": { "latitude": "-33.8688", "longitude": "151.2093" },"timezone": { "offset": "+10:00", "description": "Eastern Australia" }},"email": "emma.wilson@example.com","picture": {"large": "https://...","medium": "https://...","thumbnail": "https://..."},"nat": "AU"}
In the Apify Console Output tab you can open Random users (overview) or Full dataset as defined in the output schema. Fields like Photo and Email are shown in a table for easy reading.
For bloggers & tutorial writers
You can use this Actor in tutorials, blog posts, or videos without running it first:
- Input: Use the Example input or Usage examples table, or the ready-to-use JSON files in the Example/ folder (
input-basic.json,input-female-au.json,input-fields-only.json). - Output: Use the Example output above to show what users get.
- API: Use the API (run-sync) or HTTP API (standby mode) examples; remind readers to replace
YOUR_USERNAMEandYOUR_API_TOKEN.
For promotion ideas, copy-paste posts, and where to share, see PROMOTION.md in this repo.
Integration
- Make (Integromat) — Use the Apify module and select this Actor; map count, gender, nationalities, and inc/exc to inputs.
- Zapier — Use the Apify Zapier app and choose "Run Actor"; select this Actor and pass the input JSON.
- Custom apps — Call the Apify API (
/runor/run-sync) or the standby HTTP API with the same input JSON.
Technical details
- Runtime: Node.js (see Dockerfile).
- Input: Validated against the input schema; invalid input returns a clear error.
- Output schema: Defined in
.actor/output_schema.json; Console uses it to display dataset and overview links. - External API: MultipleWords random users API; failures are logged and surfaced to the user.
- Standby mode: HTTP server on port 8080 with readiness probe (
x-apify-container-server-readiness-probe).
FAQ
How long does a run take?
Usually under 10 seconds for up to 100 users.
Can I get more than 100 users in one run?
No. Count is capped at 1–100 per run. For more users, run the Actor multiple times or use pagination (same seed for reproducibility).
Where is the data from?
The MultipleWords random users API. Data is fake but realistic (names, addresses, etc.).
Do I need an API key for the random users API?
The Actor uses its own integration; you only need your Apify account and (for API calls) your Apify API token.
What is the output schema?
The output schema (.actor/output_schema.json) tells Apify Console where your dataset is and how to show it (e.g. "Random users" overview table, "Full dataset" link). All Actors should have one so users see organized results instead of raw data.
Resources
- Apify Console — Run the Actor and view datasets
- Apify API — Run actors programmatically
- Example/ — Ready-to-use input JSON files for demos, tutorials, and blog posts
- Output schema docs — Define and present Actor output
- PROMOTION.md — How to promote this Actor and grow your user base
- .actor/CHANGELOG.md — Version history
Built with Apify SDK