RANDOM.ORG API function library

randomdotorg_integer( num,    min,    max,    base  =  "10", rnd  =  "new" )

It generates truly random integers in configurable intervals.

Parameters

Returns

• Success: Generated integers as comma separated values (CSV)
• Error: The string “Error:” followed by a string with further details.

Remarks

rnd:

Determines the randomization to use to generate the numbers.  If new is specified, then a new randomization will created from the truly random bitstream at RANDOM.ORG.  This is probably what you want in most cases.  If id.identifier is specified, the identifier is used to determine the randomization in a deterministic fashion from a large pool of pregenerated random bits.  Because the numbers are produced in a deterministic fashion, specifying an id basically uses RANDOM.ORG as a pseudo-random number generator.  The third (date.iso-date) form is similar to the second; it allows the randomization to be based on one of the daily pregenerated files.  This form must refer to one of the dates for which files exist, so it must be the current day (according to UTC) or a day in the past.  The date must be in ISO 8601 format (i.e., YYYY-MM-DD) or one of the two shorthand strings today or yesterday.

Examples

MsgBox, % randomdotorg_integer(10,0,9999)
MsgBox, % randomdotorg_integer(5,111111,121212,10,"date.2010-01-01")
MsgBox, % randomdotorg_integer(1,-555,555)
MsgBox, % randomdotorg_integer(1,0,10,2)

randomdotorg_string( num,    len,    digits  =  true, upperalpha  =  true, loweralpha  =  true, unique  =  true, rnd  =  "new" )

It generates truly random strings of various length and character compositions.

Parameters

Returns

• Success: Generated strings as comma separated values (CSV)
• Error: The string “Error:” followed by a string with further details.

Remarks

rnd:

Determines the randomization to use to generate the numbers.  If new is specified, then a new randomization will created from the truly random bitstream at RANDOM.ORG.  This is probably what you want in most cases.  If id.identifier is specified, the identifier is used to determine the randomization in a deterministic fashion from a large pool of pregenerated random bits.  Because the numbers are produced in a deterministic fashion, specifying an id basically uses RANDOM.ORG as a pseudo-random number generator.  The third (date.iso-date) form is similar to the second; it allows the randomization to be based on one of the daily pregenerated files.  This form must refer to one of the dates for which files exist, so it must be the current day (according to UTC) or a day in the past.  The date must be in ISO 8601 format (i.e., YYYY-MM-DD) or one of the two shorthand strings today or yesterday.

Examples

;This one generates ten unique strings. Each string is 15 characters long,
;and contains lower- and uppercase letters and numbers:
MsgBox, % randomdotorg_string(10,15)


;This one generates five strings. Each string is 12 characters long,
;and consists of lowercase letters and numbers, and the strings may be identical:
MsgBox, % randomdotorg_string(5,12,true,false,true,false)

randomdotorg_password( num,    len,    rnd  =  "new" )

It generates truly random passwords (6-24 characters long).

Parameters

Returns

• Success: Generated passwords as comma separated values (CSV)
• Error: The string “Error:” followed by a string with further details.

Remarks

rnd:

Determines the randomization to use to generate the numbers.  If new is specified, then a new randomization will created from the truly random bitstream at RANDOM.ORG.  This is probably what you want in most cases.  If id.identifier is specified, the identifier is used to determine the randomization in a deterministic fashion from a large pool of pregenerated random bits.  Because the numbers are produced in a deterministic fashion, specifying an id basically uses RANDOM.ORG as a pseudo-random number generator.  The third (date.iso-date) form is similar to the second; it allows the randomization to be based on one of the daily pregenerated files.  This form must refer to one of the dates for which files exist, so it must be the current day (according to UTC) or a day in the past.  The date must be in ISO 8601 format (i.e., YYYY-MM-DD) or one of the two shorthand strings today or yesterday.

About security

The passwords are transmitted securely (via SSL) and are not stored on the RANDOM.ORG server.  Nevertheless, the best data security practice is not to let anyone but yourself generate your most important passwords.  So, feel free to use these passwords for your wi-fi encryption or for that extra Gmail account, but you shouldn’t use any online service to generate passwords for highly sensitive things, such as your online bank account.

Examples

MsgBox, % randomdotorg_password(10,20)
MsgBox, % randomdotorg_password(10,6)

randomdotorg_randomizelist( list,    rnd  =  "new" )

It arranges the items of a list in random order.

Parameters

Returns

• Success: Randomized list, items separated with linebreaks.
• Error: The string “Error:” followed by a string with further details.

Remarks

• rnd:

Determines the randomization to use to generate the numbers.  If new is specified, then a new randomization will created from the truly random bitstream at RANDOM.ORG.  This is probably what you want in most cases.  If id.identifier is specified, the identifier is used to determine the randomization in a deterministic fashion from a large pool of pregenerated random bits.  Because the numbers are produced in a deterministic fashion, specifying an id basically uses RANDOM.ORG as a pseudo-random number generator.  The third (date.iso-date) form is similar to the second; it allows the randomization to be based on one of the daily pregenerated files.  This form must refer to one of the dates for which files exist, so it must be the current day (according to UTC) or a day in the past.  The date must be in ISO 8601 format (i.e., YYYY-MM-DD) or one of the two shorthand strings today or yesterday.

• linebreaks:

All three types of linebreak can be used: “`r” amd “`n” and “`r`n”.  After the randomization the result list will have the same linebreaks as the input list.

Examples

;This one loads the content of a file, randomizes it and displays the randomized list via MsgBox.
;(Note: The file must exist and must contain a valid list of items separated by linebreaks for this example to work.)
FileRead, _list, c:\list.txt
Msgbox, % randomdotorg_randomizelist(_list)


;This one randomizes the list content of a variable.
_list := "item1`nitem2`nitem3`nitem4`n"  ;the content of the _list variable is a list with 4 items, separated by linebreaks (`n)
_list := randomdotorg_randomizelist(_list)


;This one is the same as the second example.
_list=
(
item1
item2
item3
item4
)
_list := randomdotorg_randomizelist(_list)

randomdotorg_lottery( tickets,    num_main,    highest_main,    num_bonus  =  "0", highest_bonus  =  "0" )

It allows you to quick pick lottery tickets.

Parameters

Returns

• Success: Generated tickets as comma separated items (CSV)
• Error: The string “Error:” followed by a string with further details.

Remarks

If you have to select 6 numbers from 1-49 and 1 bonus number from 1-20 then: num_main is 6, highest_main is 49, num_bonus is 1, highest_bonus is 20.

Examples

MsgBox, % randomdotorg_lottery(5,6,59) ;five tickets for a game where 6 numbers are drawn from 1-59
MsgBox, % randomdotorg_lottery(5,6,59,1,20) ;same as above, only with an additional bonus number from 1-20

randomdotorg_clocktime( num,    earliest  =  "00:00", latest  =  "23:59", interval  =  "5", rnd  =  "new" )

It generates random clock times of the day (or night).

Parameters

Returns

• Success: Generated clock times as comma separated values (CSV)
• Error: The string “Error:” followed by a string with further details.

Remarks

• rnd:

Determines the randomization to use to generate the numbers.  If new is specified, then a new randomization will created from the truly random bitstream at RANDOM.ORG.  This is probably what you want in most cases.  If id.identifier is specified, the identifier is used to determine the randomization in a deterministic fashion from a large pool of pregenerated random bits.  Because the numbers are produced in a deterministic fashion, specifying an id basically uses RANDOM.ORG as a pseudo-random number generator.  The third (date.iso-date) form is similar to the second; it allows the randomization to be based on one of the daily pregenerated files.  This form must refer to one of the dates for which files exist, so it must be the current day (according to UTC) or a day in the past.  The date must be in ISO 8601 format (i.e., YYYY-MM-DD) or one of the two shorthand strings today or yesterday.

• earliest, latest, interval:

Each clock time will be generated between the earliest time and the latest time with intervals specified in the interval parameter.  (Limits for earliest and latest are: 00:00 and 23:59; both inclusive).  Eg.: Wrong usage: earliest is “00:00” latest is “00:01” interval is “5”.  In this case no clock times can be generated.  The difference between the earliest and the latest time should be at least 5 minutes to generate one clock time.  Proper usage: earliest is “00:00” latest is “11:00” interval is “60”.  This will successfully generate at least 12 clock times, because the difference between 00:00 and 11:00 is 12 hours (12 x 60 minutes).

Examples

MsgBox, % randomdotorg_clocktimes(10)
MsgBox, % randomdotorg_clocktimes(10,"11:12","23:00")
MsgBox, % randomdotorg_clocktimes(10,"11:12","23:00",30)

randomdotorg_sequence( min,    max,    rnd  =  "new" )

It randomizes a given interval of integers, i.e., arranges them in random order.

Parameters

Returns

• Success: Generated integers as comma separated values (CSV)
• Error: The string “Error:” followed by a string with further details.

Remarks

rnd:

Determines the randomization to use to generate the numbers.  If new is specified, then a new randomization will created from the truly random bitstream at RANDOM.ORG.  This is probably what you want in most cases.  If id.identifier is specified, the identifier is used to determine the randomization in a deterministic fashion from a large pool of pregenerated random bits.  Because the numbers are produced in a deterministic fashion, specifying an id basically uses RANDOM.ORG as a pseudo-random number generator.  The third (date.iso-date) form is similar to the second; it allows the randomization to be based on one of the daily pregenerated files.  This form must refer to one of the dates for which files exist, so it must be the current day (according to UTC) or a day in the past.  The date must be in ISO 8601 format (i.e., YYYY-MM-DD) or one of the two shorthand strings today or yesterday.

Examples

MsgBox, % randomdotorg_sequence(1,144)
MsgBox, % randomdotorg_sequence(-10,20)
MsgBox, % randomdotorg_sequence(-10,20,"date.2010-01-01")

randomdotorg_decimalfraction( num,    dec  =  10, rnd  =  "new" )

It generates random decimal fractions in the [0,1] interval.

Parameters

Returns

• Success: Generated decimal fractions as comma separated values (CSV)
• Error: The string “Error:” followed by a string with further details.

Remarks

rnd:

Determines the randomization to use to generate the numbers.  If new is specified, then a new randomization will created from the truly random bitstream at RANDOM.ORG.  This is probably what you want in most cases.  If id.identifier is specified, the identifier is used to determine the randomization in a deterministic fashion from a large pool of pregenerated random bits.  Because the numbers are produced in a deterministic fashion, specifying an id basically uses RANDOM.ORG as a pseudo-random number generator.  The third (date.iso-date) form is similar to the second; it allows the randomization to be based on one of the daily pregenerated files.  This form must refer to one of the dates for which files exist, so it must be the current day (according to UTC) or a day in the past.  The date must be in ISO 8601 format (i.e., YYYY-MM-DD) or one of the two shorthand strings today or yesterday.

Examples

MsgBox, % randomdotorg_decimalfraction(10)
MsgBox, % randomdotorg_decimalfraction(10,2)

randomdotorg_gaussian( num,    mean  =  "0.0", stdev  =  "1.0", dec  =  10, rnd  =  "new" )

It generates random numbers from a Gaussian distribution (also known as a normal distribution).

Parameters

Returns

• Success: Generated numbers as comma separated values (CSV)
• Error: The string “Error:” followed by a string with further details.

Remarks

rnd:

Determines the randomization to use to generate the numbers.  If new is specified, then a new randomization will created from the truly random bitstream at RANDOM.ORG.  This is probably what you want in most cases.  If id.identifier is specified, the identifier is used to determine the randomization in a deterministic fashion from a large pool of pregenerated random bits.  Because the numbers are produced in a deterministic fashion, specifying an id basically uses RANDOM.ORG as a pseudo-random number generator.  The third (date.iso-date) form is similar to the second; it allows the randomization to be based on one of the daily pregenerated files.  This form must refer to one of the dates for which files exist, so it must be the current day (according to UTC) or a day in the past.  The date must be in ISO 8601 format (i.e., YYYY-MM-DD) or one of the two shorthand strings today or yesterday.

Examples

MsgBox, % randomdotorg_gaussian(5)

randomdotorg_bitmap( save_path  =  "", format  =  "gif", width  =  64, height  =  64, zoom  =  1 )

It generates random bitmaps.  (BETA)

Parameters

Returns

• Success: If the save_path parameter isn’t specified (left blank: “”): The function will return the generated random image as hex data.  If the save_path paraneter is specified: The function will return true/false values indicating if the saving process was successful.
• Error: The string “Error:” will be returned followed by a string with further details.  (Only if the query to RANDOM.ORG wasn’t successful.)

Remarks

The final image resolution will be (w × z) by (h × z) where w is the width, h is the height and z is the zoom factor.  If you want to save the generated random image to the hard disk, specify a full path in the save_path parameter, eg.

randomdotorg_bitmap("c:\random\images\random1.gif") ;This'll work.

or

randomdotorg_bitmap("f:\random-image.png","png") ;This'll work.

depending on the format defined in the format parameter (gif by default).  If the specified path doesn’t include a file name, the function will not be able to save the image, and will return False eg.: Wrong usage:

randomdotorg_bitmap("c:\images") ;This WON'T work.

If you leave the save_path parameter blank, eg.:

randomdotorg_bitmap() ;This'll work.

or

randomdotorg_bitmap("",png) ;This'll work.

etc., the function will return the image converted into hex data.  This way you can store the image in text files, include in scripts, and so on.  You can also write the image to hard disk yourself, but before you can do that, the hex data must be converted back into binary.  For the binary<->hex conversion and the binary file writing you can use PhiLho’s scripts: http://www.autohotkey.com/forum/viewtopic.php?t=7549 . Here’s a small example script for this scenario: http://autohotkey.net/~gahks/_randomdotorg_bitmap_EXAMPLE.zip

Examples

; This example generates a 64x64 random image in gif format (default parameters), saves it as "c:\random.gif",
; and displays "Successful!", if saving the image was successful, or "Error!", if the the generation or saving process failed.
_var:=randomdotorg_bitmap("c:\random.gif")
if (_var && !InStr(_var,"Error:"))
   MsgBox, Successful!
else
   MsgBox, Error!


; This example generates a 100x100 random image with a zoom value of 2 (see Remarks) in png format,
; returns the image converted into hex data, and displays it in an Edit control.
_var:=randomdotorg_bitmap("","png",100,100,2)
if (_var && !InStr(_var,"Error:")) {
gui, add, edit, w300 h300, % _var
gui, show,, Image data in hex format!
return
}
else
   MsgBox, Error!
GuiClose:
ExitApp

; A full working version of the second example (the hex data is converted back to binary
; and written out to an image file) can be downloaded here:
; http://autohotkey.net/~gahks/_randomdotorg_bitmap_EXAMPLE.zip

randomdotorg_noise( save_path  =  "", format  =  "wav", volume  =  100, channels  =  "stereo", rate  =  16000, size  =  8, date  =  "today" )

It generates random audio noise, i.e., audio files containing perfect white noise.  (Detailed description in Remarks.)

Parameters

Returns

• Success: If the save_path parameter isn’t specified (left blank: “”): The function will return the generated random noise as hex data.  If the save_path paraneter is specified: The function will return true/false values indicating if the saving process was successful.
• Error: The string “Error:” will be returned followed by a string with further details.  (Only if the query to RANDOM.ORG wasn’t successful.)

Remarks

Detailed description of random noise generator: http://www.random.org/audio-noise/description/ For more info on the save_path parameter, and the return values and useage of this function see the Returns,Remarks,Examples sections of the function randomdotorg_bitmap().

Examples

; This example generates a random noise of 16000 bits per second sample rate, 8 bits per sample sample size,
; with 100% volume and stereo channels in wav format based on the randomness generated today. (Default parameters),
; saves the generated noise as "c:\random.wav", and displays the message "Successful!", if saving the image was successful,
; or "Error!", if the the generation or saving process failed.
_var:=randomdotorg_noise("c:\noise.wav")
if (_var && !InStr(_var,"Error:"))
   MsgBox, Successful!
else
   MsgBox, Error!


; This example generates a random noise of 44100 bits per second sample rate, 16 bits per sample sample size,
; with 80% volume and mono channels in aiff format based on the randomness generated on 2010-01-01,
; returns the noise in hex data format, and displays the first 500 chars in an Edit control.
_var:=randomdotorg_noise("","aiff",80,"mono",44100,16,"2010-01-01")
if (_var && !InStr(_var,"Error:")) {
gui, add, edit, w300 h300, % SubStr(_var,1,500)
gui, show,, Audio data in hex format!
return
}
else
   MsgBox, Error!
GuiClose:
ExitApp

; For an example on what to do with the hex data, see the Remarks and Examples section of randomdotorg_bitmap().

randomdotorg_quota( ip  =  "" )

It allows you to examine your quota at any point in time.  For further info see: Remarks.

Parameters

Returns

• Success: The qutoa associated with the specified IP address.
• Error: The string “Error:” followed by a string with further details.

Remarks

The quota system works on the basis of IP addresses.  Each IP address has a base quota of 1,000,000 bits.  When you make a request for random numbers (or strings, etc.), the server deducts the number of bits it took to satisfy your request from the quota associated with your client’s IP address.  If your client issues a request for random numbers while its quota is negative, the RANDOM.ORG server will return a 503 error response.  Every day, shortly after midnight UTC, all quotas with less than 1,000,000 bits receive a free top-up of 200,000 bits.

Examples

MsgBox, % randomdotorg_quota()
MsgBox, % randomdotorg_quota("134.226.36.80")