🆔 GUID Generator Generate globally unique identifiers (GUIDs) in various formats, catering to developers and applications that require unique identification strings. This Actor supports the generation of multiple types of GUIDs, including standard UUID v1, v4, and v5 formats, as well as custom alphanumeric identifiers and sequential GUIDs with timestamp prefixes. --- ## ✨ Why Use GUID Generator? - ⚡ Bulk Generation - Generate thousands of unique identifiers simultaneously - 🎯 Multiple Formats - Support for UUID v1, v4, v5, alphanumeric, and sequential formats - 📈 Scalable - Create from 1 to 10,000 GUIDs in a single run - 🎨 Customizable - Add custom prefixes, suffixes, and character sets - 📊 Flexible Output - Export in JSON, CSV, or plain text formats - 🔒 Standards Compliant - Follows RFC 4122 for UUID generation --- ## 📥 Input Parameters | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | guidType | String | ✅ Yes | "uuid-v4" | Type of GUID to generate: uuid-v1, uuid-v4, uuid-v5, alphanumeric, sequential | | count | Integer | ✅ Yes | 100 | Number of GUIDs to generate (range: 1-10,000) | | prefix | String | ❌ No | "" | Optional prefix to add to each GUID | | suffix | String | ❌ No | "" | Optional suffix to add to each GUID | | outputFormat | String | ❌ No | "json" | Output format: json, csv, or text | | namespace | String | ❌ No | "example.com" | Namespace for UUID v5 generation | | name | String | ❌ No | "guid-generator" | Name for UUID v5 generation | > Note: For UUID v5 generation, both namespace and name parameters are used to create deterministic UUIDs. --- ## 📖 Usage Examples ### Example 1: Basic UUID v4 Generation Generate 100 standard UUID v4 identifiers: json { "guidType": "uuid-v4", "count": 100, "outputFormat": "json" } ### Example 2: Custom Alphanumeric IDs Generate 500 alphanumeric IDs with prefix: json { "guidType": "alphanumeric", "count": 500, "prefix": "USER_", "suffix": "_2024", "outputFormat": "csv" } ### Example 3: Sequential Timestamped GUIDs Generate 1000 sequential GUIDs with timestamps: json { "guidType": "sequential", "count": 1000, "prefix": "ORDER_", "outputFormat": "text" } ### Example 4: Deterministic UUID v5 Generate consistent UUIDs v5 for specific namespace: json { "guidType": "uuid-v5", "count": 50, "namespace": "myapp.com", "name": "user-session", "outputFormat": "json" } ### Example 5: Time-based UUID v1 Generate 200 time-based UUID v1 identifiers: json { "guidType": "uuid-v1", "count": 200, "prefix": "TXN_", "outputFormat": "json" } --- ## 📤 Output Data Each GUID result includes: | Field | Type | Description | |-------|------|-------------| | id | String | Generated GUID/UUID with optional prefix/suffix | | type | String | Type of GUID generated | | timestamp | String | Generation timestamp (ISO 8601 format) | | index | Integer | Sequential index of the generated GUID | ### Sample Output json { "id": "USER_f47ac10b-58cc-4372-a567-0e02b2c3d479_2024", "type": "uuid-v4", "timestamp": "2024-01-15T10:30:00.000Z", "index": 1 } ### Output Formats - JSON: Structured data with metadata (default) - CSV: Tabular format with headers - Text: Plain text list of GUIDs only Data is delivered in clean JSON format, ready to download as JSON, CSV, Excel, or integrate via API. --- ## 🎯 Target Audience This Actor is ideal for: - Software Developers building applications that require unique record identifiers - Database Administrators needing primary keys for large datasets - API Developers creating unique tokens and session IDs - System Integrators working on data migration projects - DevOps Engineers generating unique resource names - Security Engineers creating unique session identifiers --- ## 💡 Benefits - Eliminates Custom Code - No need to write your own GUID generation logic - Standards Compliant - Ensures compliance with RFC 4122 for UUIDs - Saves Development Time - Automated bulk generation saves hours of work - Reduces Collision Risk - Cryptographically secure generation prevents duplicates - Flexible Integration - Multiple output formats for easy integration - Scalable Solution - Handle from small projects to enterprise-scale needs --- ## ❓ FAQ Q: What's the difference between UUID v1, v4, and v5? A: UUID v1 uses timestamp and MAC address, v4 uses random numbers, and v5 uses namespace/name hashing for deterministic results. Q: How many GUIDs can I generate at once? A: You can generate between 1 and 10,000 GUIDs per run. For larger datasets, run the Actor multiple times. Q: Are the generated GUIDs truly unique? A: Yes, UUID v4 uses cryptographically secure random numbers, making collisions statistically impossible for practical purposes. Q: Can I use custom character sets for alphanumeric GUIDs? A: Currently, alphanumeric GUIDs use uppercase letters, lowercase letters, and numbers (A-Z, a-z, 0-9). Q: What format are the timestamps in? A: Timestamps are in ISO 8601 format (e.g., "2024-01-15T10:30:00.000Z"). Q: Can I generate GUIDs with specific patterns? A: Yes, you can use prefix and suffix parameters to add custom patterns to any GUID type. --- ## 🔧 Technical Details - UUID v1: Time-based with 60-bit timestamp and 48-bit node identifier - UUID v4: Random-based with 122 random bits - UUID v5: SHA-1 hash of namespace and name - Alphanumeric: 16-character random string from A-Z, a-z, 0-9 - Sequential: Base36 timestamp + random suffix for ordering All generated GUIDs follow industry standards and are suitable for production use in databases, APIs, and distributed systems.