UUID Generation API

Generate random UUID. RFC 4122 based UUIDs as well as non standard version 6 uuid are supported.

Supported features:

• Generate random UUIDs
• Support for nil (00000000-0000-0000-0000-000000000000) uuid
• Support for RFC 4122 version 1(date-time and MAC)
• Support for RFC 4122 version 2 (date-time and MAC address, DCE security version)
• Support for RFC 4122 version 3 and 5 (namespace name based)
• Support for RFC 4122 version 4 (random)
• Support for non standard version 6 (Ordered Time UUID)
• Support for new version 7 UUIDs
• Parse UUID strings, check for validity and get version details

API End Points

The end point for connecting : If you subscribe directly from us use this endpoint.

	https://api.fungenerators.com

Documentation

Generate UUIDs

    GET /uuid?limit=2&version=4

The above call should produce a result like the following

{
  "success": {
    "total": 4
  },
  "contents": [
    {
      "uuid": "1419cdfc-7ffc-4074-93c0-cd047e58c716",
      "version": "4"
    },
    {
      "uuid": "4b5c78fe-9c8b-4351-89a6-c7b573b286de",
      "version": "4"
    }
  ],
  "copyright": {
    "url": "http://fungenerators.com",
    "year": "2024"
  }
}

Parsing UUIDs

    GET /uuid/parse?uuid=018f53b0-7387-717b-ae74-d3a326ba16cd

The above call should produce a result like the following

{
  "success": {
    "total": 3
  },
  "contents": {
    "valid": true,
    "version": 7,
    "uuid": "018f53b0-7387-717b-ae74-d3a326ba16cd"
  },
  "copyright": {
    "url": "http://fungenerators.com",
    "year": "2024"
  }
}

API Rate Limiting for UUID Generation API

Some of our API calls may be public(requires free API key) , while others requires paid subscription. To maintain our serice levels both public and private API endpoints are ratelimited. Please consult your specific plan that you subscribed to for the rate limit details.

Authenticating with the UUID Generation API

Currently we support API Key based authentication. Please set your Autorization Bearer request header with value of your API key. Alternatively you can also pass api_key= as a request parameter, though we strongly discourage this mode of passing the key, since it will allow others to see your key.

In curl this would mean sending the Authorization header like below.

            
 curl -i <url> -H "Authorization: Bearer <api_key>"
            
            

If you are using PHP.

            
$authorization = "Authorization: Bearer <api_key>";
$ch = curl_init('<url>'); // Initialise cURL
curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type: application/json' , $authorization ));
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST"); // OR GET
$result = curl_exec($ch);
curl_close($ch);
            
            

In javascript you can use headers key to add the authorization header

            
$.ajax({
   url: '<url>'
   type: 'GET',
   contentType: 'application/json'
   headers: {
      'Authorization': 'Bearer <api_key>'
   },
   success: function (result) {
       // CallBack(result);
   },
   error: function (error) {

   }
});