True Random Number Service

API Keys

All applications that use RANDOM.ORG's API require an API key, which must be included in calls to the API.

Format and Security

An API key is a UUID generated for you by RANDOM.ORG. If you are an application developer, you would typically create one API key for each application you make that uses RANDOM.ORG. You can monitor the true random bit usage for each key, start and stop each key separately.

Knowledge of your API key gives access to the request and bit quotas for that key. For this reason, you will most likely want to keep your API keys as secret as possible. For example, if you need to embed a key in a mobile app, you will most likely want to obfuscate it.

Daily Limits

Your API key has a daily request limit and a daily bit limit. These limits depend on the license tier you chose for the API key. Your key's daily limits are reset every midnight UTC.

To query the limits of your API key, use the getUsage method of the API. For a beta key, the default request limit is 1,000 requests/day and the bit limit is 250,000 bits/day.

Key States

An API key can be in one of the following states:

running
This is the normal state for an API key. It means that the key is active and can be used to serve requests, as long as those requests do not result in the key exceeding its daily request or bit limits.
stopped
If you wish to stop requests being served for a given API key, you can place it in a stopped state. While the key is stopped, any requests using that key will return an error message. The key will remain stopped until you start it again.

To query the status of your API key, use the getUsage method of the API.

© 1998-2017 RANDOM.ORG
Terms and Conditions
About Us