🔑 UUID Generator Generate universally unique identifiers (UUIDs) on demand through Apify's platform. This Actor supports multiple UUID versions, including version 1 (timestamp-based), version 4 (random), and version 5 (namespace-based), catering to a wide range of application needs. --- ## ✨ Why Use UUID Generator? - ⚡ Fast & Efficient - Generate thousands of UUIDs in seconds with optimized algorithms - 🎯 RFC Compliant - All generated UUIDs follow RFC 4122 standards for guaranteed uniqueness - 📈 Scalable - Generate from 1 to 10,000 UUIDs in a single run with bulk processing - 🔧 Multiple Versions - Choose from UUID v1, v4, or v5 to meet specific technical requirements - 📊 Flexible Output - Export UUIDs in JSON, CSV, or plain text formats for easy integration --- ## 📥 Input Parameters | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | version | String | ✅ Yes | "4" | UUID version: 1 (timestamp-based), 4 (random), or 5 (namespace-based) | | count | Integer | ✅ Yes | 100 | Number of UUIDs to generate (range: 1-10,000) | | namespace | String | ❌ No | "example.com" | Namespace for UUID version 5 (required when version is '5') | | name | String | ❌ No | "default-name" | Name for UUID version 5 (required when version is '5') | | outputFormat | String | ❌ No | "json" | Output format: json, csv, or text | > Note: For UUID version 5, both namespace and name parameters are required. The namespace should be a DNS name, URL, or any string that uniquely identifies your application. --- ## 📖 Usage Examples ### Example 1: Basic Random UUIDs Generate 100 random UUIDs (version 4): json { "version": "4", "count": 100, "outputFormat": "json" } ### Example 2: Timestamp-based UUIDs Generate 50 timestamp-based UUIDs (version 1): json { "version": "1", "count": 50, "outputFormat": "csv" } ### Example 3: Namespace-based UUIDs Generate 200 namespace-based UUIDs (version 5): json { "version": "5", "count": 200, "namespace": "mycompany.com", "name": "user-session", "outputFormat": "text" } ### Example 4: Bulk Generation Generate the maximum number of UUIDs for large-scale applications: json { "version": "4", "count": 10000, "outputFormat": "json" } --- ## 📤 Output Data Each UUID result includes: | Field | Type | Description | |-------|------|-------------| | uuid | String | Generated UUID string | | version | String | UUID version used (1, 4, or 5) | | timestamp | String | Generation timestamp in ISO format | | index | Integer | Sequential index of the UUID (1-based) | ### Sample Output json { "uuid": "550e8400-e29b-41d4-a716-446655440000", "version": "4", "timestamp": "2024-01-15T10:30:00.000Z", "index": 1 } ### Output Formats - JSON: Structured data with all fields (default) - CSV: Tabular format with headers for spreadsheet applications - Text: Plain text file with just the UUID strings (one per line) Data is delivered in clean, structured format, ready to download as JSON, CSV, plain text, or integrate via API. --- ## 🔍 UUID Versions Explained ### Version 1 (Timestamp-based) - Uses timestamp and MAC address - Time-ordered and sortable - Good for database primary keys - Slightly less random than v4 ### Version 4 (Random) - Completely random (except for version bits) - Most commonly used version - Highest randomness - Not time-ordered ### Version 5 (Namespace-based) - Deterministic - same namespace+name always produces same UUID - Useful for generating consistent identifiers - Based on SHA-1 hash - Great for application-specific IDs --- ## ❓ FAQ Q: How many UUIDs can I generate? A: You can generate between 1 and 10,000 UUIDs per run. For larger datasets, run the Actor multiple times. Q: Are the UUIDs guaranteed to be unique? A: Yes, all generated UUIDs follow RFC 4122 standards. Version 1 and 4 provide practical uniqueness, while version 5 provides deterministic uniqueness within the same namespace. Q: Which UUID version should I use? A: Use v4 for general purposes, v1 for time-ordered identifiers, and v5 when you need consistent, reproducible IDs from the same input. Q: Can I use this for database primary keys? A: Yes, all UUID versions are suitable for database keys. Version 1 is particularly good for time-ordered data. Q: What's the difference between output formats? A: JSON provides full metadata, CSV is ideal for spreadsheets, and text format gives you just the UUID strings for simple integration. --- ## 🎯 Target Audience This Actor is designed for: - Software Developers building applications that require unique identifiers - Database Administrators managing large-scale data systems - API Developers creating microservices architectures - QA Testers needing test data with unique identifiers - System Integrators working on distributed applications --- ## 🚀 Benefits - Eliminate the need for custom UUID generation scripts - Ensure compliance with RFC standards for identifier uniqueness - Save development time with ready-to-use functionality - Scale reliably for high-volume identifier needs - Integrate easily with existing Apify workflows and external systems through standard output formats and API accessibility